Terminal, radio communication method, and base station

Abstract

To provide a terminal, a radio communication method, and a base station capable of performing flexible communication operation between operators.SOLUTION: A terminal according to an aspect of the present disclosure includes a receiver configured to receive configuration information of a second SIB included in a first system information block (SIB), and a controller configured to control monitoring of the second SIB based on the configuration information of the second SIB. According to an aspect of the present disclosure, it is possible to operate flexible communication between operators.SELECTED DRAWING: Figure 5

Description

[Technical Field]

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

[0002] In Universal Mobile Telecommunications System (UMTS) networks, Long Term Evolution (LTE) was specified with the aim of achieving higher data rates and lower latency (Non-Patent Document 1). Also, LTE-Advanced (3GPP Rel. 10-14) was specified with the aim of achieving higher capacity and more advanced features than LTE (Third Generation Partnership Project (3GPP) Release (Rel.) 8, 9).

[0003] Successor systems to LTE (e.g., 5th generation mobile communication system (5G), 5G+ (plus), 6th generation mobile communication system (6G), New Radio (NR), 3GPP Rel. 15 or later) are also being considered. [Prior art documents] [Non-patent literature]

[0004] [Non-Patent Document 1] 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 Summary of the Invention [Problem to be solved by the invention]

[0005] In future wireless communication systems (for example, Rel. 18 and later), resource sharing is being considered with the aim of improving the efficiency of frequency band utilization (existing frequency bands and new high frequency bands).

[0006] However, there are cases where it is not possible to change the settings for a specific UE between multiple operators. In such cases, flexible communication operation for each operator cannot be performed, which may lead to a suppression of communication quality improvement.

[0007] Therefore, one of the objects of the present disclosure is to provide a terminal, a wireless communication method, and a base station that enable flexible communication operations between operators. [Means for solving the problem]

[0008] A terminal according to one embodiment of the present disclosure has a receiving unit that receives configuration information of a second system information block (SIB) included in a first SIB, and a control unit that controls monitoring of the second SIB based on the configuration information of the second SIB. [Effects of the Invention]

[0009] According to one aspect of the present disclosure, flexible communication operations can be performed between operators. [Brief explanation of the drawings]

[0010] [Figure 1] 1A-1D are diagrams illustrating an example of network sharing. [Figure 2] 2A and 2B are diagrams showing an example of association related to PLMN IDs in the first embodiment. [Figure 3] 3A and 3B are diagrams showing an example of association related to PLMN IDs in the second embodiment. [Figure 4]4A and 4B are diagrams showing an example of association related to PLMN IDs in the third embodiment. [Figure 5] FIG. 5 is a diagram showing an example of association related to PLMN IDs in the fourth embodiment. [Figure 6] FIG. 6 is a diagram showing an example of association related to PLMN IDs in the fifth embodiment. [Figure 7] FIG. 7 is a diagram illustrating an example of a schematic configuration of a wireless communication system according to an embodiment. [Figure 8] FIG. 8 is a diagram illustrating an example of the configuration of a base station according to an embodiment. [Figure 9] FIG. 9 is a diagram illustrating an example of the configuration of a user terminal according to an embodiment. [Figure 10] FIG. 10 is a diagram illustrating an example of the hardware configuration of a base station and a user terminal according to an embodiment. [Figure 11] FIG. 11 is a diagram illustrating an example of a vehicle according to an embodiment. DETAILED DESCRIPTION OF THE INVENTION

[0011] (resource sharing) In future wireless communication systems (for example, Rel. 18 and later), resource sharing is being considered with the aim of improving the efficiency of frequency band utilization (existing frequency bands and new high frequency bands).

[0012] Resource sharing allows multiple operators to share a radio access network (RAN), dividing the network (e.g., base station) investment costs among them and enabling the installation of a large number of base stations.

[0013] For example, by sharing an antenna site (land / tower, etc.) among multiple operators, the cost of installing a station can be shared among those operators.

[0014] In addition, by sharing distributed nodes (e.g., Distributed Units (DUs)) / aggregation nodes (e.g., Central Units (CUs)) among multiple operators (e.g., by sharing the hardware infrastructure), the equipment costs can be shared among the multiple operators.

[0015] Furthermore, by sharing a frequency / antenna unit (e.g., a Radio Unit (RU)) among multiple operators, resource utilization efficiency can be improved, for example, resources not being used by one operator can be used by other operators.

[0016] 1A-1D are diagrams illustrating an example of network sharing.

[0017] Figure 1A shows an example of site sharing. As shown in Figure 1A, in site sharing, multiple operators share an antenna site. However, the service platform, HSS (Home Subscriber Server) / HLR (Home Location Register), Core Network (CN) Packet Switching (PS), base stations, and cells / frequencies are independent for each operator.

[0018] Figure 1B shows an example of MORAN (Multi Operator RAN). As shown in Figure 1B, in MORAN, multiple operators share antenna sites and parts of base stations (e.g., base station hardware). On the other hand, the service platform, HSS / HLR, CN PS, other parts of the base station (e.g., base station software), and cells / frequencies are independent for each operator.

[0019] Figure 1C shows an example of an MOCN (Multi Operator Core Network). As shown in Figure 1C, in an MOCN, multiple operators share base stations and cells / frequencies. On the other hand, the service platform, HSS / HLR, and CN PS are independent for each of the multiple operators.

[0020] Figure 1D shows an example of a GWCN (Gateway Core Network). As shown in Figure 1D, in a GWCN, multiple operators share CN PS, base stations, and cells / frequencies. On the other hand, the service platform and HSS / HLR are independent for each operator.

[0021] In MOCN / GWCN, since cells are shared by multiple operators, it is desirable to be able to change settings for each operator (for example, for each Public Land Mobile Network (PLMN) ID).

[0022] For example, in existing specifications, whether or not initial access to a cell is permitted, the tracking area code, a unique cell ID within a PLMN, etc. can be set for each PLMN ID.

[0023] On the other hand, for a terminal (user terminal, User Equipment (UE)) in an RRC connected state, operator-specific settings can be configured as an RRC configuration according to the PLMN ID of the terminal. Specifically, in resource sharing, if it is desired that only terminals of a specific operator can use some time resources of a shared cell, it is possible to configure terminals of other operators not to use those some time resources.

[0024] However, in existing specifications, most of the configurations (e.g., broadcast information, etc.) for a specific UE (e.g., a UE at initial access / in idle mode) are not assigned per operator (e.g., PLMN ID), and therefore the configurations cannot be changed between multiple operators. For example, parameters (e.g., ServingCellConfigCommonSIB) used for configuring random access channel (RACH) resources in system information block 1 (SIB1) are not assigned per PLMN ID, and therefore the RACH resources of a UE cannot be configured / changed per operator.

[0025] In this way, if the settings for a specific UE cannot be changed between multiple operators, flexible communication operation for each operator cannot be performed, which may hinder improvement in communication quality.

[0026] Therefore, the present inventors came up with the idea of ​​a method for applying / setting flexible operational policies / parameters between operators in order to efficiently place stations / utilize frequencies through resource sharing.

[0027] Hereinafter, embodiments of the present disclosure will be described in detail with reference to the drawings. Wireless communication methods according to the embodiments may be applied independently or in combination.

[0028] In the present disclosure, "A / B" and "at least one of A and B" may be interpreted interchangeably. Also, in the present disclosure, "A / B / C" may mean "at least one of A, B, and C."

[0029] In the present disclosure, terms such as activate, deactivate, indicate (or indicate), select, configure, update, and determine may be read interchangeably. In the present disclosure, terms such as support, control, controllable, operate, and operate may be read interchangeably.

[0030] In the present disclosure, Radio Resource Control (RRC), RRC parameters, RRC messages, higher layer parameters, information elements (IEs), configurations, etc. may be interchangeable. In the present disclosure, Medium Access Control (MAC) control elements (CEs), update commands, activation / deactivation commands, etc. may be interchangeable.

[0031] In the present disclosure, higher layer signaling may be, for example, any one of Radio Resource Control (RRC) signaling, Medium Access Control (MAC) signaling, broadcast information, and the like, or a combination thereof.

[0032] In the present disclosure, MAC signaling may use, for example, a MAC Control Element (MAC CE), a MAC Protocol Data Unit (PDU), etc. Broadcast information may be, for example, a Master Information Block (MIB), a System Information Block (SIB), Remaining Minimum System Information (RMSI), Other System Information (OSI), etc.

[0033] In the present disclosure, physical layer signaling may be, for example, Downlink Control Information (DCI), Uplink Control Information (UCI), and the like.

[0034] In this disclosure, the terms index, identifier (ID), indicator, resource ID, etc. may be interchangeable. In this disclosure, the terms sequence, list, set, group, cluster, subset, etc. may be interchangeable.

