WO2023100351A1

WO2023100351A1 - Terminal, radio communication method, and base station

Info

Publication number: WO2023100351A1
Application number: PCT/JP2021/044480
Authority: WO
Inventors: 浩樹原田; 真由子岡野; 慎也熊谷; 聡永田
Original assignee: 株式会社Ｎｔｔドコモ
Priority date: 2021-12-03
Filing date: 2021-12-03
Publication date: 2023-06-08

Abstract

A terminal according to an aspect of this disclosure includes a reception unit that receives configuration information for a second system information block (SIB) that is associated with a Public Land Mobile Network (PLMN) ID and included in a first SIB and a control unit that controls monitoring of the second SIB associated with the PLMN ID on the basis of the configuration information for the second SIB. An aspect of this disclosure enables flexible operations of communications among operators.

Description

Terminal, wireless communication method and base station

The present disclosure relates to terminals, wireless communication methods, and base stations in next-generation mobile communication systems.

In the Universal Mobile Telecommunications System (UMTS) network, Long Term Evolution (LTE) has been specified for the purpose of further high data rate, low delay, etc. (Non-Patent Document 1). In addition, LTE-Advanced (3GPP Rel. 10-14) has been specified for the purpose of further increasing the capacity and sophistication of LTE (Third Generation Partnership Project (3GPP) Release (Rel.) 8, 9).

LTE successor systems (for example, 5th generation mobile communication system (5G), 5G+ (plus), 6th generation mobile communication system (6G), New Radio (NR), 3GPP Rel. 15 and later) are also being considered. .

In future wireless communication systems (for example, after Rel. 18), resource sharing is being considered for the purpose of improving the efficiency of using frequency bands (existing frequency bands and new high frequency bands).

However, there are cases where settings for specific UEs cannot be changed between multiple operators. In such a case, communication cannot be operated flexibly for each carrier, and there is a risk that improvement in communication quality will be suppressed.

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 operation between operators.

A terminal according to an aspect of the present disclosure includes a receiving unit that receives setting information of a second SIB associated with a Public Land Mobile Network (PLMN) ID, which is included in a first system information block (SIB); and a control unit that controls monitoring of the second SIB associated with the PLMN ID based on setting information of the second SIB.

According to one aspect of the present disclosure, it is possible to flexibly operate communication between operators.

1A-1D are diagrams illustrating an example of network sharing. FIGS. 2A and 2B are diagrams showing an example of PLMN ID associations in the first embodiment. FIGS. 3A and 3B are diagrams showing an example of PLMN ID associations in the second embodiment. FIGS. 4A and 4B are diagrams showing an example of PLMN ID associations in the third embodiment. FIG. 5 is a diagram showing an example of PLMN ID associations in the fourth embodiment. FIG. 6 is a diagram showing an example of PLMN ID associations in the fifth embodiment. FIG. 7 is a diagram illustrating an example of a schematic configuration of a radio communication system according to an embodiment. FIG. 8 is a diagram illustrating an example of the configuration of a base station according to one embodiment. FIG. 9 is a diagram illustrating an example of the configuration of a user terminal according to one embodiment. FIG. 10 is a diagram illustrating an example of hardware configurations of a base station and a user terminal according to one embodiment. FIG. 11 is a diagram illustrating an example of a vehicle according to one embodiment;

(resource sharing)
In future wireless communication systems (for example, after Rel. 18), resource sharing is being studied for the purpose of highly efficient use of frequency bands (existing frequency bands and new high frequency bands).

In resource sharing, a radio access network (RAN) is shared by multiple operators (operators), the network (NW, e.g., base station) investment cost is divided for each operator, and multiple base stations are used. station can be set up.

For example, by sharing an antenna site (land/steel tower, etc.) among multiple operators, the station installation cost can be shared among the multiple operators.

In addition, by sharing distributed nodes (e.g., Distributed Unit (DU))/aggregated nodes (e.g., Central Unit (CU)) among multiple operators (e.g., sharing hardware infrastructure), equipment costs can be can be shared among operators.

In addition, by sharing a frequency/antenna unit (for example, Radio Unit (RU)) among multiple operators, resources that are not being used by one operator can be used by other operators, etc. can improve the utilization efficiency of

　Figures 1A to 1D are diagrams showing an example of network sharing.

Fig. 1A shows an example of site sharing. As shown in FIG. 1A, in site sharing, multiple operators share an antenna site. On the other hand, for service platforms, HSS (Home Subscriber Server) / HLR (Home Location Register), Core Network (CN) Packet Switching (PS), base stations, and cells/frequencies, multiple Each operator is independent.

FIG. 1B shows an example of MORAN (Multi Operator RAN). As shown in FIG. 1B, in MORAN, multiple operators share antenna sites as well as a portion of a base station (eg, base station hardware). On the other hand, the service platform, HSS/HLR, CNPS, other parts of the base station (eg, base station software), and cells/frequencies are independent for multiple operators.

FIG. 1C shows an example of MOCN (Multi Operator Core Network). As shown in FIG. 1C, in MOCN, multiple operators share base stations and cells/frequencies. On the other hand, service platforms, HSS/HLR, and CNPS are independent for multiple operators.

FIG. 1D shows an example of a GWCN (Gateway Core Network). As shown in FIG. 1D, in a GWCN, multiple operators share CNPS, base stations and cells/frequencies. On the other hand, the service platform and HSS/HLR are independent for each of multiple carriers.

In MOCN/GWCN, since cells are shared by multiple operators, settings must be made for each operator (for example, for each ID (PLMN ID) related to the Public Land Mobile Network (PLMN)). It is desirable to be able to change.

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

On the other hand, for terminals in the RRC connected state (user terminal, User Equipment (UE)), according to the PLMN ID of the terminal, the operator-specific settings are set as RRC settings can be set. Specifically, in resource sharing, if it is desired that only terminals of a specific operator can use a part of the time resources of a shared cell, terminals of other operators should not use the part of the time resources. can be set.

However, in existing specifications, many of the settings (eg, broadcast information, etc.) for specific UEs (eg, initial access/idle mode UE) are not given for each operator (eg, PLMN ID). , the inability to change settings between multiple operators. For example, parameters used for random access channel (RACH) resource configuration (for example, ServingCellConfigCommonSIB) in system information block 1 (SIB1) are not given for each PLMN ID, so the UE's RACH resource can be used by the business It cannot be set/changed for each user.

In this way, if settings for a specific UE cannot be changed between multiple operators, flexible communication operation cannot be performed for each operator, and there is a risk of suppressing improvement in communication quality.

Therefore, the inventors came up with the idea of a flexible operation policy/parameter application/setting method between operators for efficient station placement/frequency utilization through resource sharing.

Hereinafter, embodiments according to the present disclosure will be described in detail with reference to the drawings. The wireless communication method according to each embodiment may be applied independently, or may be applied in combination.

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

In the present disclosure, activate, deactivate, indicate (or indicate), select, configure, update, determine, etc. may be read interchangeably. In the present disclosure, supporting, controlling, controllable, operating, capable of operating, etc. may be read interchangeably.

In the present disclosure, Radio Resource Control (RRC), RRC parameters, RRC messages, higher layer parameters, information elements (IEs), settings, etc. may be read interchangeably. In the present disclosure, Medium Access Control control element (MAC Control Element (CE)), update command, activation/deactivation command, etc. may be read interchangeably.

In the present disclosure, higher layer signaling may be, for example, Radio Resource Control (RRC) signaling, Medium Access Control (MAC) signaling, broadcast information, or a combination thereof.