[0035] In the present disclosure, specific ID, ID related to a Public Land Mobile Network (PLMN), PLMN ID, PLMN identifier, PLMN Identity, PLMN identifier information, PLMN Identity information, PLMN ID information, information for identifying an operator, ID for identifying an operator, ID for each operator, group ID, PLMN group ID, etc. may be read interchangeably.

[0036] In the present disclosure, PLMN, carrier, operator, operator policy, carrier-specific settings, operator-specific settings, etc. may be read interchangeably.

[0037] (Wireless communication method) In the following description of the present disclosure, a PLMN ID will be used as an example of a specific ID, but the name of the specific ID is not limited to this.

[0038] In the present disclosure, the SIB used for initial access, SIB1, first SIB, and specific SIB may be read interchangeably.

[0039] First Embodiment Separate (independent) frequency / time resource configuration for each specific ID (eg, PLMN ID) may be supported.

[0040] The UE may receive information regarding frequency / time resources that are configured separately for each specific ID.

[0041] The frequency / time resource may be, for example, a frequency resource configured for a UE at initial access, or may be an initial DL / UL Bandwidth Part (BWP).

[0042] The information on the specific frequency / time resource may be included in configuration information (e.g., ServingCellConfigCommonSIB) of the serving cell included in broadcast information (e.g., system information (e.g., SIB / SIB1)). The information on the specific frequency / time resource may be included in at least one of DL configuration (e.g., downlinkConfigCommon / DownlinkConfigCommonSIB), UL configuration (e.g., uplinkConfigCommon / UplinkConfigCommonSIB), and supplementary UL (supplementaryUplink / UplinkConfigCommonSIB), which are included in the configuration information (e.g., ServingCellConfigCommonSIB) of the serving cell included in the system information.

[0043] The information regarding the specific frequency / time resource may be, for example, at least one of information regarding the initial DL BWP (e.g., initialDownlinkBWP / BWP-DownlinkCommon) and information regarding the initial UL BWP (e.g., initialUplinkBWP / BWP-UplinkCommon).

[0044] The information about the particular frequency / time resource may be associated with a particular ID (eg, a PLMN ID).

[0045] For example, the configuration information of the serving cell (eg, ServingCellConfigCommonSIB) included in the system information (eg, SIB / SIB1) may include information on one or more specific IDs (eg, PLMN IDs).

[0046] In the present disclosure, the information regarding a plurality of specific IDs may be information indicating a list of the specific IDs.

[0047] For example, at least one of the DL configuration (e.g., downlinkConfigCommon / DownlinkConfigCommonSIB), UL configuration (e.g., uplinkConfigCommon / UplinkConfigCommonSIB), and supplementary UL (supplementaryUplink / UplinkConfigCommonSIB) included in the configuration information of the serving cell included in the system information (e.g., ServingCellConfigCommonSIB) may include information regarding one or more specific IDs (e.g., PLMN IDs).

[0048] The UE may determine the configuration of a specific frequency resource for each specific ID (for example, a PLMN ID) based on the specific ID included in the SIB / SIB1.

[0049] The number (maximum number, for example, 1) of frequency resources (e.g., BWPs) that can be configured for each specific ID may be specified in the specification. The upper limit (for example, maxPLMN) of the number (total number) of frequency resources (e.g., BWPs) for different specific IDs may be specified in the specification.

[0050] 2A is a diagram showing an example of association related to PLMN IDs in the first embodiment. In the example shown in FIG. 2A, operator #1 whose PLMN ID is #1, operator #2 whose PLMN ID is #2, and operator #3 whose PLMN ID is #3 are defined. Note that in the present disclosure, the values ​​and numbers of PLMN IDs and the numbers and numbers of operators are merely examples and are not limited to the examples shown in each drawing.

[0051] In the example shown in Figure 2A, information about PLMN IDs (e.g., plmn-Identity / plmn-IdentityList) is included in the ServingCellConfigCommonSIB. That is, a ServingCellConfigCommonSIB is defined for each PLMN ID (each operator). That is, a DownlinkConfigCommonSIB and an UplinkConfigCommonSIB included in the ServingCellConfigCommonSIB, an initialDownlinkBWP included in the DownlinkConfigCommonSIB, and an initialUplinkBWP included in the UplinkConfigCommonSIB are defined for each PLMN ID (each operator).

[0052] Fig. 2B is a diagram showing another example of associations related to PLMN IDs in the first embodiment. In the example shown in Fig. 2B, the correspondence between PLMN IDs and operators is the same as in Fig. 2A.

[0053] In the example shown in Figure 2B, information about PLMN IDs (e.g., plmn-Identity / plmn-IdentityList) is included in the DownlinkConfigCommonSIB and the UplinkConfigCommonSIB. That is, a DownlinkConfigCommonSIB and an UplinkConfigCommonSIB are defined for each PLMN ID (each operator). That is, an initialDownlinkBWP included in the DownlinkConfigCommonSIB and an initialUplinkBWP included in the UplinkConfigCommonSIB are defined for each PLMN ID (each operator).

[0054] In the configurations shown in FIGS. 2A and 2B, certain parameters may be set separately for each PLMN ID, and other parameters may be set commonly to a plurality of PLMN IDs.

[0055] For example, the initialUplinkBWP may be set for each PLMN ID, and the initialDownlinkBWP may be set commonly for multiple PLMN IDs.

[0056] Alternatively, for example, the initialDownlinkBWP may be set for each PLMN ID, and the initialUplinkBWP may be set commonly for a plurality of PLMN IDs.

[0057] For at least one specific ID (e.g., PLMN ID), configuration of an SSB different from the SSB detected for receiving SIB / SIB1 may be supported. For at least one specific ID (e.g., PLMN ID), the UE may receive an SSB different from the SSB detected for receiving SIB / SIB1.

[0058] Serving cell configuration information (e.g., ServingCellConfigCommonSIB) included in system information (e.g., SIB / SIB1) may include information about the SSB. The information about the SSB may be associated with a specific ID (e.g., PLMN ID).

[0059] The information about the SSB may be at least one of information about the frequency position of the SSB (e.g., absoluteFrequencySSB), information about the subcarrier spacing of the SSB (e.g., ssbSubcarrierSpacing), information about the SSB index (information about the SSB index at which the UE is assumed to be transmitting, e.g., ssb-PositionsInBurst), and information about the periodicity of the SSB (e.g., ssb-periodicityServingCell).

[0060] The association of the information about the SSB with a specific ID (e.g., PLMN ID) may be performed within the parameters of a specific frequency resource, which may be the parameters of an initial DL BWP (e.g., initialDownlinkBWP / BWP-DownlinkCommon).

[0061] The UE may assume that the SSBs associated with a particular ID are included in the initial DL BWP for that particular ID, and may also support the case where the SSBs associated with a particular ID are not included in the initial DL BWP for that particular ID.

[0062] The UE may monitor only SSBs associated with a particular ID (eg, PLMN ID) of the UE, assuming that they are SSBs of the serving cell.

[0063] The UE may monitor both SSBs associated with the UE's particular ID (eg, PLMN ID) and SSBs detected to receive system information as SSBs of the serving cell.

[0064] The UE may use SSBs associated with an ID other than the UE's specific ID (eg, PLMN ID) for determining rate matching.

[0065] According to the first embodiment described above, it is possible to configure frequency resources (for example, initial DL / UL BWP) separately for each specific ID (for example, PLMN ID).

[0066] <Second embodiment> Separate (independent) frequency / time resource configuration for each specific ID (eg, PLMN ID) may be supported.

[0067] The UE may receive information regarding frequency / time resources that are configured separately for each specific ID.

[0068] The frequency / time resources may be, for example, time resources configured for a UE at initial access time, or may be UL / DL configuration in Time Division Duplex (TDD).

[0069] The information on the specific frequency / time resources may be included in configuration information (e.g., ServingCellConfigCommonSIB) of the serving cell included in broadcast information (e.g., system information (e.g., SIB / SIB1)). The information on the specific frequency / time resources may be UL / DL configuration in TDD (e.g., tdd-UL-DL-ConfigurationCommon / TDD-UL-DL-ConfigCommon).

[0070] The information about the particular frequency / time resource may be associated with a particular ID (eg, a PLMN ID).

[0071] For example, the configuration information of the serving cell (eg, ServingCellConfigCommonSIB) included in the system information (eg, SIB / SIB1) may include information on one or more specific IDs (eg, PLMN IDs).

[0072] For example, the UL / DL configuration in TDD (e.g., tdd-UL-DL-ConfigurationCommon / TDD-UL-DL-ConfigCommon) included in the configuration information of the serving cell included in the system information (e.g., ServingCellConfigCommonSIB) may include information on one or more specific IDs (e.g., PLMN IDs).

[0073] The UE may determine the configuration of specific time resources for each specific ID (e.g., PLMN ID) based on the specific ID included in the SIB / SIB1.

[0074] Fig. 3A is a diagram showing an example of association related to PLMN IDs in the second embodiment. In the example shown in Fig. 3A, the correspondence between PLMN IDs and operators is the same as in Fig. 2A and so on.