In the present disclosure, MAC signaling may use, for example, MAC Control Element (MAC CE), MAC Protocol Data Unit (PDU), and the like. Broadcast information includes, for example, Master Information Block (MIB), System Information Block (SIB), Remaining Minimum System Information (RMSI), and other system information ( It may be Other System Information (OSI).

In the present disclosure, the physical layer signaling may be, for example, downlink control information (DCI), uplink control information (UCI), or the like.

In the present disclosure, indices, identifiers (ID), indicators, resource IDs, etc. may be read interchangeably. In the present disclosure, sequences, lists, sets, groups, groups, clusters, subsets, etc. may be read interchangeably.

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

In the present disclosure, PLMN, operator, operator, operator policy, setting for each operator, setting for each operator, etc. may be read interchangeably.

(Wireless communication method)
In the present disclosure, the PLMN ID will be described as an example of the specific ID, but the name of the specific ID is not limited to this.

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

<First Embodiment>
Separate (independent) configuration of frequency/time resources for each specific ID (eg, PLMN ID) may be supported.

The UE may receive information on frequency/time resources configured separately for each specific ID.

The frequency/time resource may be, for example, a frequency resource configured for the UE during initial access. The frequency/time resource may be the initial DL/UL Bandwidth Part (BWP).

Information about the specific frequency/time resource may be included in serving cell configuration information (eg, ServingCellConfigCommonSIB) included in broadcast information (eg, system information (eg, SIB/SIB1)). Information on the specific frequency / time resource, included in the configuration information (e.g., ServingCellConfigCommonSIB) of the serving cell included in the system information, DL configuration (e.g., downlinkConfigCommon / DownlinkConfigCommonSIB), UL configuration (e.g., uplinkConfigCommon / UplinkConfigCommonSIB), and , supplementary UL (supplementaryUplink/UplinkConfigCommonSIB).

The information on the specific frequency/time resource is, for example, at least one of information on the initial DL BWP (eg initialDownlinkBWP/BWP-DownlinkCommon) and information on the initial UL BWP (eg initialUplinkBWP/BWP-UplinkCommon). may

Information about the specific frequency/time resource may be associated with a specific ID (eg, PLMN ID).

For example, the serving cell configuration information (eg, ServingCellConfigCommonSIB) included in the system information (eg, SIB/SIB1) may include information about one or more specific IDs (eg, PLMN ID).

In the present disclosure, information about multiple specific IDs may be information indicating a list of specific IDs.

For example, DL configuration (e.g., downlinkConfigCommon/DownlinkConfigCommonSIB), UL configuration (e.g., uplinkConfigCommon/UplinkConfigCommonSIB), and supplementary UL (supplementaryUplink/UplinkConfigCommonSIB) included in the serving cell configuration information (e.g., ServingCellConfigCommonSIB) included in the system information , may include information about one or more specific IDs (eg, PLMN IDs).

The UE may determine specific frequency resource configuration for each specific ID based on a specific ID (eg, PLMN ID) included in SIB/SIB1.

The number of frequency resources (eg, BWP) that can be set for each specific ID (maximum number, eg, 1) may be defined in the specifications. An upper limit (eg, maxPLMN) on the number (total number) of frequency resources (eg, BWPs) for different specific IDs may be defined in the specification.

FIG. 2A is a diagram showing an example of PLMN ID associations in the first embodiment. In the example shown in FIG. 2A, operator #1 with PLMN ID #1, operator #2 with PLMN ID #2, and operator #3 with PLMN ID #3 are defined. In addition, in the present disclosure, the values and numbers of PLMN IDs and numbers and numbers of operators are merely examples, and are not limited to the examples shown in each drawing.

In the example shown in FIG. 2A, ServingCellConfigCommonSIB contains information on PLMN IDs (eg, plmn-Identity/plmn-IdentityList). That is, ServingCellConfigCommonSIB is defined for each PLMN ID (for each operator). In other words, DownlinkConfigCommonSIB, UplinkConfigCommonSIB, initialDownlinkBWP included in DownlinkConfigCommonSIB, and initialUplinkBWP included in UplinkConfigCommonSIB, which are included in ServingCellConfigCommonSIB, are specified for each PLMN ID (for each operator).

FIG. 2B is a diagram showing another example of association regarding 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.

In the example shown in FIG. 2B, information on PLMN IDs (eg, plmn-Identity/plmn-IdentityList) is included in DownlinkConfigCommonSIB and UplinkConfigCommonSIB. That is, DownlinkConfigCommonSIB and UplinkConfigCommonSIB are defined for each PLMN ID (for each operator). That is, initialDownlinkBWP included in DownlinkConfigCommonSIB and initialUplinkBWP included in UplinkConfigCommonSIB are defined for each PLMN ID (for each operator).

It should be noted that, in the configurations shown in FIGS. 2A and 2B, a certain parameter may be set separately for each PLMN ID, and another parameter may be set commonly for multiple PLMN IDs.

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

Also, for example, the initialDownlinkBWP may be set for each PLMN ID, and the initialUplinkBWP may be set commonly for multiple PLMN IDs.

For at least one specific ID (eg PLMN ID), setting an SSB different from the SSB detected for receiving SIB/SIB1 may be supported. The UE may receive a different SSB than it detected for receiving SIB/SIB1 for at least one specific ID (eg PLMN ID).

Information about the SSB may be included in the serving cell configuration information (eg, ServingCellConfigCommonSIB) included in the system information (eg, SIB/SIB1). Information about the SSB may be associated with a specific ID (eg PLMN ID).

The information on the SSB includes information on the frequency position of the SSB (eg, absoluteFrequencySSB), information on the subcarrier spacing of the SSB (eg, ssbSubcarrierSpacing), information on the SSB index (information on the SSB index assumed to be transmitted by the UE , eg, ssb-PositionsInBurst), and information about the periodicity of the SSB (eg, ssb-periodicityServingCell).

The association between the information on the SSB and a specific ID (eg, PLMN ID) may be made within the parameters of a specific frequency resource. The parameter of the specific frequency resource may be the parameter of the initial DL BWP (eg initialDownlinkBWP/BWP-DownlinkCommon).

The UE may assume that the SSBs associated with a particular ID are included in the initial DL BWP for that particular ID. Also, the case where the SSB associated with a particular ID is not included in the initial DL BWP for that particular ID may be supported.

A UE may monitor only SSBs associated with a specific ID of the UE (eg, PLMN ID), assuming that they are SSBs of the serving cell.

A UE may monitor both SSBs associated with the UE's specific ID (eg, PLMN ID) and SSBs detected to receive system information as SSBs of the serving cell.

A UE may use an SSB associated with an ID other than the specific ID of the UE (eg, PLMN ID) for rate match determination.

According to the first embodiment, it is possible to set frequency resources (eg, initial DL/UL BWP) separately for each specific ID (eg, PLMN ID).

<Second embodiment>
Separate (independent) configuration of frequency/time resources for each specific ID (eg, PLMN ID) may be supported.

The frequency/time resource may be, for example, a time resource configured for the UE during initial access. The frequency/time resources may be UL/DL settings in Time Division Duplex (TDD).

Information about the specific frequency/time resource may be included in serving cell configuration information (eg, ServingCellConfigCommonSIB) included in broadcast information (eg, system information (eg, SIB/SIB1)). The information about the specific frequency/time resource may be the UL/DL configuration in TDD (eg, tdd-UL-DL-ConfigurationCommon/TDD-UL-DL-ConfigCommon).

For example, in the UL/DL configuration in TDD (e.g., tdd-UL-DL-ConfigurationCommon/TDD-UL-DL-ConfigCommon) included in the serving cell configuration information (e.g., ServingCellConfigCommonSIB) included in the system information, one or Information on multiple specific IDs (eg PLMN IDs) may be included.

The UE may determine specific time resource settings for each specific ID based on a specific ID (eg, PLMN ID) included in SIB/SIB1.

FIG. 3A is a diagram showing an example of PLMN ID associations 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.

In the example shown in FIG. 3A, ServingCellConfigCommonSIB contains information on PLMN IDs (eg, plmn-Identity/plmn-IdentityList). That is, ServingCellConfigCommonSIB is defined for each PLMN ID (for each operator). That is, tdd-UL-DL-ConfigurationCommon contained in ServingCellConfigCommonSIB is defined for each PLMN ID (for each operator).

FIG. 3B is a diagram showing another example of association regarding 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.

In the example shown in FIG. 3B, tdd-UL-DL-ConfigurationCommon contains information about PLMN IDs (eg, plmn-Identity/plmn-IdentityList). That is, tdd-UL-DL-ConfigurationCommon is defined for each PLMN ID (for each operator). That is, the parameters included in tdd-UL-DL-ConfigurationCommon (for example, the parameter indicating the subcarrier spacing (referenceSubcarrierSpacing), the parameter indicating the first TDD UL/DL pattern (pattern1), and the second TDD UL/DL At least one of the parameters (pattern2) indicating the pattern is defined for each PLMN ID (for each operator).

It should be noted that in the configurations shown in FIGS. 3A and 3B, a certain parameter may be set separately for each PLMN ID, and another parameter may be set commonly for multiple PLMN IDs.

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

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

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

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

Information about available and unavailable DL/UL resources in the UL/DL configuration in TDD (e.g. tdd-UL-DL-ConfigurationCommon/TDD-UL-DL-ConfigCommon) , may be included. According to this, available/unavailable resources can be set and notified for each business operator.

According to the second embodiment, it is possible to set time resources (for example, TDD UL/DL settings) separately for each specific ID (for example, PLMN ID).

<Third Embodiment>
A separate (independent) configuration for the Random Access Channel (RACH) for each specific ID (eg, PLMN ID) may be supported.

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

The UE may receive information on RACH configuration that is configured separately for each specific ID. The UE may control the random access procedure (RACH operation) based on the information regarding the configuration of the RACH.

The UE may determine RACH time resources, RACH frequency resources, and RACH preambles configured for each specific ID.

The information related to the RACH settings may be RACH settings (eg, RACH-ConfigCommon). The RACH configuration (eg RACH-ConfigCommon) may be included in the initial UL BWP information (eg initialUplinkBWP/BWP-UplinkCommon).

Information about the configuration of the RACH may be associated with a specific ID (eg, PLMN ID).

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

For example, information about the initial UL BWP (eg initialUplinkBWP/BWP-UplinkCommon) may include information about one or more specific IDs (eg PLMN ID). The UE may determine the association between the specific ID and the information regarding the setting of the RACH included in the information regarding the initial UL BWP.

For example, a RACH configuration (eg, RACH-ConfigCommon) may contain information about one or more specific IDs (eg, PLMN ID). UE is included in the RACH configuration (eg, RACH-ConfigCommon), information on PRACH time resource / format configuration (eg, prach-ConfigurationIndex), information on the start position of PRACH frequency resource (eg, msg1-FrequencyStart) , and at least one of the information about the PRACH sequence (for example, prach-RootSequenceIndex) and information about one or more specific IDs (for example, PLMN ID) and the association may be determined.

The UE may determine the RACH setting for each specific ID based on the specific ID (eg PLMN ID) included in the RACH setting.

FIG. 4A is a diagram showing an example of PLMN ID associations 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.

In the example shown in FIG. 4A, BWP-UplinkCommon contains information on PLMN IDs (eg, plmn-Identity/plmn-IdentityList). That is, BWP-UplinkCommon is defined for each PLMN ID (for each operator). In other words, RACH-ConfigCommon included in BWP-UplinkCommon is defined for each PLMN ID (for each operator).

FIG. 4B is a diagram showing another example of association regarding 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.

In the example shown in FIG. 4B, RACH-ConfigCommon contains information about PLMN IDs (eg, plmn-Identity/plmn-IdentityList). That is, RACH-ConfigCommon is defined for each PLMN ID (for each operator). That is, parameters included in RACH-ConfigCommon (e.g., information on PRACH time resource / format settings (e.g., prach-ConfigurationIndex), information on the start position of PRACH frequency resources (e.g., msg1-FrequencyStart), and PRACH At least one of the information about the sequence of (for example, prach-RootSequenceIndex)) is defined for each PLMN ID (for each operator).

It should be noted that in the configurations shown in FIGS. 4A and 4B, a certain parameter may be set separately for each PLMN ID, and another parameter may be set commonly for multiple PLMN IDs.

For example, information related to PRACH time resource/format configuration (eg, prach-ConfigurationIndex) is configured for each PLMN ID, information related to the start position of PRACH frequency resource (eg, msg1-FrequencyStart), and PRACH sequence related Information (eg, prach-RootSequenceIndex) may be commonly set for multiple PLMN IDs.

Also, for example, information on the configuration of the PRACH time resource/format (eg, prach-ConfigurationIndex) and information on the start position of the PRACH frequency resource (eg, msg1-FrequencyStart) are set for each PLMN ID, and the PRACH Information about the sequence (for example, prach-RootSequenceIndex) may be commonly set for multiple PLMN IDs.

Also, for example, information related to PRACH time resource/format configuration (eg, prach-ConfigurationIndex) and information related to PRACH sequence (eg, prach-RootSequenceIndex) are configured for each PLMN ID, and PRACH frequency resource start Information related to location (eg msg1-FrequencyStart) may be commonly set for multiple PLMN IDs.

For example, information on the start position of the PRACH frequency resource (eg, msg1-FrequencyStart) and information on the PRACH sequence (eg, prach-RootSequenceIndex) are set for each PLMN ID, and related to the setting of the PRACH time resource/format Information (eg, prach-ConfigurationIndex) may be commonly set for multiple PLMN IDs.

Also, for example, information on the PRACH sequence (for example, prach-RootSequenceIndex) is set for each PLMN ID, information on the setting of the PRACH time resource/format (for example, prach-ConfigurationIndex), and the start of the PRACH frequency resource Information related to location (eg msg1-FrequencyStart) may be commonly set for multiple PLMN IDs.

Also, for example, information on the start position of the PRACH frequency resource (eg, msg1-FrequencyStart) is set for each PLMN ID, information on the setting of the PRACH time resource/format (eg, prach-ConfigurationIndex), and the PRACH Information about the sequence (for example, prach-RootSequenceIndex) may be commonly set for multiple PLMN IDs.

The UE may include information about a specific ID (eg, PLMN ID) in the RACH (eg, message 1 (PRACH)/message 3 (RRCSetupRequest)/message A) and transmit the RACH. Information related to the specific ID (for example, PLMN ID) may be specific ID information (PLMN ID), or may be other information related to specific ID information (PLMN ID) .

According to this, PRACH resources (at least one of time/frequency resources and preambles) associated with a specific ID (PLMN ID) can be determined/set separately, and the network (base station) can A specific ID (PLMN ID) selected by the UE can be recognized from the detected PRACH resource.

According to the third embodiment, it is possible to set random access channels separately for each specific ID (eg, PLMN ID).

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

The other SIBs may be SIBs defined by existing specifications other than SIB1 (for example, at least one of SIB2 to SIB14), or may be newly defined other than SIBs defined by existing specifications. SIB (for example, may be called SIB N (N is any alphanumeric character)). This other SIB may be called SIB1X.

In the present disclosure, the other SIB (SIB1X) may be called an SIB associated with a specific ID.

Information/parameters regarding SIBs associated with a particular ID may be set in SIB1. The UE may monitor the SIBs associated with a particular ID based on the information about the SIBs associated with the particular ID configured in SIB1.

Information on SIBs associated with a specific ID, for example, information on the period of SIB (eg, si-Periodicity), information on the length of the system information window (eg, si-WindowLength), and a request to send system information It may be at least one of information related to usage settings (eg, si-RequestConfig).

At least one of the information on SIBs associated with a specific ID may be associated with a specific ID (eg PLMN ID).

FIG. 5 is a diagram showing an example of PLMN ID associations 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.

In the example shown in FIG. 5, SIB1 includes parameters related to SIB1X. Information on PLMN ID (eg, plmn-Identity/plmn-IdentityList) is included in the parameters for SIB1X. That is, a parameter (SIB1X) regarding SIB1X is defined for each PLMN ID (for each operator). That is, parameters included in the parameters related to SIB1X (e.g., information on the period of SIB (SIB1X) (e.g., si-Periodicity), information on the length of the window of system information (e.g., si-WindowLength), and system information At least one piece of information (for example, si-RequestConfig) regarding transmission request settings is defined for each PLMN ID (for each operator).

It should be noted that, in the configuration shown in FIG. 5, a certain parameter may be set separately for each PLMN ID, and another parameter may be set commonly for multiple PLMN IDs.

For example, information related to the SIB period (eg, si-Periodicity) is set for each PLMN ID, information related to the window length of system information (eg, si-WindowLength), and information related to system information transmission request settings (eg, si-RequestConfig) may be commonly set for multiple PLMN IDs.

Also, for example, information on the SIB period (eg, si-Periodicity) and information on the length of the system information window (eg, si-WindowLength) are set for each PLMN ID, and system information transmission request settings information (eg, si-RequestConfig) may be commonly set for multiple PLMN IDs.

Also, for example, information on the SIB period (eg, si-Periodicity) and information on system information transmission request settings (eg, si-RequestConfig) are set for each PLMN ID, and the length of the system information window information (eg si-WindowLength) may be commonly set for multiple PLMN IDs.

Also, for example, information on the length of the system information window (eg, si-WindowLength) and information on the settings for system information transmission request (eg, si-RequestConfig) are set for each PLMN ID, and the SIB cycle information (eg, si-Periodicity) may be commonly set for multiple PLMN IDs.

Also, for example, information related to system information transmission request settings (eg, si-RequestConfig) is set for each PLMN ID, information related to the SIB period (eg, si-Periodicity), and system information window length information (eg si-WindowLength) may be commonly set for multiple PLMN IDs.

Also, for example, information on the length of the system information window (eg, si-WindowLength) is set for each PLMN ID, information on the SIB period (eg, si-Periodicity), and system information transmission request settings information (eg, si-RequestConfig) may be commonly set for multiple PLMN IDs.

The UE may change/overwrite at least one of the information notified in SIB1 based on the information notified in SIB associated with a specific ID.

As described above, according to the fourth embodiment, it is possible to appropriately set system information for each business operator.

<Fifth Embodiment>
A separate (independent) configuration for cell reselection for each specific ID (eg, PLMN ID) may be supported.

The settings related to cell reselection and the settings related to idle mode measurement may be read interchangeably.

The UE may receive information on RACH configuration that is configured separately for each specific ID.

The UE may receive specific parameters associated with a specific ID (eg PLMN ID).

The specific parameter may be included in a specific SIB. The specific SIB may be the SIB (for example, SIB 3/4) defined by existing specifications, or may be SIB X described in the fourth embodiment.

The specific parameters are, for example, information on neighboring cells of the same frequency (intra-frequency) / different frequencies (inter-frequency) (e.g., intraFreqNeighCellList/interFreqNeighCellList), information on cell reselection non-target cell lists (e.g., intraFreqBlackCellList/interFreqBlackCellList ), information on the target cell list for cell reselection (e.g., intraFreqWhiteCellList/interFreqWhiteCellList), and information on cell reselection settings (e.g., cellReselectionInfoCommon/cellReselectionServingFreqInfo/intraFreqCellReselectionInfo/InterFreqCarrierFreqInfo), at least one of.

At least one of the above specific parameters may be associated with a specific ID (eg PLMN ID).

FIG. 6 is a diagram showing an example of PLMN ID associations 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 PLMN #3 and operator #3 are omitted for simplicity.

In the example shown in FIG. 6, a specific SIB (SIB3/4/1X) contains information on PLMN ID (eg, plmn-Identity/plmn-IdentityList) and specific parameters on cell reselection. The specific parameters are, for example, information on neighboring cells of the same frequency (intra-frequency) / different frequencies (inter-frequency) (e.g., intraFreqNeighCellList/interFreqNeighCellList), information on cell reselection non-target cell lists (e.g., intraFreqBlackCellList/interFreqBlackCellList ), information on the target cell list for cell reselection (e.g., intraFreqWhiteCellList/interFreqWhiteCellList), and information on cell reselection settings (e.g., cellReselectionInfoCommon/cellReselectionServingFreqInfo/intraFreqCellReselectionInfo/InterFreqCarrierFreqInfo), at least one of. Although all of these parameters are described in the example shown in FIG. 6, this description is merely an example, and the configuration may include at least one of them.

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

It should be noted that, in the configuration shown in FIG. 6, a certain parameter may be set separately for each PLMN ID, and another parameter may be set commonly for multiple PLMN IDs.

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

<Modification>
The settings/parameters for each specific ID (eg, PLMN ID) described in each of the above embodiments are merely examples. In addition to the settings/parameters described in the above embodiments, settings/parameters (eg, broadcast information) for the UE during any initial access/idle mode are configured/parameters for each specific ID (eg, PLMN ID). may be notified.

There may be a one-to-one correspondence between a specific ID (eg PLMN ID) and settings related to the specific ID. In other words, one setting may be associated with one specific ID.

Specific IDs (eg, PLMN IDs) and settings related to the specific IDs may correspond in multiple (one or more) to multiple one. In other words, a single setting may be associated with multiple (one or more) specific IDs (eg, a list of specific IDs).

Also, 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 SCell, and network sharing may not be performed in PCell (SpCell). Alternatively, the cell in which network sharing is performed may be PCell (SpCell), and network sharing may not be performed in SCell.

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

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

The wireless communication system 1 may also support dual connectivity between multiple Radio Access Technologies (RATs) (Multi-RAT Dual Connectivity (MR-DC)). MR-DC is 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. may be included.

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.

The wireless communication system 1 has dual connectivity between multiple base stations within the same RAT (for example, dual connectivity (NR-NR Dual Connectivity (NN-DC) in which both MN and SN are NR base stations (gNB) )) may be supported.

A wireless communication system 1 includes a base station 11 forming a macrocell C1 with a relatively wide coverage, and base stations 12 (12a-12c) arranged in the macrocell C1 and forming a small cell C2 narrower than the macrocell C1. You may prepare. A user terminal 20 may be located within at least one cell. The arrangement, number, etc. of each cell and user terminals 20 are not limited to the embodiment shown in the figure. Hereinafter, the base stations 11 and 12 are collectively referred to as the base station 10 when not distinguished.

The user terminal 20 may connect to at least one of the multiple base stations 10 . The user terminal 20 may utilize at least one of carrier aggregation (CA) using a plurality of component carriers (CC) and dual connectivity (DC).

Each CC may be included in at least one of the first frequency band (Frequency Range 1 (FR1)) and the second frequency band (Frequency Range 2 (FR2)). Macrocell C1 may be included in FR1, and small cell C2 may be included in FR2. For example, FR1 may be a frequency band below 6 GHz (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 correspond to a higher frequency band than FR2.

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

A plurality of base stations 10 may be connected by wire (for example, an optical fiber conforming to Common Public Radio Interface (CPRI), X2 interface, etc.) 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 is an Integrated Access Backhaul (IAB) donor, and the base station 12 corresponding to the relay station (relay) is an IAB Also called a node.

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 Evolved Packet Core (EPC), 5G Core Network (5GCN), Next Generation Core (NGC), and the like.

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

In the radio communication system 1, a radio access scheme based on orthogonal frequency division multiplexing (OFDM) may be used. For example, in at least one of Downlink (DL) and Uplink (UL), 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), etc. may be used.

A radio access method may be called a waveform. Note that in the radio communication system 1, other radio access schemes (for example, other single-carrier transmission schemes and other multi-carrier transmission schemes) may be used as the UL and DL radio access schemes.

In the radio communication system 1, as downlink channels, 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)) or the like may be used.

In the radio communication system 1, as uplink channels, an uplink shared channel (PUSCH) shared by each user terminal 20, an uplink control channel (PUCCH), a random access channel (Physical Random Access Channel (PRACH)) or the like may be used.

User data, upper layer control information, System Information Block (SIB), etc. are transmitted by the PDSCH. User data, higher layer control information, and the like may be transmitted by PUSCH. Also, a Master Information Block (MIB) may be transmitted by the PBCH.

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 PDSCH and PUSCH.

The DCI that schedules PDSCH may be called DL assignment, DL DCI, etc., and the DCI that schedules PUSCH may be called UL grant, UL DCI, etc. PDSCH may be replaced with DL data, and PUSCH may be replaced with UL data.

A control resource set (CControl Resource SET (CORESET)) and a search space (search space) may be used for PDCCH detection. CORESET corresponds to a resource searching for DCI. The search space corresponds to the search area and search method of PDCCH candidates. A CORESET may be associated with one or more search spaces. The UE may monitor CORESETs associated with certain search spaces based on the search space settings.

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

By PUCCH, channel state information (CSI), acknowledgment information (for example, Hybrid Automatic Repeat reQuest ACKnowledgement (HARQ-ACK), ACK/NACK, etc.) and scheduling request (Scheduling Request ( SR)) may be transmitted. A random access preamble for connection establishment with a cell may be transmitted by the PRACH.

In addition, in the present disclosure, downlink, uplink, etc. may be expressed without adding "link". Also, various channels may be expressed without adding "Physical" to the head.

In the wireless communication system 1, synchronization signals (SS), downlink reference signals (DL-RS), etc. may be transmitted. In the radio communication system 1, the DL-RS includes a cell-specific reference signal (CRS), a channel state information reference signal (CSI-RS), a demodulation reference signal (DeModulation Reference Signal (DMRS)), Positioning Reference Signal (PRS)), Phase Tracking Reference Signal (PTRS)), etc. may be transmitted.

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