[0075] In the example shown in Figure 3A, information about PLMN IDs (e.g., plmn-Identity / plmn-IdentityList) is included in the ServingCellConfigCommonSIB. That is, a ServingCellConfigCommonSIB is defined for each PLMN ID (each operator). That is, tdd-UL-DL-ConfigurationCommon included in the ServingCellConfigCommonSIB is defined for each PLMN ID (each operator).

[0076] Fig. 3B is a diagram showing another example of associations related to PLMN IDs in the first embodiment. In the example shown in Fig. 3B, the correspondence between PLMN IDs and operators is the same as in Fig. 2A and so on.

[0077] In the example shown in Figure 3B, information about PLMN IDs (e.g., plmn-Identity / plmn-IdentityList) is included in tdd-UL-DL-ConfigurationCommon. That is, tdd-UL-DL-ConfigurationCommon is specified for each PLMN ID (for each operator). That is, at least one of the parameters included in tdd-UL-DL-ConfigurationCommon (e.g., a parameter indicating subcarrier spacing (referenceSubcarrierSpacing), a parameter indicating a first TDD UL / DL pattern (pattern1), and a parameter indicating a second TDD UL / DL pattern (pattern2)) is specified for each PLMN ID (for each operator).

[0078] In the configurations shown in FIGS. 3A and 3B, certain parameters may be set separately for each PLMN ID, and other parameters may be set commonly to a plurality of PLMN IDs.

[0079] For example, a parameter (pattern1) indicating a first TDD UL / DL pattern and a parameter (pattern2) indicating a second TDD UL / DL pattern may be set for each PLMN ID, and a parameter (referenceSubcarrierSpacing) indicating subcarrier spacing may be set commonly to multiple PLMN IDs.

[0080] Also, for example, a parameter (pattern 1) indicating a first TDD UL / DL pattern may be set for each PLMN ID, and a parameter (referenceSubcarrierSpacing) indicating a subcarrier spacing and a parameter (pattern 2) indicating a second TDD UL / DL pattern may be set in common to multiple PLMN IDs.

[0081] Also, for example, a parameter (pattern2) indicating the second TDD UL / DL pattern may be set for each PLMN ID, and a parameter (referenceSubcarrierSpacing) indicating the subcarrier spacing and a parameter (pattern1) indicating the first TDD UL / DL pattern may be set in common to multiple PLMN IDs.

[0082] Also, for example, a parameter indicating subcarrier spacing (referenceSubcarrierSpacing) may be set for each PLMN ID, and a parameter indicating a first TDD UL / DL pattern (pattern1) and a parameter indicating a second TDD UL / DL pattern (pattern2) may be set in common to multiple PLMN IDs.

[0083] The UL / DL configuration in TDD (e.g., tdd-UL-DL-ConfigurationCommon / TDD-UL-DL-ConfigCommon) may include at least one of information about available DL / UL resources and information about unavailable DL / UL resources. This allows each operator to configure and notify available / unavailable resources.

[0084] According to the second embodiment described above, it is possible to configure time resources (for example, UL / DL configuration in TDD) separately for each specific ID (for example, PLMN ID).

[0085] <Third embodiment> Separate (independent) random access channel (RACH) configuration for each specific ID (eg, PLMN ID) may be supported.

[0086] In the present disclosure, RACH, PRACH, random access preamble, random access, random access procedure, etc. may be read interchangeably.

[0087] The UE may receive information about the configuration of the RACH that is configured separately for each specific ID, and may control the random access procedure (RACH operation) based on the information about the configuration of the RACH.

[0088] The UE may determine the RACH time resource, RACH frequency resource, and RACH preamble configured for each specific ID.

[0089] The information on the configuration of the RACH may be a RACH configuration (e.g., RACH-ConfigCommon). The RACH configuration (e.g., RACH-ConfigCommon) may be included in information on the initial UL BWP (e.g., initialUplinkBWP / BWP-UplinkCommon).

[0090] The information regarding the configuration of the RACH may be associated with a specific ID (eg, a PLMN ID).

[0091] For example, the configuration information of the serving cell (e.g., ServingCellConfigCommonSIB) included in the system information (e.g., SIB / SIB1) may include information on one or more specific IDs (e.g., PLMN IDs). The UE may determine an association between the specific IDs and information on the configuration of the RACH included in the information on the initial UL BWP in the configuration information of the serving cell.

[0092] For example, information on one or more specific IDs (e.g., PLMN IDs) may be included in information on the initial UL BWP (e.g., initialUplinkBWP / BWP-UplinkCommon). The UE may determine an association between the specific IDs and information on the configuration of the RACH included in the information on the initial UL BWP.

[0093] For example, the RACH configuration (e.g., RACH-ConfigCommon) may include information on one or more specific IDs (e.g., PLMN IDs). The UE may determine an association between at least one of information on the configuration of the time resource / format of the PRACH (e.g., prach-ConfigurationIndex), information on the start position of the frequency resource of the PRACH (e.g., msg1-FrequencyStart), and information on the sequence of the PRACH (e.g., prach-RootSequenceIndex), which are included in the RACH configuration (e.g., RACH-ConfigCommon), and the information on the one or more specific IDs (e.g., PLMN IDs).

[0094] The UE may determine the configuration of the RACH for each specific ID (eg, PLMN ID) based on the specific ID included in the RACH configuration.

[0095] Fig. 4A is a diagram showing an example of association relating to PLMN IDs in the third embodiment. In the example shown in Fig. 4A, the correspondence between PLMN IDs and operators is the same as in Fig. 2A and so on.

[0096] In the example shown in Fig. 4A, information about PLMN IDs (e.g., plmn-Identity / plmn-IdentityList) is included in BWP-UplinkCommon. That is, BWP-UplinkCommon is defined for each PLMN ID (each operator). That is, RACH-ConfigCommon included in BWP-UplinkCommon is defined for each PLMN ID (each operator).

[0097] Fig. 4B is a diagram showing another example of associations relating to PLMN IDs in the third embodiment. In the example shown in Fig. 4B, the correspondence between PLMN IDs and operators is the same as in Fig. 2A and so on.

[0098] In the example shown in Fig. 4B, information about PLMN IDs (e.g., plmn-Identity / plmn-IdentityList) is included in RACH-ConfigCommon. That is, RACH-ConfigCommon is defined for each PLMN ID (for each operator). That is, at least one of parameters included in RACH-ConfigCommon (e.g., information about the configuration of time resources / formats of PRACH (e.g., prach-ConfigurationIndex), information about the start position of frequency resources of PRACH (e.g., msg1-FrequencyStart), and information about sequences of PRACH (e.g., prach-RootSequenceIndex)) is defined for each PLMN ID (for each operator).

[0099] In the configurations shown in FIGS. 4A and 4B, certain parameters may be set separately for each PLMN ID, and other parameters may be set commonly to a plurality of PLMN IDs.

[0100] For example, information regarding the configuration of the time resource / format of the PRACH (e.g., prach-ConfigurationIndex) may be configured for each PLMN ID, and information regarding the start position of the frequency resource of the PRACH (e.g., msg1-FrequencyStart) and information regarding the sequence of the PRACH (e.g., prach-RootSequenceIndex) may be configured commonly for multiple PLMN IDs.

[0101] Furthermore, for example, information regarding the configuration of the time resource / format of the PRACH (e.g., prach-ConfigurationIndex) and information regarding the start position of the frequency resource of the PRACH (e.g., msg1-FrequencyStart) may be configured for each PLMN ID, and information regarding the sequence of the PRACH (e.g., prach-RootSequenceIndex) may be configured in common for multiple PLMN IDs.

[0102] Furthermore, for example, information regarding the configuration of the time resource / format of the PRACH (e.g., prach-ConfigurationIndex) and information regarding the sequence of the PRACH (e.g., prach-RootSequenceIndex) may be configured for each PLMN ID, and information regarding the start position of the frequency resource of the PRACH (e.g., msg1-FrequencyStart) may be configured commonly for multiple PLMN IDs.

[0103] For example, information regarding the start position of the frequency resource of the PRACH (e.g., msg1-FrequencyStart) and information regarding the sequence of the PRACH (e.g., prach-RootSequenceIndex) may be configured for each PLMN ID, and information regarding the configuration of the time resource / format of the PRACH (e.g., prach-ConfigurationIndex) may be configured commonly for multiple PLMN IDs.

[0104] Furthermore, for example, information regarding the PRACH sequence (e.g., prach-RootSequenceIndex) may be configured for each PLMN ID, and information regarding the configuration of the PRACH time resource / format (e.g., prach-ConfigurationIndex) and information regarding the start position of the PRACH frequency resource (e.g., msg1-FrequencyStart) may be configured in common for multiple PLMN IDs.

[0105] Furthermore, for example, information regarding the start position of the frequency resource of the PRACH (e.g., msg1-FrequencyStart) may be configured for each PLMN ID, and information regarding the configuration of the time resource / format of the PRACH (e.g., prach-ConfigurationIndex) and information regarding the sequence of the PRACH (e.g., prach-RootSequenceIndex) may be configured commonly for multiple PLMN IDs.

[0106] The UE may transmit a RACH (e.g., message 1 (PRACH) / message 3 (RRC Setup Request) / message A) by including information about a specific ID (e.g., PLMN ID) in the RACH. The information about the specific ID (e.g., PLMN ID) may be the information about the specific ID (PLMN ID) or other information associated with the information about the specific ID (PLMN ID).

[0107] This allows the PRACH resources (time / frequency resources and / or preambles) associated with a specific ID (PLMN ID) to be determined / configured separately, and the network (base station) can recognize the specific ID (PLMN ID) selected by the UE from the detected PRACH resources.

[0108] According to the third embodiment described above, it is possible to set up a random access channel separately for each specific ID (for example, PLMN ID).

[0109] <Fourth embodiment> Apart from a particular system information block (eg, SIB1), the UE may monitor / detect / receive other SIBs for each particular ID (eg, PLMN ID).

[0110] The other SIB may be a SIB defined in an existing specification other than SIB1 (e.g., at least one of SIB2 to SIB14), or may be a newly defined SIB (e.g., SIB N (N is any alphanumeric character)) that is separate from the SIBs defined in the existing specification. The other SIB may be called SIB1X.

[0111] In this disclosure, the other SIB (SIB1X) may be referred to as a SIB associated with a particular ID.

[0112] Information / parameters regarding an SIB associated with a specific ID may be configured in SIB1. The UE may monitor the SIB associated with the specific ID based on the information regarding the SIB associated with the specific ID configured in SIB1.

[0113] The information regarding the SIB associated with a particular ID may be, for example, at least one of information regarding the periodicity of the SIB (e.g., si-Periodicity), information regarding the length of the window of system information (e.g., si-WindowLength), and information regarding the settings for transmission requests of system information (e.g., si-RequestConfig).

[0114] At least one of the pieces of information related to the SIB associated with a particular ID may be associated with the particular ID (eg, a PLMN ID).

[0115] Fig. 5 is a diagram showing an example of association relating to PLMN IDs in the fourth embodiment. In the example shown in Fig. 5, the correspondence between PLMN IDs and operators is the same as in Fig. 2A and so on.

[0116] In the example shown in Fig. 5, SIB1 includes parameters related to SIB1X. The parameters related to SIB1X include information related to PLMN IDs (e.g., plmn-Identity / plmn-IdentityList). That is, the parameters related to SIB1X (SIB1X) are specified for each PLMN ID (each operator). That is, at least one of parameters included in the parameters related to SIB1X (e.g., information related to the periodicity of SIB (SIB1X) (e.g., si-Periodicity), information related to the window length of system information (e.g., si-WindowLength), and information related to the configuration for transmission request of system information (e.g., si-RequestConfig)) is specified for each PLMN ID (each operator).

[0117] In the configuration shown in FIG. 5, some parameters may be set separately for each PLMN ID, and other parameters may be set commonly to a plurality of PLMN IDs.

[0118] For example, information regarding the periodicity of SIBs (e.g., si-Periodicity) may be configured for each PLMN ID, and information regarding the window length of system information (e.g., si-WindowLength) and information regarding the configuration for system information transmission requests (e.g., si-RequestConfig) may be configured commonly for multiple PLMN IDs.

[0119] Furthermore, for example, information regarding the periodicity of SIBs (e.g., si-Periodicity) and information regarding the length of the system information window (e.g., si-WindowLength) may be configured for each PLMN ID, and information regarding the configuration for system information transmission requests (e.g., si-RequestConfig) may be configured commonly for multiple PLMN IDs.

[0120] Furthermore, for example, information regarding the periodicity of SIBs (e.g., si-Periodicity) and information regarding the configuration for transmission requests of system information (e.g., si-RequestConfig) may be configured for each PLMN ID, and information regarding the window length of system information (e.g., si-WindowLength) may be configured commonly for multiple PLMN IDs.

[0121] Furthermore, for example, information regarding the window length of system information (e.g., si-WindowLength) and information regarding the configuration for a transmission request of system information (e.g., si-RequestConfig) may be configured for each PLMN ID, and information regarding the periodicity of SIBs (e.g., si-Periodicity) may be configured commonly for multiple PLMN IDs.

[0122] Also, for example, information regarding the configuration for requesting transmission of system information (e.g., si-RequestConfig) may be configured for each PLMN ID, and information regarding the periodicity of SIBs (e.g., si-Periodicity) and information regarding the window length of system information (e.g., si-WindowLength) may be configured commonly for multiple PLMN IDs.

[0123] Furthermore, for example, information regarding the window length of system information (e.g., si-WindowLength) may be set for each PLMN ID, and information regarding the periodicity of SIBs (e.g., si-Periodicity) and information regarding the configuration for system information transmission requests (e.g., si-RequestConfig) may be set commonly for multiple PLMN IDs.

[0124] The UE may modify / overwrite at least one of the pieces of information signaled in SIB1 based on the information signaled in the SIB associated with the particular ID.

[0125] According to the fourth embodiment, it is possible to appropriately set system information for each operator.

[0126] <Fifth embodiment> Separate (independent) cell reselection configurations for each specific ID (eg, PLMN ID) may be supported.

[0127] The settings regarding cell reselection and the settings regarding idle mode measurement may be read as interchangeable.

[0128] The UE may receive information regarding the configuration of the RACH that is configured separately for each specific ID.

[0129] The UE may receive specific parameters associated with a particular ID (eg, a PLMN ID).

[0130] The specific parameter may be included in a specific SIB. The specific SIB may be a SIB defined in an existing specification (e.g., SIB3 / 4) or may be SIB X described in the fourth embodiment.

[0131] The specific parameter may be at least one of, for example, information about neighboring cells on the same frequency (intra-frequency) / different frequency (inter-frequency) (e.g., intraFreqNeighCellList / interFreqNeighCellList), information about a list of cells not targeted for cell reselection (e.g., intraFreqBlackCellList / interFreqBlackCellList), information about a list of cells targeted for cell reselection (e.g., intraFreqWhiteCellList / interFreqWhiteCellList), and information about cell reselection settings (e.g., cellReselectionInfoCommon / cellReselectionServingFreqInfo / intraFreqCellReselectionInfo / InterFreqCarrierFreqInfo).

[0132] At least one of the particular parameters may be associated with a particular ID (eg, a PLMN ID).

[0133] Fig. 6 is a diagram showing an example of association related to PLMN IDs in the fifth embodiment. In the example shown in Fig. 6, the correspondence between PLMN IDs and operators is the same as in Fig. 2A etc., but for simplicity, PLMN #3 and operator #3 are omitted.

[0134] In the example shown in Fig. 6, specific SIBs (SIB3 / 4 / 1X) include information on PLMN IDs (e.g., plmn-Identity / plmn-IdentityList) and specific parameters related to cell reselection. The specific parameters may be at least one of information on neighboring cells on the same frequency (intra-frequency) / different frequencies (inter-frequency) (e.g., intraFreqNeighCellList / interFreqNeighCellList), information on a list of cells not targeted for cell reselection (e.g., intraFreqBlackCellList / interFreqBlackCellList), information on a list of cells targeted for cell reselection (e.g., intraFreqWhiteCellList / interFreqWhiteCellList), and information on cell reselection configuration (e.g., cellReselectionInfoCommon / cellReselectionServingFreqInfo / intraFreqCellReselectionInfo / InterFreqCarrierFreqInfo). In the example shown in FIG. 6, all of these parameters are listed, but this listing is merely an example, and the configuration may include at least one of these.

[0135] In the example shown in FIG. 6, specific parameters regarding cell reselection are defined for each PLMN ID (each operator).

[0136] In the configuration shown in FIG. 6, some parameters may be set separately for each PLMN ID, and other parameters may be set commonly to a plurality of PLMN IDs.

[0137] According to the fifth embodiment described above, at least one of cell reselection and measurement in idle mode can be appropriately set for each operator.

[0138] <Modification> The settings / parameters for each specific ID (e.g., PLMN ID) described in each of the above embodiments are merely examples. In addition to the settings / parameters described in each of the above embodiments, any settings / parameters (e.g., broadcast information) for UEs at the time of initial access / in idle mode may be set / notified for each specific ID (e.g., PLMN ID).

[0139] There may be a one-to-one correspondence between a particular ID (e.g., PLMN ID) and a configuration associated with that particular ID, in other words, one configuration may be associated with one particular ID.

[0140] A specific ID (e.g., PLMN ID) and a configuration associated with the specific ID may have a multiple-to-one correspondence. In other words, one configuration may be associated with multiple specific IDs (e.g., a list of specific IDs).