Also, in the radio communication system 1, even if measurement reference signals (SRS), demodulation reference signals (DMRS), etc. are transmitted as uplink reference signals (UL-RS), good. Note that DMRS may also be called a user terminal-specific reference signal (UE-specific reference signal).

(base station)
FIG. 8 is a diagram illustrating an example of the configuration of a base station according to one embodiment. The base station 10 comprises a control section 110 , a transmission/reception section 120 , a transmission/reception antenna 130 and a transmission line interface 140 . One or more of each of the control unit 110, the transmitting/receiving unit 120, the transmitting/receiving antenna 130, and the transmission path interface 140 may be provided.

It should be noted that this example mainly shows the functional blocks of the features of the present embodiment, and it may be assumed that the base station 10 also has other functional blocks necessary for wireless communication. A part of the processing of each unit described below may be omitted.

The control unit 110 controls the base station 10 as a whole. The control unit 110 can be configured from a controller, a control circuit, and the like, which are explained based on common recognition in the technical field according to the present disclosure.

The control unit 110 may control signal generation, scheduling (for example, resource allocation, mapping), and the like. The control unit 110 may control transmission/reception, measurement, etc. using the transmission/reception unit 120 , the transmission/reception antenna 130 and the transmission line interface 140 . The control unit 110 may generate data to be transmitted as a signal, control information, a sequence, etc., and transfer them to the transmission/reception unit 120 . The control unit 110 may perform call processing (setup, release, etc.) of communication channels, state management of the base station 10, management of radio resources, and the like.

The transmitting/receiving section 120 may include a baseband section 121 , a radio frequency (RF) section 122 and a measuring section 123 . The baseband section 121 may include a transmission processing section 1211 and a reception processing section 1212 . The transmitting/receiving unit 120 is configured from a transmitter/receiver, an RF circuit, a baseband circuit, a filter, a phase shifter, a measurement circuit, a transmitting/receiving circuit, etc., which are explained based on common recognition in the technical field according to the present disclosure. be able to.

The transmission/reception unit 120 may be configured as an integrated transmission/reception unit, or may be configured from a transmission unit and a reception unit. The transmission section may be composed of the transmission processing section 1211 and the RF section 122 . The receiving section may be composed of a reception processing section 1212 , an RF section 122 and a measurement section 123 .

The transmitting/receiving antenna 130 can be configured from an antenna described based on common recognition in the technical field related to the present disclosure, such as an array antenna.

The transmitting/receiving unit 120 may transmit the above-described downlink channel, synchronization signal, downlink reference signal, and the like. The transmitting/receiving unit 120 may receive the above-described uplink channel, uplink reference signal, and the like.

The transmitting/receiving unit 120 may form at least one of the transmission beam and the reception beam using digital beamforming (eg, precoding), analog beamforming (eg, phase rotation), or the like.