[0141] Furthermore, in each embodiment of the present disclosure, the cell in which network sharing is performed may be a specific cell. For example, the cell in which network sharing is performed may be an SCell, and network sharing may not be performed in a PCell (SpCell). Alternatively, the cell in which network sharing is performed may be a PCell (SpCell), and network sharing may not be performed in an SCell.

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

[0143] 7 is a diagram illustrating an example of a schematic configuration of a wireless communication system according to an embodiment. The wireless communication system 1 may be a system that realizes communication using Long Term Evolution (LTE) or 5th generation mobile communication system New Radio (5G NR) specified by the Third Generation Partnership Project (3GPP).

[0144] The wireless communication system 1 may also 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)), etc.

[0145] 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.

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

[0147] The wireless communication system 1 may include a base station 11 that forms a macrocell C1 with a relatively wide coverage, and base stations 12 (12a-12c) that are located within the macrocell C1 and form small cells C2 that are smaller than the macrocell C1. A user terminal 20 may be located within at least one of the cells. The locations and numbers of the cells and user terminals 20 are not limited to the embodiment shown in the figure. Hereinafter, when there is no need to distinguish between the base stations 11 and 12, they will be collectively referred to as base station 10.

[0148] 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).

[0149] Each CC may be included in at least one of a first frequency band (Frequency Range 1 (FR1)) and a second frequency band (Frequency Range 2 (FR2)). The macro cell C1 may be included in FR1, and the 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 (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 a frequency band higher than FR2.

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

[0151] The multiple base stations 10 may be connected by wire (for example, optical fiber conforming to the Common Public Radio Interface (CPRI), an X2 interface, or the like) or wirelessly (for example, NR communication). For example, when NR communication is used as a backhaul between the base stations 11 and 12, the base station 11 corresponding to the upper station may be called an Integrated Access Backhaul (IAB) donor, and the base station 12 corresponding to the relay station (relay) may be called an IAB node.

[0152] The base station 10 may be connected to the core network 30 directly or via another base station 10. The core network 30 may include, for example, at least one of an Evolved Packet Core (EPC), a 5G Core Network (5GCN), a Next Generation Core (NGC), and the like.

[0153] The user terminal 20 may be a terminal compatible with at least one of communication methods such as LTE, LTE-A, and 5G.

[0154] An Orthogonal Frequency Division Multiplexing (OFDM)-based radio access scheme may be used in the radio communication system 1. 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-FDMA), or the like may be used in at least one of the downlink (DL) and uplink (UL).

[0155] The radio access scheme may also be called a waveform. Note that in the wireless communication system 1, other radio access schemes (for example, other single-carrier transmission schemes, other multi-carrier transmission schemes) may be used as the UL and DL radio access schemes.

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

[0157] Furthermore, in the wireless communication system 1, an uplink shared channel (Physical Uplink Shared Channel (PUSCH)) shared by each user terminal 20, an uplink control channel (Physical Uplink Control Channel (PUCCH)), a random access channel (Physical Random Access Channel (PRACH)), etc. may be used as an uplink channel.

[0158] The PDSCH transmits user data, higher layer control information, System Information Block (SIB), etc. The PUSCH may transmit user data, higher layer control information, etc. Furthermore, the PBCH may transmit Master Information Block (MIB).

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

[0160] Note that the DCI for scheduling the PDSCH may be referred to as a DL assignment, a DL DCI, etc., and the DCI for scheduling the PUSCH may be referred to as an UL grant, a UL DCI, etc. Note that the PDSCH may be interpreted as DL data, and the PUSCH may be interpreted as UL data.

[0161] A control resource set (CORESET) and a search space may be used to detect the PDCCH. The CORESET corresponds to resources to search for DCI. The search space corresponds to a search region and a search method for PDCCH candidates. One CORESET may be associated with one or more search spaces. The UE may monitor a CORESET associated with a certain search space based on the search space configuration.

[0162] One search space may correspond to PDCCH candidates corresponding to one or more aggregation levels. One or more search spaces may be called a search space set. Note that the terms "search space," "search space set," "search space setting," "search space set setting," "CORESET," "CORESET setting," etc. in the present disclosure may be read interchangeably.

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

[0164] In the present disclosure, downlink, uplink, etc. may be expressed without adding "link." Also, various channels may be expressed without adding "Physical" to the beginning.

[0165] 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, 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. may be transmitted as DL-RS.

[0166] 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 the SS (PSS, SSS) and the PBCH (and DMRS for the PBCH) may be referred to as an SS / PBCH block, an SS Block (SSB), or the like. Note that the SS, SSB, and the like may also be referred to as reference signals.

[0167] Furthermore, in the wireless communication system 1, a sounding reference signal (SRS), a demodulation reference signal (DMRS), etc. may be transmitted as an uplink reference signal (UL-RS). Note that the DMRS may also be called a user equipment-specific reference signal (UE-specific reference signal).

[0168] (base station) 8 is a diagram showing an example of the configuration of a base station according to an embodiment. The base station 10 includes a control unit 110, a transceiver unit 120, a transceiver antenna 130, and a transmission line interface 140. Note that the base station may include one or more of each of the control unit 110, the transceiver unit 120, the transceiver antenna 130, and the transmission line interface 140.

[0169] In this example, the functional blocks of the characteristic parts of the present 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 unit described below may be omitted.

[0170] The control unit 110 performs overall control of the base station 10. The control unit 110 can be configured from a controller, a control circuit, and the like that are explained based on common understanding in the technical field to which the present disclosure relates.

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

[0172] The transceiver 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 transceiver unit 120 may be configured with a transmitter / receiver, an RF circuit, a baseband circuit, a filter, a phase shifter, a measurement circuit, a transceiver circuit, etc., which are described based on common understanding in the technical field related to the present disclosure.

[0173] The transmitting / receiving unit 120 may be configured as an integrated transmitting / receiving unit, or may be composed of a transmitting unit and a receiving unit. The transmitting unit may be composed of a transmission processing unit 1211 and an RF unit 122. The receiving unit may be composed of a reception processing unit 1212, an RF unit 122, and a measurement unit 123.

[0174] The transmitting and receiving antenna 130 can be configured from an antenna described based on common understanding in the technical field to which the present disclosure pertains, such as an array antenna.

[0175] The transceiver 120 may transmit the above-mentioned downlink channel, synchronization signal, downlink reference signal, etc. The transceiver 120 may receive the above-mentioned uplink channel, uplink reference signal, etc.

[0176] The transceiver 120 may form at least one of a transmission beam and a reception beam using digital beamforming (for example, precoding), analog beamforming (for example, phase rotation), or the like.

[0177] The transceiver 120 (transmission processing unit 1211) may perform Packet Data Convergence Protocol (PDCP) layer processing, Radio Link Control (RLC) layer processing (e.g., RLC retransmission control), Medium Access Control (MAC) layer processing (e.g., HARQ retransmission control), etc. on data, control information, etc. obtained from the control unit 110, and generate a bit string to be transmitted.

[0178] The transceiver 120 (transmission processor 1211) may perform transmission processing 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 on the bit string to be transmitted, and output a baseband signal.

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

[0180] 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 .

[0181] The transceiver 120 (reception 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 (which may include error correction decoding), MAC layer processing, RLC layer processing, and PDCP layer processing to the acquired baseband signal, thereby acquiring user data, etc.

[0182] The transceiver 120 (measurement unit 123) may perform measurements on 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 measure received power (e.g., Reference Signal Received Power (RSRP)), received 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.

[0183] The transmission path interface 140 may transmit and receive signals (backhaul signaling) between devices included in the core network 30, other base stations 10, etc., and may acquire and transmit user data (user plane data), control plane data, etc. for the user terminal 20.

[0184] The transmitting section and receiving section of the base station 10 in the present disclosure may be configured by at least one of the transmitting / receiving section 120, the transmitting / receiving antenna 130, and the transmission path interface 140.

[0185] The transceiver 120 may transmit configuration information of a serving cell associated with a Public Land Mobile Network (PLMN) ID included in a first system information block (SIB, for example, SIB1). The controller 110 may use the configuration information to indicate at least one of frequency resources and time resources associated with the PLMN ID (first and second embodiments).

[0186] The transceiver 120 may transmit configuration information of a random access channel (RACH) associated with a public land mobile network (PLMN) ID included in a system information block (SIB, for example, SIB1). The controller 110 may use the RACH configuration information to control a random access procedure associated with the PLMN ID (third embodiment).

[0187] The transceiver 120 may transmit configuration information of a second SIB (e.g., an SIB other than SIB1) associated with a Public Land Mobile Network (PLMN) ID included in a first system information block (SIB, e.g., SIB1). The control unit 110 may use the configuration information of the second SIB to control transmission of the second SIB associated with the PLMN ID (fourth and fifth embodiments).

[0188] (user terminal) 9 is a diagram showing an example of the configuration of a user terminal according to one embodiment. The user terminal 20 includes a control unit 210, a transceiver unit 220, and a transceiver antenna 230. Note that the user terminal 20 may include one or more of each of the control unit 210, the transceiver unit 220, and the transceiver antenna 230.

[0189] Note that this example mainly shows functional blocks of the characteristic parts of the present embodiment, 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 unit described below may be omitted.

[0190] The control unit 210 performs overall control of the user terminal 20. The control unit 210 can be configured from a controller, a control circuit, and the like that are explained based on common understanding in the technical field to which the present disclosure relates.

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

[0192] The transceiver 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 transceiver unit 220 may be configured from a transmitter / receiver, an RF circuit, a baseband circuit, a filter, a phase shifter, a measurement circuit, a transceiver circuit, etc., which are described based on common understanding in the technical field related to the present disclosure.

[0193] The transmitting / receiving unit 220 may be configured as an integrated transmitting / receiving unit, or may be composed of a transmitting unit and a receiving unit. The transmitting unit may be composed of a transmission processing unit 2211 and an RF unit 222. The receiving unit may be composed of a reception processing unit 2212, an RF unit 222, and a measurement unit 223.

[0194] The transmitting / receiving antenna 230 can be configured as an antenna described based on common understanding in the technical field to which the present disclosure pertains, such as an array antenna.

[0195] The transceiver 220 may receive the above-mentioned downlink channel, synchronization signal, downlink reference signal, etc. The transceiver 220 may transmit the above-mentioned uplink channel, uplink reference signal, etc.

[0196] The transceiver 220 may form at least one of a transmission beam and a reception beam using digital beamforming (for example, precoding), analog beamforming (for example, phase rotation), or the like.

[0197] The transceiver 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, control information, etc. obtained from the control unit 210, and generate a bit string to be transmitted.

[0198] The transceiver 220 (transmission processor 2211) may perform transmission processing 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 on the bit string to be transmitted, and output a baseband signal.

[0199] Whether or not to apply DFT processing may be based on the setting of transform precoding. When transform precoding is enabled for a certain channel (e.g., PUSCH), the transceiver unit 220 (transmission processing unit 2211) may perform DFT processing as the transmission processing to transmit the channel using a DFT-s-OFDM waveform, and when transform precoding is not enabled, the transceiver unit 220 may not perform DFT processing as the transmission processing.

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

[0201] 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.

[0202] The transceiver 220 (reception processing unit 2212) may apply reception processing such as analog-to-digital conversion, FFT processing, IDFT processing (if necessary), filtering, demapping, demodulation, decoding (which 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.

[0203] The transceiver 220 (measurement unit 223) may perform measurements on the received signal. For example, the measurement unit 223 may perform RRM measurement, CSI measurement, etc. based on the received signal. The measurement unit 223 may 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.

[0204] The transmitting section and receiving section of the user terminal 20 in the present disclosure may be configured by at least one of the transmitting / receiving section 220 and the transmitting / receiving antenna 230.

[0205] The transceiver 220 may receive configuration information of a serving cell associated with a Public Land Mobile Network (PLMN) ID included in a first system information block (SIB, for example, SIB1). The controller 210 may determine at least one of frequency resources and time resources associated with the PLMN ID based on the configuration information (first and second embodiments).

[0206] The frequency resource may be at least one of an initial downlink bandwidth portion and an initial uplink bandwidth portion. The frequency resource may be an initial downlink bandwidth portion and an initial uplink bandwidth portion (first embodiment).

[0207] The time resource may be a resource based on uplink / downlink configuration of time division duplexing (second embodiment).

[0208] The control unit 210 may control monitoring of the separate system information block based on information about the second SIB included in the setting information (first embodiment).

[0209] The transceiver 220 may receive configuration information of a random access channel (RACH) associated with a public land mobile network (PLMN) ID, which is included in a system information block (SIB, for example, SIB1). The controller 210 may control a random access procedure associated with the PLMN ID based on the configuration information of the RACH (third embodiment).

[0210] The RACH configuration information may be included in information about an initial uplink bandwidth portion. The information about the initial uplink bandwidth portion may include the PLMN ID (third embodiment).

[0211] The RACH configuration information may include the PLMN ID and at least one of information regarding the configuration of time resources and formats of a physical random access channel (PRACH), information regarding the starting position of frequency resources of the PRACH, and information regarding a sequence of the PRACH (third embodiment).

[0212] The control unit 210 may report the PLMN ID of the terminal using the RACH (third embodiment).

[0213] The transceiver 220 may receive configuration information of a second SIB (e.g., an SIB other than SIB1) associated with a Public Land Mobile Network (PLMN) ID, which is included in a first system information block (SIB, e.g., SIB1). The controller 210 may control monitoring of the second SIB associated with the PLMN ID based on the configuration information of the second SIB (fourth and fifth embodiments).

[0214] The configuration information of the second SIB may include at least one of information regarding the periodicity of the second SIB, information regarding the window length of the second SIB, and information regarding the configuration for a transmission request of system information (fourth embodiment).

[0215] The control unit 210 may change at least one of the settings based on the first SIB using the settings based on the second SIB (fourth embodiment).

[0216] The second SIB may include information regarding cell reselection (fifth embodiment).

[0217] (Hardware configuration) The block diagrams used to explain the above embodiments show functional blocks. These functional blocks (components) are realized by any combination of at least one of hardware and software. Furthermore, the method for realizing each functional block is not particularly limited. That is, each functional block may be realized using a single device that is physically or logically coupled, or may be realized using two or more physically or logically separated devices that are directly or indirectly connected (for example, using wires, wirelessly, etc.) and these multiple devices. The functional block may also be realized by combining the single device or multiple devices with software.

[0218] Here, the functions include, but are not limited to, judgment, determination, judgment, calculation, computation, processing, derivation, investigation, search, confirmation, reception, transmission, output, access, resolution, selection, election, establishment, comparison, assumption, expectation, deeming, broadcasting, notifying, communicating, forwarding, configuring, reconfiguring, allocating, mapping, and assignment. For example, a functional block (component) that performs transmission may be called a transmitting unit, transmitter, etc. As mentioned above, the implementation method of each is not particularly limited.

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

[0220] In this disclosure, terms such as apparatus, circuit, device, section, unit, etc. may be read interchangeably. The hardware configurations of the base station 10 and the user terminal 20 may be configured to include one or more of the devices shown in the drawings, or may be configured to exclude some of the devices.

[0221] For example, although only one processor 1001 is shown, there may be multiple processors. Furthermore, processing may be performed by one processor, or processing may be performed by two or more processors simultaneously, serially, or in other ways. Furthermore, processor 1001 may be implemented by one or more chips.

[0222] 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 a processor 1001 and a memory 1002, causing the processor 1001 to perform calculations, control communication via the communication device 1004, and control at least one of reading and writing data in the memory 1002 and the storage 1003.

[0223] The processor 1001, for example, runs an operating system to control the entire computer. The processor 1001 may be configured as a central processing unit (CPU) including an interface with peripheral devices, a control device, an arithmetic unit, a register, etc. For example, at least a part of the above-mentioned control unit 110 (210), transmission / reception unit 120 (220), etc. may be realized by the processor 1001.

[0224] The processor 1001 also reads programs (program codes), 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 in accordance with these. The programs used are those that cause a computer to execute at least some of the operations described in the above-described embodiments. For example, the control unit 110 (210) may be realized by a control program stored in the memory 1002 and running on the processor 1001, and the other functional blocks may be realized in a similar manner.

[0225] The memory 1002 is a computer-readable recording medium and may be configured by at least one of, for example, a read-only memory (ROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), a random access memory (RAM), or other suitable storage medium. The memory 1002 may also be referred to as a register, a cache, a main memory, or the like. The memory 1002 may store executable programs (program codes), software modules, and the like for implementing a wireless communication method according to an embodiment of the present disclosure.

[0226] Storage 1003 is a computer-readable recording medium and may be constituted by at least one of, for example, a flexible disk, a floppy disk, a magneto-optical disk (e.g., a compact disc (e.g., a Compact Disc ROM (CD-ROM)), a digital versatile disc, a Blu-ray disc), 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. Storage 1003 may also be referred to as a secondary storage device.

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

[0228] The input device 1005 is an input device (for example, a keyboard, a mouse, a microphone, a switch, a button, a sensor, etc.) that receives input from the outside. The output device 1006 is an output device (for example, a display, a speaker, a light emitting diode (LED) lamp, etc.) that outputs to the outside. The input device 1005 and the output device 1006 may be integrated into one device (for example, a touch panel).

[0229] 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 may be configured using different buses between each device.

[0230] 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), or a field programmable gate array (FPGA), and some or all of the functional blocks may be realized using such hardware. For example, the processor 1001 may be implemented using at least one of these pieces of hardware.

[0231] (Variation) Note that terms explained in the present disclosure and terms necessary for understanding the present disclosure may be replaced with terms having the same or similar meanings. For example, a channel, a symbol, and a signal (signal or signaling) may be interchangeable. A signal may also be a message. A reference signal may be abbreviated as RS, and may also be called a pilot, pilot signal, etc. depending on the applicable standard. A component carrier (CC) may also be called a cell, frequency carrier, carrier frequency, etc.

[0232] A radio frame may be composed of one or more periods (frames) in the time domain. Each of the one or more periods (frames) constituting a radio frame may be called a subframe. Furthermore, a subframe may be composed 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.

[0233] Here, the numerology may be a communication parameter applied to at least one of transmission and reception of a signal or channel, and may indicate at least one of, for example, a subcarrier spacing (SCS), a bandwidth, a symbol length, a cyclic prefix length, a transmission time interval (TTI), the number of symbols per TTI, a radio frame structure, a specific filtering process performed by a transceiver in the frequency domain, and a specific windowing process performed by a transceiver in the time domain.

[0234] A slot may be composed of one or more symbols in the time domain (such as an Orthogonal Frequency Division Multiplexing (OFDM) symbol or a Single Carrier Frequency Division Multiple Access (SC-FDMA) symbol), and may be a time unit based on numerology.

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

[0236] A radio frame, a subframe, a slot, a minislot, and a symbol all represent time units for transmitting signals. The radio frame, the subframe, the slot, the minislot, and the symbol may be referred to by other names corresponding to the radio frame, the subframe, the slot, the minislot, and the symbol. Note that the time units such as a frame, a subframe, a slot, a minislot, and a symbol in the present disclosure may be interchangeable.

[0237] For example, one subframe may be referred to as a TTI, or multiple consecutive subframes may be referred to as a TTI, or one slot or one minislot may be referred to as a TTI. That is, at least one of a subframe and a TTI may be a subframe (1 ms) in existing LTE, a period shorter than 1 ms (for example, 1-13 symbols), or a period longer than 1 ms. Note that the unit representing the TTI may be called a slot, minislot, etc., instead of a subframe.

[0238] Here, TTI refers to, for example, the smallest time unit for scheduling in wireless communication. For example, in an LTE system, a base station performs scheduling to allocate radio resources (such as frequency bandwidth and transmission power that can be used by each user terminal) to each user terminal in TTI units. However, the definition of TTI is not limited to this.

[0239] The TTI may be a transmission time unit for a channel-encoded data packet (transport block), a code block, a code word, etc., or may be a processing unit for scheduling, link adaptation, etc. When a TTI is given, the time interval (e.g., the number of symbols) to which a transport block, a code block, a code word, etc. is actually mapped may be shorter than the TTI.

[0240] When one slot or one minislot is called a TTI, one or more TTIs (i.e., one or more slots or one or more minislots) may be the minimum time unit for scheduling. Also, the number of slots (minislots) constituting the minimum time unit for scheduling may be controlled.

[0241] A TTI having a time length of 1 ms may be called a regular TTI (TTI in 3GPP Rel. 8-12), normal TTI, long TTI, regular subframe, normal subframe, long subframe, slot, etc. A TTI shorter than a regular TTI may be called a shortened TTI, short TTI, partial or fractional TTI, shortened subframe, short subframe, minislot, subslot, slot, etc.

[0242] In addition, a long TTI (e.g., a normal TTI, a subframe, etc.) may be interpreted as a TTI having a time length of more than 1 ms, and a short TTI (e.g., a shortened TTI, etc.) may be interpreted as a TTI having a TTI length shorter than the TTI length of a long TTI and equal to or greater than 1 ms.

[0243] A resource block (RB) is a resource allocation unit in the time domain and the frequency domain, and may include one or more consecutive subcarriers in the frequency domain. The number of subcarriers included in an RB may be the same regardless of numerology, for example, 12. The number of subcarriers included in an RB may also be determined based on numerology.

[0244] In addition, an RB may include one or more symbols in the time domain and may have a length of one slot, one minislot, one subframe, or one TTI. One TTI, one subframe, etc. may each be composed of one or more resource blocks.

[0245] Note that one or more RBs may also be called a physical resource block (PRB), a sub-carrier group (SCG), a resource element group (REG), a PRB pair, an RB pair, etc.

[0246] Furthermore, a resource block may be composed of one or more resource elements (REs). For example, one RE may be a radio resource region of one subcarrier and one symbol.

[0247] A Bandwidth Part (BWP), which may also be referred to as a fractional bandwidth, may represent a subset of contiguous common resource blocks (RBs) for a given numerology on a given carrier, where the common RBs may be identified by their index relative to a common reference point of the carrier. PRBs may be defined in a given BWP and numbered within that BWP.

[0248] The BWP may include an UL BWP (a BWP for UL) and a DL BWP (a BWP for DL). One or more BWPs may be configured for a UE within one carrier.

[0249] At least one of the configured BWPs may be active, and the UE may not expect to transmit or receive a given signal / channel outside the active BWP. Note that the terms "cell," "carrier," etc. in this disclosure may be read as "BWP."

[0250] The above-described structures of radio frames, subframes, slots, minislots, symbols, etc. are merely examples. For example, the number of subframes included in a radio frame, the number of slots per subframe or radio 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, the number of symbols in a TTI, the symbol length, the cyclic prefix (CP) length, etc. may be changed in various ways.

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

[0252] The names used for parameters and the like in this disclosure are not intended to be limiting in any way. Furthermore, the mathematical expressions and the like using these parameters may differ from those explicitly disclosed in this disclosure. The various channels (PUCCH, PDCCH, etc.) and information elements may be identified by any suitable names, and therefore the various names assigned to these various channels and information elements are not intended to be limiting in any way.

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

[0254] Furthermore, information, signals, etc. may be output from a higher layer to a lower layer and / or from a lower layer to a higher layer. Information, signals, etc. may be input / output via multiple network nodes.

[0255] Input and output information, signals, etc. may be stored in a specific location (for example, memory) or may be managed using a management table. Input and output information, signals, etc. may be overwritten, updated, or added. Output information, signals, etc. may be deleted. Input information, signals, etc. may be transmitted to another device.

[0256] Notification of information is not limited to the aspects / embodiments described in the present disclosure, and may be performed using other methods. For example, notification of information in the present disclosure may be performed by physical layer signaling (e.g., Downlink Control Information (DCI) and Uplink Control Information (UCI)), higher layer signaling (e.g., Radio Resource Control (RRC) signaling, broadcast information (Master Information Block (MIB) and System Information Block (SIB)), Medium Access Control (MAC) signaling), other signals, or a combination thereof.

[0257] Note that the physical layer signaling may be called Layer 1 / Layer 2 (L1 / L2) control information (L1 / L2 control signal), L1 control information (L1 control signal), etc. Furthermore, the RRC signaling may be called an RRC message, such as an RRC connection setup message or an RRC connection reconfiguration message. Furthermore, the MAC signaling may be notified using, for example, a MAC Control Element (CE).

[0258] Furthermore, notification of specified information (e.g., notification that "it is X") is not limited to explicit notification, but may be made implicitly (e.g., by not notifying the specified information or by notifying other information).

[0259] The determination may be made by a value represented by one bit (0 or 1), by a Boolean value represented by true or false, or by a comparison of numerical values ​​(e.g., comparison with a predetermined value).

[0260] Software shall be construed broadly to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, threads of execution, procedures, functions, etc., whether referred to as software, firmware, middleware, microcode, hardware description language, or otherwise.

[0261] Software, instructions, information, etc. may also be transmitted or received over a transmission medium. For example, if software is transmitted from a website, server, or other remote source using wired technologies (such as coaxial cable, fiber optic cable, twisted pair, Digital Subscriber Line (DSL)), and / or wireless technologies (such as infrared, microwave), then these wired and / or wireless technologies are included within the definition of transmission media.

[0262] As used in this disclosure, the terms "system" and "network" may be used interchangeably. A "network" may refer to devices included in the network (e.g., base stations).

[0263] In the present 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," "antenna port group," "layer," "number of layers," "rank," "resource," "resource set," "resource group," "beam," "beam width," "beam angle," "antenna," "antenna element," "panel," etc. may be used interchangeably.

[0264] In this disclosure, terms such as "base station (BS)," "radio 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," "component carrier," etc. may be used interchangeably. Base stations may also be referred to by terms such as macrocell, small cell, femtocell, picocell, etc.

[0265] A base station can accommodate one or more (e.g., three) cells. When a base station accommodates multiple cells, the overall coverage area of ​​the base station can be divided into multiple smaller areas, and each smaller area can be provided with communication service by a base station subsystem (e.g., a small indoor base station (Remote Radio Head (RRH))). The term "cell" or "sector" refers to a part or the entire coverage area of ​​a base station and / or base station subsystem that provides communication service within this coverage.

[0266] In this disclosure, the terms "Mobile Station (MS)," "user terminal," "User Equipment (UE)," "terminal," etc. may be used interchangeably.

[0267] A mobile station may also be referred to as 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 suitable terminology.

[0268] 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. Note that at least one of the base station and the mobile station may be a device mounted on a moving object, the moving object itself, etc.

[0269] The mobile body is a movable object that can move at any speed and naturally includes cases where the mobile body is stationary. Examples of the mobile body include, but are not limited to, vehicles, transport vehicles, automobiles, motorcycles, bicycles, connected cars, excavators, bulldozers, wheel loaders, dump trucks, forklifts, trains, buses, handcars, rickshaws, ships and other watercraft, airplanes, rockets, satellites, drones, multicopters, quadcopters, balloons, and objects mounted thereon. The mobile body may also be a mobile body that moves autonomously based on an operation command.

[0270] The mobile object may be a vehicle (e.g., a car, an airplane, etc.), an unmanned mobile object (e.g., a drone, an autonomous vehicle, etc.), or a robot (manned or unmanned). Note that at least one of the base station and the mobile station may also include devices that do 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.

[0271] 11 is a diagram showing an example of a vehicle according to an embodiment. A 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, axles 48, an electronic control unit 49, various sensors (including a current sensor 50, an RPM sensor 51, an air 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.

[0272] The drive unit 41 is configured with at least one of an engine, a motor, and a hybrid of an engine and a motor, for example. 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.

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

[0274] The signals from the various sensors 50-58 include a current signal from a current sensor 50 that senses the current of the motor, a rotation speed signal of the front wheels 46 / rear wheels 47 obtained by a rotation speed sensor 51, an air pressure signal of the front wheels 46 / rear wheels 47 obtained by an air pressure sensor 52, a vehicle speed signal obtained by a vehicle speed sensor 53, an acceleration signal obtained by an acceleration sensor 54, a depression amount signal of the accelerator pedal 43 obtained by an accelerator pedal sensor 55, a depression amount signal of the brake pedal 44 obtained by a brake pedal sensor 56, an operation signal of the shift lever 45 obtained by a shift lever sensor 57, and a detection signal for detecting obstacles, vehicles, pedestrians, etc. obtained by an object detection sensor 58.

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

[0276] The information service unit 59 may include input devices (e.g., keyboards, mice, microphones, switches, buttons, sensors, touch panels, etc.) that accept input from the outside, and may also include output devices (e.g., displays, speakers, LED lamps, touch panels, etc.) that output to the outside.

[0277] The driving assistance system unit 64 is configured with various devices that provide functions for preventing accidents and reducing the driver's driving burden, 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 Units (IMUs), Inertial Navigation Systems (INSs)), Artificial Intelligence (AI) chips, and AI processors, as well as one or more ECUs that control these devices. The driving assistance system unit 64 also transmits and receives various information via the communication module 60 to realize driving assistance functions or autonomous driving functions.

[0278] 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 transmits and receives data (information) via the communication port 63 to and from 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, axles 48, the microprocessor 61 and memory (ROM, RAM) 62 in the electronic control unit 49, and the various sensors 50-58, which are provided in the vehicle 40.

[0279] 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 an external device. For example, it transmits and receives various information to and from the external device 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 above-mentioned base station 10 or user terminal 20. Furthermore, the communication module 60 may be, for example, at least one of the above-mentioned base station 10 and user terminal 20 (or may function as at least one of the base station 10 and user terminal 20).

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

[0281] The communication module 60 receives various information (traffic information, traffic signal information, vehicle distance information, etc.) transmitted from external devices and displays it on an information service unit 59 provided in the vehicle. The information service unit 59 may also be called an output unit that outputs information (for example, outputs information to a device such as a display or speaker based on the PDSCH received by the communication module 60 (or data / information decoded from the PDSCH)).

[0282] 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, axles 48, various sensors 50-58, and the like provided in the vehicle 40.

[0283] Furthermore, a base station in the present disclosure may be read as a user terminal. For example, the aspects / embodiments of the present 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) or Vehicle-to-Everything (V2X)). In this case, the user terminal 20 may be configured to have the functions of the base station 10 described above. Furthermore, terms such as "uplink" and "downlink" may be read as terms corresponding to terminal-to-terminal communication (for example, "sidelink"). For example, terms such as uplink channel and downlink channel may be read as sidelink channel.