The transmission/reception unit 120 (transmission processing unit 1211) performs Packet Data Convergence Protocol (PDCP) layer processing, Radio Link Control (RLC) layer processing (for example, RLC retransmission control), Medium Access Control (MAC) layer processing (for example, HARQ retransmission control), etc. may be performed to generate a bit string to be transmitted.

The transmission/reception unit 120 (transmission processing unit 1211) performs channel coding (which may include error correction coding), modulation, mapping, filtering, and discrete Fourier transform (DFT) on the bit string to be transmitted. Processing (if necessary), Inverse Fast Fourier Transform (IFFT) processing, precoding, transmission processing such as digital-to-analog conversion may be performed, and the baseband signal may be output.

The transmitting/receiving unit 120 (RF unit 122) may perform modulation to a radio frequency band, filter processing, amplification, and the like on the baseband signal, and may transmit the radio frequency band signal via the transmitting/receiving antenna 130. .

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

The transmission/reception unit 120 (reception processing unit 1212) performs analog-to-digital conversion, Fast Fourier transform (FFT) processing, and Inverse Discrete Fourier transform (IDFT) processing on the acquired baseband signal. )) processing (if necessary), filtering, demapping, demodulation, decoding (which may include error correction decoding), MAC layer processing, RLC layer processing and PDCP layer processing. User data and the like may be acquired.

The transmitting/receiving unit 120 (measuring unit 123) may measure the received signal. For example, the measurement unit 123 may perform Radio Resource Management (RRM) measurement, Channel State Information (CSI) measurement, etc. based on the received signal. The measurement unit 123 measures received power (for example, Reference Signal Received Power (RSRP)), reception quality (for example, Reference Signal Received Quality (RSRQ), Signal to Interference plus Noise Ratio (SINR), Signal to Noise Ratio (SNR)) , signal strength (for example, Received Signal Strength Indicator (RSSI)), channel information (for example, CSI), and the like may be measured. The measurement result may be output to control section 110 .

The transmission path interface 140 transmits and receives signals (backhaul signaling) to and from devices included in the core network 30, other base stations 10, etc., and user data (user plane data) for the user terminal 20, control plane data, and the like. Data and the like may be obtained, transmitted, and the like.

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

The transmitting/receiving unit 120 may transmit the setting information of the serving cell associated with the Public Land Mobile Network (PLMN) ID included in the first system information block (SIB, eg, SIB1). The control unit 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).

The transmitting/receiving unit 120 may transmit setting information of a random access channel (RACH) associated with a Public Land Mobile Network (PLMN) ID included in a system information block (SIB, eg, SIB1). The control unit 110 may use the RACH setting information to control the random access procedure associated with the PLMN ID (third embodiment).

The transmitting/receiving unit 120 transmits setting information of a second SIB (for example, an SIB other than SIB1) associated with the Public Land Mobile Network (PLMN) ID included in the first system information block (SIB, for example, SIB1). You may The control unit 110 may use the setting information of the second SIB to control the transmission of the second SIB associated with the PLMN ID (fourth and fifth embodiments).

(user terminal)
FIG. 9 is a diagram illustrating an example of the configuration of a user terminal according to one embodiment. The user terminal 20 includes a control section 210 , a transmission/reception section 220 and a transmission/reception antenna 230 . One or more of each of the control unit 210, the transmitting/receiving unit 220, and the transmitting/receiving antenna 230 may be provided.

It should be noted that this example mainly shows the functional blocks of the features of the present embodiment, and it may be assumed that the user terminal 20 also has other functional blocks necessary for wireless communication. A part of the processing of each unit described below may be omitted.

The control unit 210 controls the user terminal 20 as a whole. The control unit 210 can be configured from a controller, a control circuit, and the like, which are explained based on common recognition in the technical field according to the present disclosure.

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

The transmitting/receiving section 220 may include a baseband section 221 , an RF section 222 and a measurement section 223 . The baseband section 221 may include a transmission processing section 2211 and a reception processing section 2212 . The transmitting/receiving unit 220 can be configured from a transmitter/receiver, an RF circuit, a baseband circuit, a filter, a phase shifter, a measuring circuit, a transmitting/receiving circuit, etc., which are explained based on common recognition in the technical field according to the present disclosure.

The transmission/reception unit 220 may be configured as an integrated transmission/reception unit, or may be configured from a transmission unit and a reception unit. The transmission section may be composed of a transmission processing section 2211 and an RF section 222 . The receiving section may include a reception processing section 2212 , an RF section 222 and a measurement section 223 .

The transmitting/receiving antenna 230 can be configured from an antenna described based on common recognition in the technical field related to the present disclosure, such as an array antenna.

The transmitting/receiving unit 220 may receive the above-described downlink channel, synchronization signal, downlink reference signal, and the like. The transmitting/receiving unit 220 may transmit the above-described uplink channel, uplink reference signal, and the like.

The transmitter/receiver 220 may form at least one of the transmission beam and the reception beam using digital beamforming (eg, precoding), analog beamforming (eg, phase rotation), or the like.