[0284] Similarly, the user terminal in the present disclosure may be read as a base station, in which case the base station 10 may be configured to have the functions of the user terminal 20 described above.

[0285] In the present disclosure, an operation described as being performed by a base station may be performed by its upper node in some cases. It is apparent that in a network including one or more network nodes having a base station, various operations performed for communication with a terminal may be performed by the base station, one or more network nodes other than the base station (such as, but not limited to, a Mobility Management Entity (MME) and a Serving-Gateway (S-GW)), or a combination thereof.

[0286] Each aspect / embodiment described in this disclosure may be used alone, in combination, or switched depending on the implementation. Furthermore, the order of the processing procedures, sequences, flowcharts, etc. of each aspect / embodiment described in this disclosure may be changed unless inconsistent. For example, the methods described in this disclosure present elements of various steps using an example order, and are not limited to the specific order presented.

[0287] Each aspect / embodiment described in the present disclosure may be a technology other than 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 (x is, for example, an integer or decimal number)), 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 (registered trademark)), CDMA2000, Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi (registered trademark)), IEEE 802.16 (WiMAX (registered trademark)), IEEE The present invention may be applied to systems that use 802.20, Ultra-WideBand (UWB), Bluetooth (registered trademark), or other appropriate wireless communication methods, or to next-generation systems that are expanded, modified, created, or defined based on these. It may also be applied to a combination of multiple systems (e.g., a combination of LTE or LTE-A and 5G).