The transmitting/receiving unit 220 (transmission processing unit 2211) performs PDCP layer processing, RLC layer processing (eg, RLC retransmission control), MAC layer processing (eg, , HARQ retransmission control) and the like may be performed to generate a bit string to be transmitted.

The transmission/reception unit 220 (transmission processing unit 2211) performs channel coding (which may include error correction coding), modulation, mapping, filtering, DFT processing (if necessary), and IFFT processing on a bit string to be transmitted. , precoding, digital-analog conversion, and other transmission processing may be performed, and the baseband signal may be output.

Whether or not to apply DFT processing may be based on transform precoding settings. Transmitting/receiving unit 220 (transmission processing unit 2211), for a certain channel (for example, PUSCH), if transform precoding is enabled, the above to transmit the channel using the DFT-s-OFDM waveform The DFT process may be performed as the transmission process, or otherwise the DFT process may not be performed as the transmission process.

The transmitting/receiving unit 220 (RF unit 222) may perform modulation to a radio frequency band, filter processing, amplification, and the like on the baseband signal, and may transmit the radio frequency band signal via the transmitting/receiving antenna 230. .

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

The transmission/reception unit 220 (reception processing unit 2212) performs analog-to-digital conversion, FFT processing, IDFT processing (if necessary), filtering, demapping, demodulation, decoding (error correction) on the acquired baseband signal. decoding), MAC layer processing, RLC layer processing, PDCP layer processing, and other reception processing may be applied to acquire user data and the like.

The transmitting/receiving section 220 (measuring section 223) may measure the received signal. For example, the measurement unit 223 may perform RRM measurement, CSI measurement, etc. based on the received signal. The measuring unit 223 may measure received power (eg, RSRP), received quality (eg, RSRQ, SINR, SNR), signal strength (eg, RSSI), channel information (eg, CSI), and the like. The measurement result may be output to control section 210 .

Note that the transmitter and receiver of the user terminal 20 in the present disclosure may be configured by at least one of the transmitter/receiver 220 and the transmitter/receiver antenna 230 .

The transmitting/receiving unit 220 may receive the setting information of the serving cell associated with the Public Land Mobile Network (PLMN) ID included in the first system information block (SIB, eg, SIB1). The control unit 210 may determine at least one of frequency resources and time resources associated with the PLMN ID based on the setting information (first and second embodiments).

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).

The time resource may be a resource based on time division duplex uplink/downlink configuration (second embodiment).

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

The transmitting/receiving unit 220 may receive configuration information of a random access channel (RACH) associated with a Public Land Mobile Network (PLMN) ID included in a system information block (SIB, eg, SIB1). The control unit 210 may control the random access procedure associated with the PLMN ID based on the RACH setting information (third embodiment).

The RACH configuration information may be included in the information on the initial uplink bandwidth portion. The information on the initial uplink bandwidth portion may include the PLMN ID (third embodiment).

The RACH configuration information includes at least one of the PLMN ID, information on physical random access channel (PRACH) time resource and format configuration, information on the start position of the PRACH frequency resource, and information on the PRACH sequence. (third embodiment).

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

Transmitter/receiver 220 receives setting information of a second SIB (for example, SIB other than SIB1) associated with the Public Land Mobile Network (PLMN) ID included in the first system information block (SIB, for example, SIB1). You may The control unit 210 may control monitoring of the second SIB associated with the PLMN ID based on the setting information of the second SIB (fourth and fifth embodiments).

The second SIB configuration information includes at least one of information on the second SIB period, information on the window length of the second SIB, and information on system information transmission request configuration. (fourth embodiment).

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).

The second SIB may contain information on cell reselection (fifth embodiment).

(Hardware configuration)
It should be noted that the block diagrams used in the description of the above embodiments show blocks in units of functions. These functional blocks (components) are implemented by any combination of at least one of hardware and software. Also, the method of realizing each functional block is not particularly limited. That is, each functional block may be implemented using one device physically or logically coupled, or directly or indirectly using two or more physically or logically separated devices (e.g. , wired, wireless, etc.) and may be implemented using these multiple devices. A functional block may be implemented by combining software in the one device or the plurality of devices.

where function includes judgment, decision, determination, calculation, calculation, processing, derivation, investigation, search, confirmation, reception, transmission, output, access, resolution, selection, selection, establishment, comparison, assumption, expectation, deem , broadcasting, notifying, communicating, forwarding, configuring, reconfiguring, allocating, mapping, assigning, etc. Not limited. For example, a functional block (component) that performs transmission may be called a transmitting unit, a transmitter, or the like. In either case, as described above, the implementation method is not particularly limited.

For example, a base station, a user terminal, etc. in 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 hardware configurations of a base station and a user terminal according to one embodiment. The base station 10 and user terminal 20 described above may be physically configured as a computer device including a processor 1001, a memory 1002, a storage 1003, a communication device 1004, an input device 1005, an output device 1006, a bus 1007, and the like. .

In the present disclosure, terms such as apparatus, circuit, device, section, and unit can be read interchangeably. The hardware configuration of the base station 10 and the user terminal 20 may be configured to include one or more of each device shown in the figure, or may be configured without some devices.

For example, although only one processor 1001 is illustrated, there may be multiple processors. Also, processing may be performed by one processor, or processing may be performed by two or more processors concurrently, serially, or otherwise. Note that processor 1001 may be implemented by one or more chips.

Each function in the base station 10 and the user terminal 20, for example, by loading predetermined software (program) on hardware such as a processor 1001 and a memory 1002, the processor 1001 performs calculations, communication via the communication device 1004 and at least one of reading and writing data in the memory 1002 and the storage 1003 .

The processor 1001, for example, operates an operating system and controls the entire computer. The processor 1001 may be configured by a central processing unit (CPU) including an interface with peripheral devices, a control device, an arithmetic device, registers, and the like. For example, at least part of the above-described control unit 110 (210), transmission/reception unit 120 (220), etc. may be realized by the processor 1001. FIG.

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

The memory 1002 is a computer-readable recording medium, such as Read Only Memory (ROM), Erasable Programmable ROM (EPROM), Electrically EPROM (EEPROM), Random Access Memory (RAM), or at least any other suitable storage medium. may be configured by one. The memory 1002 may also be called a register, cache, main memory (main storage device), or the like. The memory 1002 can store executable programs (program code), software modules, etc. for implementing a wireless communication method according to an embodiment of the present disclosure.

The storage 1003 is a computer-readable recording medium, for example, a flexible disk, a floppy (registered trademark) disk, a magneto-optical disk (for example, a compact disk (Compact Disc ROM (CD-ROM), etc.), a digital versatile disk, Blu-ray disc), removable disc, hard disk drive, smart card, flash memory device (e.g., card, stick, key drive), magnetic stripe, database, server, or other suitable storage medium may be configured by Storage 1003 may also be called an auxiliary storage device.

The communication device 1004 is hardware (transmitting/receiving device) for communicating between computers via at least one of a wired network and a wireless network, and is also called a network device, a network controller, a network card, a communication module, or the like. The communication device 1004 includes a high-frequency switch, duplexer, filter, frequency synthesizer, etc. in order to realize at least one of frequency division duplex (FDD) and time division duplex (TDD), for example. may be configured to include For example, the transmitting/receiving unit 120 (220), the transmitting/receiving antenna 130 (230), and the like described above may be realized by the communication device 1004. FIG. The transmitter/receiver 120 (220) may be physically or logically separated into a transmitter 120a (220a) and a receiver 120b (220b).