[0288] As used in this disclosure, the phrase "based on" does not mean "based only on," unless expressly stated otherwise. In other words, the phrase "based on" means both "based only on" and "based at least on."

[0289] As used in this disclosure, any reference to an element using a designation such as "first," "second," etc. does not generally limit the quantity or order of those elements. These designations may be used in this disclosure as a convenient method of distinguishing between two or more elements. Thus, a reference to a first and a second element does not imply that only two elements may be employed or that the first element must in some way precede the second element.

[0290] The term "determining," as used in this disclosure, may encompass a wide variety of actions. For example, "determining" may be considered to be judging, calculating, computing, processing, deriving, investigating, looking up, search, inquiry (e.g., looking up in a table, database, or another data structure), ascertaining, etc.

[0291] Additionally, "determining" may be considered to be "determining" receiving (e.g., receiving information), transmitting (e.g., sending information), input, output, accessing (e.g., accessing data in memory), etc.

[0292] Also, "decision" may be considered to be "deciding" resolving, selecting, choosing, establishing, comparing, etc. In other words, "decision" may be considered to be "deciding" on some action.

[0293] Furthermore, "judgment (decision)" may be interpreted as "assuming," "expecting," "considering," or the like.

[0294] As used in this disclosure, the terms "connected," "coupled," or any variation thereof, refer to any direct or indirect connection or coupling between two or more elements, and may include the presence of one or more intermediate elements between two elements that are "connected" or "coupled" to each other. The coupling or connection between elements may be physical, logical, or a combination thereof. For example, "connected" may be read as "access."

[0295] In this disclosure, when two elements are connected, they may be considered to be "connected" or "coupled" to one another using one or more wires, cables, printed electrical connections, etc., as well as using electromagnetic energy having wavelengths in the radio frequency range, microwave range, light (both visible and invisible) range, etc., as some non-limiting and non-exhaustive examples.

[0296] In the present 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 "coupled" may also be interpreted in the same way as "different."

[0297] When used in this disclosure, the terms "include," "including," and variations thereof are intended to be inclusive, similar to the term "comprising." Furthermore, when used in this disclosure, the term "or" is not intended to be an exclusive or.

[0298] In this disclosure, where articles are added by translation, such as a, an, and the in English, the disclosure may include that the nouns following these articles are in the plural form.

[0299] Although the invention according to the present disclosure has been described in detail above, it is clear to those skilled in the art that the invention according to the present disclosure is not limited to the embodiments described in the present disclosure. The invention according to the present disclosure can be implemented in modified and altered forms without departing from the spirit and scope of the invention as defined by the description of the claims. Therefore, the description of the present disclosure is intended to be illustrative and explanatory and does not impose any limiting meaning on the invention according to the present disclosure.

Claims

1. A receiving unit that receives configuration information of a second system information block (SIB) included in a first SIB; A terminal having a control unit that controls monitoring of the second SIB based on setting information of the second SIB.

2. receiving configuration information of a second system information block (SIB) included in a first SIB; and controlling monitoring of the second SIB based on the configuration information of the second SIB.

3. A transmitter that transmits configuration information of a second system information block (SIB) included in a first SIB; A base station comprising: a control unit that controls transmission of the second SIB using configuration information of the second SIB.

Images