The input device 1005 is an input device (for example, keyboard, mouse, microphone, switch, button, 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. Note that the input device 1005 and the output device 1006 may be integrated (for example, a touch panel).

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 devices.

In addition, the base station 10 and the user terminal 20 include a microprocessor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a programmable logic device (PLD), a field programmable gate array (FPGA), etc. It may be configured including hardware, and a part or all of each functional block may be realized using the hardware. For example, processor 1001 may be implemented using at least one of these pieces of hardware.

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

A radio frame may consist of one or more periods (frames) in the time domain. Each of the one or more periods (frames) that make up a radio frame may be called a subframe. Furthermore, a subframe may consist of one or more slots in the time domain. A subframe may be a fixed time length (eg, 1 ms) independent of numerology.

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

A slot may consist of one or more symbols (Orthogonal Frequency Division Multiplexing (OFDM) symbol, Single Carrier Frequency Division Multiple Access (SC-FDMA) symbol, etc.) in the time domain. A slot may also be a unit of time based on numerology.

A slot may contain multiple mini-slots. Each minislot may consist of one or more symbols in the time domain. A minislot may also be referred to as a subslot. A minislot may consist of fewer symbols than a slot. A PDSCH (or PUSCH) transmitted in time units larger than a minislot may be referred to as PDSCH (PUSCH) Mapping Type A. PDSCH (or PUSCH) transmitted using minislots may be referred to as PDSCH (PUSCH) mapping type B.

Radio frames, subframes, slots, minislots and symbols all represent time units when transmitting signals. Radio frames, subframes, slots, minislots and symbols may be referred to by other corresponding designations. Note that time units such as frames, subframes, slots, minislots, and symbols in the present disclosure may be read interchangeably.

For example, one subframe may be called a TTI, a plurality of consecutive subframes may be called a TTI, and one slot or one minislot may be called a TTI. That is, at least one of the subframe and TTI may be a subframe (1 ms) in existing LTE, a period shorter than 1 ms (eg, 1-13 symbols), or a period longer than 1 ms may be Note that the unit representing the TTI may be called a slot, mini-slot, or the like instead of a subframe.

Here, TTI refers to, for example, the minimum scheduling time unit in wireless communication. For example, in the LTE system, a base station performs scheduling to allocate radio resources (frequency bandwidth, transmission power, etc. that can be used by each user terminal) to each user terminal on a TTI basis. Note that the definition of TTI is not limited to this.

A TTI may be a transmission time unit such as a channel-encoded data packet (transport block), code block, or codeword, or may be a processing unit such as scheduling and link adaptation. Note that when a TTI is given, the time interval (for example, the number of symbols) in which transport blocks, code blocks, codewords, etc. are actually mapped may be shorter than the TTI.

When one slot or one minislot is called a TTI, one or more TTIs (that is, one or more slots or one or more minislots) may be the minimum scheduling time unit. Also, the number of slots (the number of mini-slots) constituting the minimum time unit of the scheduling may be controlled.

A TTI having a time length of 1 ms may be called a normal TTI (TTI in 3GPP Rel. 8-12), normal TTI, long TTI, normal subframe, normal subframe, long subframe, slot, or the like. A TTI that is shorter than a normal TTI may be called a shortened TTI, a short TTI, a partial or fractional TTI, a shortened subframe, a short subframe, a minislot, a subslot, a slot, and the like.

Note that the long TTI (e.g., normal TTI, subframe, etc.) may be replaced with a TTI having a time length exceeding 1 ms, and the short TTI (e.g., shortened TTI, etc.) is less than the TTI length of the long TTI and 1 ms A TTI having the above TTI length may be read instead.

A resource block (RB) is a resource allocation unit in the time domain and frequency domain, and may include one or more consecutive subcarriers (subcarriers) in the frequency domain. The number of subcarriers included in the RB may be the same regardless of the neumerology, eg twelve. The number of subcarriers included in an RB may be determined based on neumerology.

Also, an RB may contain one or more symbols in the time domain and may be 1 slot, 1 minislot, 1 subframe or 1 TTI long. One TTI, one subframe, etc. may each be configured with one or more resource blocks.

One or more RBs are Physical Resource Block (PRB), Sub-Carrier Group (SCG), Resource Element Group (REG), PRB pair, RB Also called a pair.

Also, a resource block may be composed of one or more resource elements (Resource Element (RE)). For example, 1 RE may be a radio resource region of 1 subcarrier and 1 symbol.

A Bandwidth Part (BWP) (which may also be called a bandwidth part) represents a subset of contiguous common resource blocks (RBs) for a numerology on a carrier. good too. Here, the common RB may be identified by an RB index based on the common reference point of the carrier. PRBs may be defined in a BWP and numbered within that BWP.

BWP may include UL BWP (BWP for UL) and DL BWP (BWP for DL). One or multiple BWPs may be configured for a UE within one carrier.

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 "cell", "carrier", etc. in the present disclosure may be read as "BWP".

It should be noted that the structures of radio frames, subframes, slots, minislots, symbols, etc. described above are merely examples. For example, the number of subframes contained in a radio frame, the number of slots per subframe or radio frame, the number of minislots contained within a slot, the number of symbols and RBs contained in a slot or minislot, the number of Configurations such as the number of subcarriers and the number of symbols in a TTI, symbol length, cyclic prefix (CP) length, etc. can be varied.

In addition, 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. may be represented. For example, radio resources may be indicated by a predetermined index.

The names used for parameters and the like in this disclosure are not restrictive names in any respect. Further, the formulas and the like using these parameters may differ from those expressly disclosed in this disclosure. Since the various channels (PUCCH, PDCCH, etc.) and information elements can be identified by any suitable names, the various names assigned to these various channels and information elements are not limiting names in any respect. .

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 refer to voltages, currents, electromagnetic waves, magnetic fields or magnetic particles, light fields or photons, or any of these. may be represented by a combination of

Also, information, signals, etc. can 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 and output through multiple network nodes.

Input/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 appended. Output information, signals, etc. may be deleted. Input information, signals, etc. may be transmitted to other devices.

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

The physical layer signaling may also be called Layer 1/Layer 2 (L1/L2) control information (L1/L2 control signal), L1 control information (L1 control signal), and the like. RRC signaling may also be called an RRC message, and may be, for example, an RRC connection setup message, an RRC connection reconfiguration message, or the like. Also, MAC signaling may be notified using, for example, a MAC Control Element (CE).

In addition, notification of predetermined information (for example, notification of “being X”) is not limited to explicit notification, but implicit notification (for example, by not notifying the predetermined information or by providing another information by notice of

The determination may be made by a value (0 or 1) represented by 1 bit, or by a boolean value represented by true or false. , may be performed by numerical comparison (eg, comparison with a predetermined value).

Software, whether referred to as software, firmware, middleware, microcode, hardware description language or otherwise, includes instructions, instruction sets, code, code segments, program code, programs, subprograms, and software modules. , applications, software applications, software packages, routines, subroutines, objects, executables, threads of execution, procedures, functions, and the like.

Also, software, instructions, information, etc. may be transmitted and received via a transmission medium. For example, the software uses wired technology (coaxial cable, fiber optic cable, twisted pair, Digital Subscriber Line (DSL), etc.) and/or wireless technology (infrared, microwave, etc.) , a server, or other remote source, these wired and/or wireless technologies are included within the definition of transmission media.

The terms "system" and "network" used in this disclosure may be used interchangeably. A “network” may refer to devices (eg, base stations) included in a network.

In the present disclosure, "precoding", "precoder", "weight (precoding weight)", "Quasi-Co-Location (QCL)", "Transmission Configuration Indication state (TCI state)", "spatial "spatial relation", "spatial domain filter", "transmission power", "phase rotation", "antenna port", "antenna port group", "layer", "number of layers", Terms such as "rank", "resource", "resource set", "resource group", "beam", "beam width", "beam angle", "antenna", "antenna element", "panel" are interchangeable. can be used as intended.

In the present disclosure, "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. A base station may also be referred to by terms such as macrocell, small cell, femtocell, picocell, and the like.

A base station can accommodate one or more (eg, three) cells. When a base station accommodates multiple cells, the overall coverage area of the base station can be partitioned into multiple smaller areas, and each smaller area is assigned to a base station subsystem (e.g., a small indoor base station (Remote Radio)). Head (RRH))) may also provide communication services. The terms "cell" or "sector" refer to part or all of the coverage area of at least one of the base stations and base station subsystems that serve communication within such coverage.

In this disclosure, terms such as "Mobile Station (MS)", "user terminal", "User Equipment (UE)", and "terminal" are used interchangeably. can be

Mobile stations include subscriber stations, mobile units, subscriber units, wireless units, remote units, mobile devices, wireless devices, wireless communication devices, remote devices, mobile subscriber stations, access terminals, mobile terminals, wireless terminals, remote terminals. , a handset, a user agent, a mobile client, a client, or some other suitable term.

At least one of the base station and the mobile station may be called a transmitting device, a receiving device, a wireless communication device, or the like. At least one of the base station and the mobile station may be a device mounted on a moving object, the mobile itself, or the like.

The moving body refers to a movable object, the speed of movement is arbitrary, and it naturally includes cases where the moving body is stationary. Examples of such moving bodies include vehicles, transportation vehicles, automobiles, motorcycles, bicycles, connected cars, excavators, bulldozers, wheel loaders, dump trucks, forklifts, trains, buses, carts, rickshaws, and ships (ships and other watercraft). , airplanes, rockets, satellites, drones, multi-copters, quad-copters, balloons and objects mounted on them. Further, the mobile object may be a mobile object that autonomously travels based on an operation command.

The mobile object may be a vehicle (e.g., car, airplane, etc.), an unmanned mobile object (e.g., drone, self-driving car, etc.), or a robot (manned or unmanned ). Note that at least one of the base station and the mobile station includes devices that do not necessarily move during communication operations. For example, at least one of the base station and mobile station may be an Internet of Things (IoT) device such as a sensor.

FIG. 11 is a diagram showing an example of a vehicle according to one embodiment. The vehicle 40 includes a drive unit 41, a steering unit 42, an accelerator pedal 43, a brake pedal 44, a shift lever 45, left and right front wheels 46, left and right rear wheels 47, an axle 48, an electronic control unit 49, various sensors (current sensor 50, revolution sensor 51, air pressure sensor 52, vehicle speed sensor 53, acceleration sensor 54, accelerator pedal sensor 55, brake pedal sensor 56, shift lever sensor 57, and object detection sensor 58), information service unit 59 and communication module 60. Prepare.

The driving unit 41 is composed of, for example, at least one of an engine, a motor, and a hybrid of an engine and a motor. The steering unit 42 includes at least a steering wheel (also referred to as a steering wheel), 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.

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

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

The information service unit 59 includes various devices such as car navigation systems, audio systems, speakers, displays, televisions, and radios for providing (outputting) various information such as driving information, traffic information, and entertainment information, and these devices. and one or more ECUs that control The information service unit 59 provides various information/services (for example, multimedia information/multimedia services) to the occupants of the vehicle 40 using information acquired from an external device via the communication module 60 or the like.

The information service unit 59 may include an input device (e.g., keyboard, mouse, microphone, switch, button, sensor, touch panel, etc.) that receives input from the outside, and an output device that outputs to the outside (e.g., display, speaker, LED lamp, touch panel, etc.).

The driving support system unit 64 includes a millimeter wave radar, Light Detection and Ranging (LiDAR), a camera, a positioning locator (e.g., Global Navigation Satellite System (GNSS), etc.), map information (e.g., High Definition (HD)) maps, autonomous vehicle (AV) maps, etc.), gyro systems (e.g., inertial measurement units (IMU), inertial navigation systems (INS), etc.), artificial intelligence ( Artificial intelligence (AI) chips, AI processors, and other devices that provide functions to prevent accidents and reduce the driver's driving load, and one or more devices that control these devices ECU. In addition, the driving support system unit 64 transmits and receives various information via the communication module 60, and realizes a driving support function or an automatic driving function.

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 communicates with the vehicle 40 through a communication port 63 such as a driving 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, Data (information) is transmitted and received between the axle 48, the microprocessor 61 and memory (ROM, RAM) 62 in the electronic control unit 49, and various sensors 50-58.

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 an external device via wireless communication. Communication module 60 may be internal or external to electronic control 49 . The external device may be, for example, the above-described base station 10, user terminal 20, or the like. Also, the communication module 60 may be, for example, at least one of the base station 10 and the user terminal 20 described above (and may function as at least one of the base station 10 and the user terminal 20).

The communication module 60 receives signals from the various sensors 50 to 58 described above input to the electronic control unit 49, information obtained based on the signals, and input from the outside (user) obtained via the information service unit 59. may be transmitted to the external device via wireless communication. The electronic control unit 49, the various sensors 50-58, the information service unit 59, etc. may be called an input unit that receives input. For example, the PUSCH transmitted by communication module 60 may include information based on the above inputs.

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

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

Also, the base station in the present disclosure may be read as a user terminal. For example, communication between a base station and a user terminal is replaced with communication between multiple user terminals (for example, Device-to-Device (D2D), Vehicle-to-Everything (V2X), etc.) Regarding the configuration, each aspect/embodiment of the present disclosure may be applied. In this case, the user terminal 20 may have the functions of the base station 10 described above. In addition, words such as "uplink" and "downlink" may be replaced with words corresponding to communication between terminals (for example, "sidelink"). For example, uplink channels, downlink channels, etc. may be read as sidelink channels.

Similarly, user terminals in the present disclosure may be read as base stations. In this case, the base station 10 may have the functions of the user terminal 20 described above.

In the present disclosure, operations that are assumed to be performed by the base station may be performed by its upper node in some cases. In a network that includes one or more network nodes with a base station, various operations performed for communication with a terminal may involve the base station, one or more network nodes other than the base station (e.g., Clearly, this can be done by a Mobility Management Entity (MME), Serving-Gateway (S-GW), etc. (but not limited to these) or a combination thereof.

Each aspect/embodiment described in the present disclosure may be used alone, may be used in combination, or may be used by switching along with execution. Also, the processing procedures, sequences, flowcharts, etc. of each aspect/embodiment described in the present disclosure may be rearranged as long as there is no contradiction. For example, the methods described in this disclosure present elements of the various steps using a sample order, and are not limited to the specific order presented.

Each aspect/embodiment described in this disclosure includes 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 a 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®), IEEE 802.16 (WiMAX®), IEEE 802.20, Ultra-WideBand (UWB), Bluetooth®, or any other suitable wireless communication method. It may be applied to a system to be used, a next-generation system extended, modified, created or defined based on these. Also, multiple systems may be applied in combination (for example, a combination of LTE or LTE-A and 5G).

The term "based on" as used in this disclosure does not mean "based only on" unless otherwise specified. In other words, the phrase "based on" means both "based only on" and "based at least on."

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

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

Also, "determining (deciding)" includes receiving (e.g., receiving information), transmitting (e.g., transmitting information), input, output, access ( accessing (e.g., accessing data in memory), etc.

Also, "determining" is considered to be "determining" resolving, selecting, choosing, establishing, comparing, etc. good too. That is, "determining (determining)" may be regarded as "determining (determining)" some action.

Also, "judgment (decision)" may be read as "assuming", "expecting", or "considering".

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

In this disclosure, when two elements are connected, using one or more wires, cables, printed electrical connections, etc., and as some non-limiting and non-exhaustive examples, radio frequency domain, microwave They can be considered to be “connected” or “coupled” together using the domain, electromagnetic energy having wavelengths in the optical (both visible and invisible) domain, and the like.

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 that "A and B are different from C". Terms such as "separate," "coupled," etc. may also be interpreted in the same manner as "different."

Where "include," "including," and variations thereof are used in this disclosure, these terms are inclusive, as is the term "comprising." is intended. Furthermore, the term "or" as used in this disclosure is not intended to be an exclusive OR.

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

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 as modifications and changes without departing from the spirit and scope of the invention determined based on the description of the claims. Therefore, the description of the present disclosure is for illustrative purposes and does not impose any limitation on the invention according to the present disclosure.

Claims

a receiver for receiving configuration information for a second SIB associated with a Public Land Mobile Network (PLMN) ID included in a first system information block (SIB);
a control unit that controls monitoring of the second SIB associated with the PLMN ID based on the configuration information of the second SIB.
The second SIB configuration information includes at least one of information on the second SIB period, information on the window length of the second SIB, and information on system information transmission request configuration. 2. The terminal of claim 1, wherein the terminal is
The terminal according to claim 1, wherein the control unit changes at least one setting based on the first SIB using the setting based on the second SIB.
The terminal according to claim 1, wherein the second SIB includes information on cell reselection.
receiving configuration information for a second SIB associated with a Public Land Mobile Network (PLMN) ID included in a first System Information Block (SIB);
and controlling monitoring of the second SIB associated with the PLMN ID based on configuration information of the second SIB.
a transmitter for transmitting configuration information of a second SIB associated with a Public Land Mobile Network (PLMN) ID included in a first system information block (SIB);
a control unit that controls transmission of the second SIB associated with the PLMN ID using configuration information of the second SIB.