Patent Description:
Long Term Evolution (LTE) has been specified for achieving a higher data rate, lower latency, and the like in a Universal Mobile Telecommunication System (UMTS) network. Future systems of LTE have also been studied for achieving a broader bandwidth and a higher speed on the basis of LTE. Examples of the future systems of LTE include systems called LTE-Advanced (LTE-A), Future Radio Access (FRA), 5th generation mobile communication system (<NUM>), <NUM> plus (<NUM>+), Radio Access Technology (New-RAT), New Radio (NR), and the like.

For future wireless communication systems (e.g., <NUM>), a technique of Integrated Access and Backhaul (IAB) that unifies an access link and a backhaul link is considered (Non-Patent Literature (hereinafter referred to as "NPL") <NUM>). In IAB, a wireless node like an IAB node forms a wireless access link with a User Equipment (UE), and also forms a wireless backhaul link with another IAB node and/or a wireless base station.

<NPL> describes agreements from the RAN1 #<NUM> and RAN #<NUM> meetings and describes the initial access procedure of IAB in NSA deployment and the SSB/RMSI periodicity assumed by the IAB node MT, and includes the following observations and proposals: Observation <NUM>: The current specification can already support a longer scheduling periodicity for RMSI. Proposal <NUM>: For initial access in NSA deployment, IAB node MT may need to ignore the barring signaling for the access UE. Proposal <NUM>: For initial cell selection, an IAB node MT may assume that half frames with SS/PBCH blocks occur with a periodicity of <NUM> frames, i.e., <NUM>. Proposal <NUM>: For initial cell selection, the RMSI periodicity assumed by the IAB node MT is same to that assumed by the access UE.

<CIT> Al describes methods and apparatus providing MTC in a wireless network. A narrow bandwidth within a wide system bandwidth is allocated for communicating data related to MTC. MTC control data generated for communicating over one or more MTC control channels for an MTC UE within the narrow bandwidth is transmitted over the one or more MTC control channels. The one or more MTC channels are multiplexed with one or more legacy channels over the wide system bandwidth. Also described is a transmission mode and content of the MTC control data or other MTC data.

However, no comprehensive study has been conducted on an initial access procedure related to the backhaul link of the wireless node like the IAB node, so that a further study is required.

One object of one aspect of the present disclosure is to provide a wireless node and a wireless communication method for optimizing the initial access procedure related to the backhaul link.

According to one aspect of the present disclosure there is provided a Integrated Access and Backhaul, IAB, node as set out in Claim <NUM>.

According to another aspect of the present disclosure there is provided a wireless communication control method as set out in Claim <NUM>.

According to another aspect of the present disclosure there is provided a system as set out in Claim <NUM>.

According to the present disclosure, it is possible to optimize the initial access procedure related to the backhaul link of the wireless node.

A wireless node described herein includes: a reception section that receives first information and second information; and a control section that controls whether or not to carry out initial access to a cell based on whether or not the second information indicates prohibition of the initial access when the first information indicates the prohibition of the initial access.

Hereinafter, a background example and an embodiment of the present disclosure will be described with reference to the accompanying drawings.

<FIG> illustrates a configuration example of a wireless communication system according to a Background Example <NUM> useful for understanding the present invention.

Wireless communication system <NUM> includes a plurality of IAB nodes 10A to 10C as one example of wireless nodes, and UE <NUM> as one example of a user equipment. Hereinafter, like in "IAB nodes <NUM>," only the common numeral of the reference signs may be used to describe IAB nodes 10A to 10C without distinguishing them from one another.

IAB nodes 10A to 10C are interconnected to one another by wireless communication. IAB node 10B is connected to IAB node 10A in <FIG>. IAB node 10C is connected to IAB node 10B. Hereinafter, IAB node 10A located upstream (in other words, in the direction nearer an IAB donor) as seen from IAB node 10B is called parent IAB node 10A, and IAB node 10C located downstream (in other words, in the direction away from the IAB donor) as seen from IAB node 10B is called child IAB node 10C.

The term "parent IAB node 10A" denotes that IAB node 10A is a parent IAB node with respect to IAB node 10B, and the term "child IAB node 10C" denotes that IAB node 10C is a child IAB node with respect to IAB node 10B. In other words, IAB node 10B corresponds to a child IAB node with respect to "parent IAB node 10A," and corresponds to a parent IAB node with respect to "child IAB node 10C.

Each of IAB nodes 10A to 10C forms a cell, which is an area in which the IAB node is available to communicate wirelessly. In other words, IAB nodes <NUM> have a function as a base station. UE <NUM> positioned in the cell is available to wirelessly connect to IAB node <NUM> which forms the cell.

IAB node 10A may also be connected to a Core Network (CN) through a Fiber Backhaul (BH). In this case, IAB node 10A may also be called "IAB donor. " Although <FIG> illustrates three IAB nodes <NUM> and one UE <NUM>, any number of IAB nodes <NUM> and any number of UEs <NUM> may be included in wireless communication system <NUM>. There may also be two or more parent IAB nodes with respect to one IAB node <NUM> and two or more child IAB nodes with respect to one IAB node <NUM>.

Note that, "L" with its subscripts illustrated in <FIG> denote the following:.

<FIG> illustrates a configuration example of each of IAB nodes <NUM>.

As illustrated in <FIG>, each of IAB nodes <NUM> includes control section <NUM>, Mobile Termination (MT) <NUM>, and Distributed Unit (DU) <NUM>. MT <NUM> and DU <NUM> may be functional blocks. Hereinafter, a function of MT <NUM> may be expressed as MT without the reference sign, and a function of DU <NUM> may be expressed as DU without the reference sign. DU <NUM> may have functions corresponding to those of the base station or an extension station. One example of MT <NUM> may have functions corresponding to those of the user equipment.

IAB node 10B is connected to upstream IAB node (or IAB donor) 10A by MT <NUM>. In other words, MT <NUM> of IAB node 10B processes connection to parent IAB node 10A.

IAB node 10B is connected to UE <NUM> and to the MT of downstream IAB node 10C by DU <NUM>. In other words, DU <NUM> of IAB node 10B processes connection to UE <NUM> and to child IAB node 10C. The connection to UE <NUM> and/or to child IAB node 10C by DU <NUM> may be establishment of a Radio Resource Control (RRC) channel, for example.

Control section <NUM> controls MT <NUM> and DU <NUM>. Operation of IAB node <NUM> described below may be achieved by control section <NUM> controlling MT <NUM> and DU <NUM>. Control section <NUM> may also be provided with a storage section for storing therein a variety of information.

Parent IAB node 10A indicates the following time resources for a link with parent IAB node 10A (hereinafter, referred to as "parent link") from a viewpoint of MT <NUM> of IAB node 10B:.

IAB node 10B, from a viewpoint of DU <NUM> of IAB node 10B, has the following types of time resources on a link between IAB node 10B and child IAB node 10C, and/or, on a link between IAB node 10B and UE <NUM> (these links are hereinafter referred to as "child link"):.

Each of the DL, UL, and FL time resources of the child link of the DU belongs to one of the following two classifications:.

New IAB node <NUM> is available to initially connect to existing IAB node <NUM> in accordance with the same initial connection procedure as that for UE <NUM> (see NPL <NUM>). The connection procedure may include cell search, System Information (SI) acquisition, and random access. The initial connection may also be referred to as "initial access.

Operation of the wireless communication system includes Stand Alone (SA) operation and Non Stand Alone (NSA) operation. In the case of SA operation, UE <NUM> is available to communicate with an NR wireless node (base station). In the case of NSA operation, UE <NUM> is available to communicate with an LTE wireless node (base station) and with the NR wireless node (base station). Hereinafter, the cell formed by the NR wireless node is called "NR cell" and the cell formed by the LTE wireless node is called "LTE cell.

Conceivable requirements relevant to SA and NSA are as follows (see Section <NUM>. <NUM> of NPL <NUM>):.

From the above requirements, the following are assumed:.

When new IAB node <NUM> connects to the network (e.g., existing IAB node <NUM>) by the same initial connection procedure as that for UE <NUM>, existing IAB node <NUM> may satisfy the following requirements (A1) and (A2) in order to support the initial connection from new IAB node <NUM>.

(A1) Synchronization Signal (SS)/Physical Broadcast Channel (PBCH) blocks are transmitted on a synchronization raster with a periodicity of <NUM> or less.

(A2) SIB1 (Remaining Minimum System Information (RMSI)) is transmitted.

However, it is assumed that, unlike normal UE <NUM>, IAB node <NUM> does not move at all or moves less frequently and to a smaller distance than normal UE <NUM>. For this reason, it is assumed that IAB node <NUM> switches connection targets less frequently than UE <NUM>. It is also assumed that IAB node <NUM> is less constrained by the size, battery, and processing load than UE <NUM>. It is thus assumed that the processing load for signal detection, for example, may be greater in IAB node <NUM> than in UE <NUM>. Because of such differences between UE <NUM> and IAB node <NUM>, SS/PBCH block transmissions and/or SIB1 transmissions to IAB node <NUM> do not necessarily need to be highly frequent (e.g., as frequent as those to UE <NUM>).

In addition, the above requirements (A1) and (A2) are not necessary in the NSA operation for UEs (the operation of Primary SCell (PSCell) with EN-DC). Therefore, the above requirements (A1) and (A2) become disadvantages, such as an increase in overhead and the like, for IAB node <NUM> not operating in the SA operation (operating in the NSA operation). In other word, the following (B1) and/or (B2) are conceivable for IAB node <NUM> in the NSA operation.

(B1) The transmission periodicity of SS/PBCH blocks and/or SIB1 may be longer than <NUM>. Alternatively, the transmission periodicity may also be <NUM> or longer.

(B2) In the case where the SA operation is not performed (in other words, in the case of the NSA), part of the parameter information of the SIB1 (RMSI) (e.g., cell selection information, SI scheduling information, and/or the like) is not necessarily needed.

In order for new IAB node <NUM> to initially connect to the network, new IAB node <NUM> performs a procedure for establishing Radio Resource Control (RRC) connection, such as transmission and reception processing on a Random Access Channel (RACH) and the like. For example, when UE <NUM> is available to receive the SIB1 in the LTE cell in the NSA operation for UEs, UE <NUM> does not have to receive the SIB1 in the NR cell since it is not essential for UE <NUM> to receive the SIB1 in the NR cell. Meanwhile, new IAB node <NUM> may receive part of the information in the SIB1 in order to initially connect to the network.

A description will be given of the initial connection procedure for IAB nodes with reference to <FIG> illustrates an example of the transmission periodicity of the SSB and SIB <NUM> of the NR cell in the SA operation. (B) in <FIG> illustrates an example of the transmission periodicity of the SSB of the NR cell in the NSA operation. (C) in <FIG> illustrates an example of the transmission periodicity of the SSB and SIB1 of existing IAB node <NUM> in the NSA operation.

For example, the following procedures (C1) and/or (C2) may be defined for the initial connection procedure for IAB nodes, which are different from those for UEs.

(C1) New IAB node <NUM> detects the SS/PBCH blocks under an assumption that the transmission periodicity of the SS/PBCH blocks is <NUM> or longer, for example. In other words, new IAB node <NUM> assumes a transmission periodicity equal to or longer than the transmission periodicity of the SS/PBCH blocks in the NR cell in the SA operation illustrated at (A) in <FIG>. The maximum value of the transmission periodicity may also be <NUM> or longer (see (C) in <FIG>).

(C2) Existing IAB node <NUM> may transmit part of information of the SIB1 with the same periodicity (e.g., at the same timings) as the periodicity of the SS/PBCH blocks. Alternatively, existing IAB node <NUM> may transmit this part of information of the SIB1 with a different periodicity (e.g., once every two transmission timings for the SS/PBCH blocks) from the periodicity of the SS/PBCH blocks (see (C) in <FIG>). The part of information of the SIB1 to be transmitted may, for example, include cellAccessRelatedInfo information, servingCellConfigCommonSIB information, and the like as the parameter information. Moreover, the part of information of the SIB1 to be transmitted does not have to include the cell selection information and/or SI scheduling information as the parameter information.

In the above (C2), existing IAB node <NUM> may also indicate, by using part of the information included in the PBCH (MIB), at least either information on the presence or absence of the part of information of the SIB1 described above (or, a PDCCH for scheduling of the part of information), or, information on the aforementioned transmission periodicity.

Alternatively, in the above (C2), information for indicating at least part of information on the transmission timing and/or periodicity of the part of information of the SIB1 described above (or, the PDCCH for scheduling of the part of information) may be fixed (defined) in specifications. For example, it may be defined that the highest X bits (X is an integer equal to or greater than one) of System Frame Number (SFN) indicates such information.

According to this initial connection procedure for IAB nodes, it is possible to reduce the overhead of a signal transmitted by existing IAB node <NUM> for the initial connection of new IAB node <NUM>, so as to enhance the spectral efficiency, since the transmission periodicity becomes longer and/or the amount of information to be transmitted decreases for this signal.

Next, the initial connection procedure for IAB nodes described above will be described in detail with reference to <FIG>, <FIG>, and <FIG>. <FIG> illustrates an example of the definition of the MIB. <FIG> illustrates an example of the definition of the kSSB in the case of Frequency Range (FR) <NUM>. <FIG> illustrates an example of the definition of the kSSB in the case of FR2. FR1 may be from <NUM> to <NUM>, and FR2 may be from <NUM> to <NUM>.

In the initial connection procedure for UEs, UE <NUM> assumes that the transmission periodicity of the SS/PBCH blocks during the initial connection is <NUM> (see Section <NUM> of NPL <NUM>).

In the initial connection procedure for IAB nodes as compared to this, IAB node <NUM> may assume that the transmission periodicity of the SSBs during the initial connection is longer than <NUM> described above. IAB node <NUM> may also assume that the transmission periodicity of the SSBs is any one of <NUM>, <NUM>, and <NUM>.

In the initial connection procedure for UEs, UE <NUM> determines presence or absence of a SIB1 transmission on the basis of a configuration of ssb-SubcarrierOffset (kSSB) (see Section <NUM> of NPL <NUM>). The ssb-SubcarrierOffset (kSSB) is used for the determination by UE <NUM> of the presence or absence of the SIB1 transmission, and is used for indication of a subcarrier offset between the SSB and the SIB1. In this respect, in particular, UE <NUM> determines that a control resource set for Type0-PDCCH Common Search Space is present if kSSB ≤ <NUM> for FR1, or UE <NUM> determines that the control resource set for Type0-PDCCH Common Search Space is absent if kSSB > <NUM> for FR1 (see <FIG>). Meanwhile, UE <NUM> determines that the control resource set for Type0-PDCCH Common Search Space is present if kSSB ≤ <NUM> for FR2, or UE <NUM> determines that the control resource set for Type0-PDCCH Common Search Space is absent if kSSB > <NUM> for FR2 (see <FIG>). The presence of the control resource set for Type0-PDCCH Common Search Space corresponds to the presence of the SIB1 transmission, and the absence of control resource set for Type0-PDCCH Common Search Space corresponds to the absence of the SIB1 transmission.

In the initial connection procedure for IAB nodes, the following option (D1) or (D2) may be defined.

(D1) In the initial connection procedure for IAB nodes, IAB node <NUM> recognizes (or determines) the presence or absence of the SIB <NUM> transmission by the same method as in the initial connection procedure for UEs. In other words, IAB node <NUM> determines that the SIB <NUM> is present if kSSB ≤ <NUM> for FR1, or IAB node <NUM> determines that the SIB1 is absent if kSSB > <NUM> for FR1 (see <FIG>). Meanwhile, IAB node <NUM> determines that the SIB is present if kSSB ≤ <NUM> for FR2, or IAB node <NUM> determines that the SIB1 is absent if kSSB > <NUM> for FR2 (see <FIG>). However, in the case of NSA operation, existing IAB node <NUM> indicates information ("barred") indicative of prohibition of interpretation to UE <NUM> in order to prevent UE <NUM> having received the information (MIB) for the IAB node from erroneously interpreting that the SIB1 is present. For example, existing IAB node <NUM> configures a parameter value "barred" in parameter information "cellBarred" of the MIB illustrated in <FIG>, and indicates it. Thus, IAB node <NUM> determines the presence or absence of the SIB1 by the aforementioned method even when the parameter value "cellBarred" of the MIB is the parameter value "barred.

(D2) In the initial connection procedure for IAB nodes, IAB node <NUM> recognizes (or determines) the presence or absence of the SIB1 transmission by a method different from the above method in the initial connection procedure for UEs. For example, a reserved bit of the PBCH is used, and new interpretations of the other bits of the PBCH in the case where the reserved bit is used are defined. Next, a description will be given of a particular example of such (D2). Hereinbelow, an example of the interpretations for each information of the MIB illustrated in <FIG> in the case of such (D2) is described.

In the initial connection procedure for IAB nodes, among values of kSSB which allow UE <NUM> to interpret that the SIB1 is absent, information (value) which does not affect the operation of UE <NUM> is indicated in ssb-SubcarrierOffset which is one element of parameter information of the MIB illustrated in <FIG>. For example, kSSB=<NUM> is indicated in the case of FR1, or kSSB=<NUM> is indicated in the case of FR2. Here, the reason for setting kSSB to "<NUM>" or "<NUM>" is because these values are Reserved and do not affect the operation of UE <NUM> as illustrated in <FIG>. UE <NUM> thus interprets that the SIB1 is absent as described above since kSSB=<NUM> > <NUM> in the case of FR1 or kSSB=<NUM> > <NUM> in the case of FR2.

In the initial connection procedure for IAB nodes, a value allowing interpretation that the SIB1 for IAB node <NUM> is present is indicated in spare, which is one element of parameter information of the MIB illustrated in <FIG>. For example, bit "<NUM>" is indicated in spare. Alternatively, without using the spare bit, it is interpreted that the SIB1 for the IAB node is present, when ssb-SubcarrierOffset has a specific value (e.g., <NUM> or <NUM>).

When the presence or absence of SIB1 for the IAB node is indicated using ssb-SubcarrierOffset, the presence or absence of SIB1 for the IAB node is indicated using the value of Reserved as described above. In this case, the subcarrier offset between the SSB and the SIB1 indicated in ssb-SubcarrierOffset in the initial connection procedure for UEs is not indicated in the initial connection procedure for IAB nodes. Thus, when the presence or absence of SIB1 for the IAB node is indicated using ssb-SubcarrierOffset, the subcarrier offset between the SSB and the SIB1 may be indicated by another method. For example, the subcarrier offset between the SSB and the SIB1 may be indicated by pdcch-ConfigSIB1.

In the initial connection procedure for IAB nodes, at least one of the SSB-SIB1 subcarrier offset and a PDCCH CORESET/search space configuration (PDCCH configuration) is indicated in pdcch-ConfigSIB <NUM>, which is one element of parameter information of the MIB illustrated in <FIG>. One example is described below.

In the case of FR1, <NUM> bits among all <NUM> bits of pdcch-ConfigSIB <NUM> are used for indication of the subcarrier offset between the SSB and the SIB1, and the remaining <NUM> bits are used for indication of the PDCCH configuration of the SIB1 for the IAB node. In the case of FR2, <NUM> bits among all the <NUM> bits of pdcch-ConfigSIB1 are used for indication of the subcarrier offset between the SSB and the SIB1, and the remaining <NUM> bits are used for indication of the PDCCH configuration of the SIB1 for the IAB node.

The PDCCH configuration may include at least one of information on the periodicity of SIB1 PDCCH for the IAB node, information on the timing of SIB1 PDCCH for the IAB node, information on the time-frequency resource location (location relative to the SSB) of SIB1 PDCCH for the IAB node, and information on a CORESET resource configuration. Information indicated by each code point may be different depending on at least one of Subcarrier Spacing (SSB SCS), SIB1 SCS, FR1 or FR2, and minimum channel bandwidth of a band, or a combination of two or more thereof. For example, a table may be defined for each combination of SCSs or for each minimum channel bandwidth.

In the initial connection procedure for IAB nodes, the SIB1 SCS is indicated in a normal way in SubCarrierSpacingCommon, which is one element of parameter information of the MIB illustrated in <FIG>.

Although the above descriptions have been given in relation to an example where IAB node <NUM> and UE <NUM> are distinguished from each other, the present background example is not limited to this example. In other words, IAB node <NUM> and UE <NUM> may be treated equally without being distinguished. For example, UE <NUM> instead of new IAB node <NUM> may connect to existing IAB node <NUM> (or IAB donor 10A). In other words, the wireless node may be any one of IAB node <NUM>, IAB donor 10A, and UE <NUM>, or may also be other than IAB node <NUM>, IAB donor 10A, and UE <NUM>. For example, the wireless node may also be expressed as a terminal, a wireless station, a relay node, or the like.

Additionally or alternatively, although the above descriptions have been given in relation to an example where the access link and the backhaul link are distinguished from each other, the present background example is not limited to this example. For example, a wireless link between IAB node <NUM> and UE <NUM> may also be one example of the backhaul link. In addition, the wireless link between IAB nodes <NUM> may also be one example of the access link. The terms "access link" and/or "backhaul link" described above are various examples of the wireless link. For example, the terms "access link" and/or "backhaul link" described above may also be expressed as a sidelink and the like.

In Background Example <NUM>, the wireless node (e.g., IAB node) includes: a reception section that receives information used for initial connection to another wireless node in a first cell; and a control section that controls the initial connection on the basis of the information, in which the control section controls reception of the information based on a periodicity equal to or longer than a periodicity defined for a user equipment in a second cell concerning transmission of the information.

This configuration makes it possible to optimize the initial connection procedure related to the backhaul link of the wireless node.

As in the descriptions for above Background Example1, the case where IAB node <NUM> initially connects to the network (e.g., existing IAB node) at a frequency for the NSA operation for UE <NUM> will be studied. In this case, on the supposition that the same method as in the initial connection at a frequency for the SA operation is used, the transmission periodicity of the SSB or RMSI may be assumed to be longer than <NUM> which is the transmission periodicity for UE <NUM>.

Since the aforementioned frequency is used for the NSA operation, it is required to support the initial connection of IAB node <NUM> while blocking the initial connection of UE <NUM>. To achieve this, it is conceivable that MT <NUM> of IAB node <NUM> ignores indication of the parameter information "cellbarred" of the MIB illustrated in <FIG>.

As understood, when MT <NUM> of IAB node <NUM> ignores the indication of the parameter information "cellbarred" of the MIB, the initial connection of MT <NUM> of IAB node <NUM> is required to be controlled by a method other than the parameter information "cellbarred" of the MIB (e.g., the initial connection is required to be blocked as needed). A description will thus be given for Embodiment <NUM> on a control method for the initial connection of MT <NUM> of IAB node <NUM>.

MT <NUM> of IAB node <NUM> obtains the SIB1 (or RMSI) even when the parameter value "barred" of the parameter information "cellbarred" of the MIB is indicated in the initial connection. Then, IAB node <NUM> performs the initial connection in that cell (or at the frequency) when the parameter value "barred" for MT <NUM> of IAB node <NUM> is not indicated explicitly or implicitly by the SIB1. Meanwhile, IAB node <NUM> does not perform the initial connection in that cell (or at the frequency) when such a parameter value "barred" is indicated explicitly or implicitly by the SIB1. This operation of IAB node <NUM> may be achieved by the following (E1), (E2), or (E3), for example.

(E1) InformationElement (IE) corresponding to the parameter information "cellbarrd" and/or "intraFreqReselection" are included in the SIB1 as new signaling for MT <NUM> of IAB node <NUM>. The parameter information "intraFreqReselection" is a parameter value for controlling cell selection or cell reselection for intra-frequency cells.

(E2) IAB node <NUM> determines, based on the presence or absence of other signaling for MT <NUM> of IAB node <NUM>, whether or not IAB node <NUM> is implicitly "barred. " For example, MT <NUM> of IAB node <NUM> may determine whether or not IAB node <NUM> is implicitly "barred," based on whether or not the SIB1 includes a RACH configuration, which is configuration information on the random access for MT <NUM> of IAB node <NUM>. For example, when the SIB1 includes the configuration information on the random access, IAB node <NUM> may determine that IAB node <NUM> is "notBarred. " Meanwhile, when the SIB1 does not include the configuration information on the random access, IAB node <NUM> may determine that IAB node <NUM> is "barred.

(E3) IAB node <NUM> may determine, based on the presence or absence of signaling for MT <NUM> of another IAB node <NUM>, whether or not IAB node <NUM> is implicitly "barred. " For example, when the signaling corresponding to "barred" for MT <NUM> of the other IAB node <NUM> is detected, IAB node <NUM> may determine itself to be implicitly "barred. " Meanwhile, when the signaling corresponding to "barred" for MT <NUM> of the other IAB node <NUM> is not detected, IAB node <NUM> may determine itself to be implicitly "notbarred.

Next, the above content will further be described with reference to <FIG>.

To begin with, the initial connection of MT <NUM> of IAB node <NUM> is described. MT <NUM> of IAB node <NUM> detects the SS/PBCH block and MIB (S101).

When the parameter value of the parameter information "cellbarred" of the obtained MIB indicates "barred" (S102), IAB node <NUM> ignores this parameter value "barred," and detects the SIB1 (S103). IAB node <NUM> may perform this SIB1 detection when the PBCH indicates the presence of RMSI. Then, when the implicit or explicit indication for MT <NUM> of IAB node <NUM> in the SIB1 indicates the parameter value "barred" (S104), MT <NUM> of IAB node <NUM> searches another cell or frequency (S105). Meanwhile, when the implicit or explicit indication in the SIB1 indicates the parameter value "notBarred," MT <NUM> of IAB node <NUM> carries out the initial connection (e.g., random access) (S114).

When the parameter value of the parameter information "cellbarred" of the obtained MIB indicates "notBarred" (S112), IAB node <NUM> detects the SIB1 (S103). IAB node <NUM> may perform this SIB1 detection when the PBCH indicates the presence of RMSI.

Then, when the implicit or explicit indication for MT <NUM> of IAB node <NUM> in the SIB1 indicates the parameter value "barred" (S104), MT <NUM> of IAB node <NUM> searches another cell or frequency (S105). Meanwhile, when the implicit or explicit indication in the SIB1 indicates the parameter value "notBarred" (S113), MT <NUM> of IAB node <NUM> carries out the initial connection (e.g., random access) (S114).

Next, the initial connection of UE <NUM> is described. UE <NUM> detects the SS/PBCH block and MIB (S101).

When the parameter value of the parameter information "cellbarred" of the obtained MIB indicates "barred" (S102), UE <NUM> searches another cell or frequency (S105).

When the parameter value of the parameter information "cellbarred" of the obtained MIB indicates "notBarred" (S112), UE <NUM> detects the SIB1 (S103). UE <NUM> may perform this SIB1 detection when the PBCH indicates the presence of RMSI. Then, UE <NUM> carries out the initial connection (e.g., random access). In other words, UE <NUM> carries out the initial connection (S114) irrespective of which of the parameter values "barred" (S104) and "notBarred" (S113) is indicated by the implicit or explicit indication for MT <NUM> of IAB node <NUM> in the SIB1.

According to the configuration and processing described above, wireless communication system <NUM> is available to control permission and/or blocking of the initial connection of MT <NUM> of IAB node <NUM> at the frequency for the NSA operation for UE <NUM>. The term "permission" may also be replaced with another term, such as "carrying out" or "approval. " The term "blocking" may also be replaced with another term, such as "stopping," "prohibition," "refusal," or "suppression.

In Embodiment <NUM>, the wireless node (e.g., IAB node <NUM>) includes: a reception section (e.g., MT <NUM>) that receives first information (e.g., MIB) and second information (e.g., SIB); and a control section (e.g., control section <NUM>) that controls whether or not to carry out initial access to a cell based on whether or not the second information indicates prohibition (e.g., "barred") of the initial access when the first information indicates the prohibition of the initial access.

Background example and embodiments of the present disclosure have been described above.

Note that the block diagrams used to describe the embodiments illustrate blocks on the basis of functions. These functional blocks (constituent sections) are implemented by any combination of hardware and/or software. A means for implementing the functional blocks is not particularly limited. That is, the functional blocks may be implemented by one physically and/or logically coupled apparatus. Two or more physically and/or logically separated apparatuses may be directly and/or indirectly (for example, via wires and/or wirelessly) connected, and the plurality of apparatuses may implement the functional blocks.

For example, IAB node <NUM>, UE <NUM>, and the like according to an embodiment of the present invention may function as a computer that executes processing of a wireless communication method of the present invention. <FIG> illustrates one example of a hardware configuration of an IAB node <NUM> and UE <NUM> according to one embodiment of the present invention. IAB node <NUM> and UE <NUM> described above may be physically constituted as a computer apparatus including processor <NUM>, memory <NUM>, storage <NUM>, communication apparatus <NUM>, input apparatus <NUM>, output apparatus <NUM>, bus <NUM>, and the like.

Note that the term "apparatus" in the following description can be replaced with a circuit, a device, a unit, or the like. The hardware configurations of IAB node <NUM> and UE <NUM> may include one apparatus or a plurality of apparatuses illustrated in the drawings or may not include part of the apparatuses.

The functions of IAB node <NUM> and UE <NUM> are implemented by predetermined software (program) loaded into hardware, such as processor <NUM>, memory <NUM>, and the like, according to which processor <NUM> performs the arithmetic and controls communication performed by communication apparatus <NUM> or reading and/or writing of data in memory <NUM> and storage <NUM>.

Processor <NUM> operates an operating system to entirely control the computer, for example. Processor <NUM> may be composed of a central processing unit (CPU) including an interface with peripheral apparatuses, a control apparatus, an arithmetic apparatus, a register, and the like. For example, control section <NUM>, MT <NUM>, DU <NUM>, and the like described above may be implemented by processor <NUM>.

Processor <NUM> reads a program (program code), a software module, and data from storage <NUM> and/or communication apparatus <NUM> to memory <NUM> and performs various types of processing according to the program (program code), the software module, and data. As the program, a program for causing the computer to perform at least a part of the operation described in the embodiments is used. For example, control section <NUM> may be implemented by a control program stored in memory <NUM> and operated by processor <NUM>, and the other functional blocks may also be implemented in the same way. While it has been described that the various types of processing as described above are performed by one processor <NUM>, the various types of processing may be performed by two or more processors <NUM> at the same time or in succession. Processor <NUM> may be implemented by one or more chips. Note that the program may be transmitted from a network through a telecommunication line.

Memory <NUM> is a computer-readable recording medium and may be composed of, for example, at least one of a Read Only Memory (ROM), an Erasable Programmable ROM (EPROM), an Electrically Erasable Programmable ROM (EEPROM), and a Random Access Memory (RAM). Memory <NUM> may be called as a register, a cache, a main memory (main storage apparatus), or the like. Memory <NUM> can save a program (program code), a software module, and the like that can be executed to carry out the wireless communication method according to an embodiment of the present invention.

Storage <NUM> is a computer-readable recording medium and may be composed of, for example, at least one of an optical disk such as a Compact Disc ROM (CD-ROM), a hard disk drive, a flexible disk, a magneto-optical disk (for example, a compact disc, a digital versatile disc, or a Blue-ray (registered trademark) disc), a smart card, a flash memory (for example, a card, a stick, or a key drive), a floppy (registered trademark) disk, and a magnetic strip. Storage <NUM> may also be called as an auxiliary storage apparatus. The storage medium as described above may be, for example, a database, a server, or other appropriate media including memory <NUM> and/or storage <NUM>.

Communication apparatus <NUM> is hardware (transmission and reception device) for communication between computers through a wired and/or wireless network and is also called as, for example, a network device, a network controller, a network card, or a communication module. For example, MT <NUM>, DU <NUM>, and the like described above may be implemented by communication apparatus <NUM>.

Input apparatus <NUM> is an input device (for example, a keyboard, a mouse, a microphone, a switch, a button, or a sensor) that receives input from the outside. Output apparatus <NUM> is an output device (for example, a display, a speaker, or an LED lamp) which makes outputs to the outside. Note that input apparatus <NUM> and output apparatus <NUM> may be integrated (for example, a touch panel).

The apparatuses, such as processor <NUM> and memory <NUM>, are connected by bus <NUM> for communication of information. Bus <NUM> may be composed of a single bus or by buses different among the apparatuses.

Furthermore, IAB node <NUM> and user equipment <NUM> may include hardware, such as a microprocessor, a digital signal processor (DSP), an Application Specific Integrated Circuit (ASIC), a Programmable Logic Device (PLD), and a Field Programmable Gate Array (FPGA), and the hardware may implement part or all of the functional blocks. For example, processor <NUM> may be implemented by at least one of these pieces of hardware.

A method of the notification of information is not limited to the aspects or embodiments described in the present specification, and the information may be notified by another method. For example, the notification of information may be carried out by one or a combination of physical layer signaling (for example, Downlink Control Information (DCI) and Uplink Control Information (UCI)), higher layer signaling (for example, Radio Resource Control (RRC) signaling, Medium Access Control (MAC) signaling, notification information (Master Information Block (MIB), and System Information Block (SIB))), and other signals. The RRC signaling may be called an RRC message and may be, for example, an RRC connection setup message, an RRC connection reconfiguration message, or the like.

The aspects and embodiments described herein may be applied to a system using Long Term Evolution (LTE), LTE-Advanced (LTE-A), SUPER <NUM>, IMT-Advanced, <NUM>, <NUM>, Future Radio Access (FRA), W-CDMA (registered trademark), GSM (registered trademark), CDMA2000, Ultra Mobile Broadband (UMB), IEEE <NUM> (Wi-Fi), IEEE <NUM> (WiMAX), IEEE <NUM>, Ultra-WideBand (UWB), Bluetooth (registered trademark), or other appropriate systems and/or to a next-generation system extended on the basis of the above systems.

The orders of the processing procedures, the sequences, the flow charts, and the like of the aspects and embodiments described herein may be changed as long as there is no contradiction. For example, elements of various steps are presented in exemplary orders in the methods described herein, and the methods are not limited to the presented specific orders.

Specific operations which are described in the specification as being performed by the base station may sometimes be performed by an upper node depending on the situation. It is obvious that various operations performed for communication with a terminal in a network including one network node or a plurality of network nodes including the base station can be performed by the base station and/or a network node other than the base station (examples include, but not limited to, MME or S-GW). Although there is one network node other than the base station in the case illustrated above, a plurality of other network nodes may be combined (for example, MME and S-GW).

Information and the like (* see the item of "information and signal") may be output from the higher layer (or lower layer) to the lower layer (or higher layer). The information, the signals, and the like may be input and output through a plurality of network nodes.

The input and output information and the like may be saved in a specific place (for example, memory) or may be managed by a management table. The input and output information and the like can be overwritten, updated, or additionally written. The output information and the like may be deleted. The input information and the like may be transmitted to another apparatus.

The determination may be made on the basis of a value expressed by one bit (zero or one), on the basis of a Boolean value (true or false), or on the basis of comparison with a numerical value (for example, comparison with a predetermined value).

The aspects and embodiments described herein may be independently used, may be used in combination, or may be switched and used along the execution. Furthermore, notification of predetermined information (for example, notification indicating "it is X") is not limited to explicit notification, and may be performed implicitly (for example, by not notifying the predetermined information).

Regardless of whether the software is called as software, firmware, middleware, a microcode, or a hardware description language or by another name, the software should be broadly interpreted to mean an instruction, an instruction set, a code, a code segment, a program code, a program, a subprogram, a software module, an application, a software application, a software package, a routine, a subroutine, an object, an executable file, an execution thread, a procedure, a function, and the like.

The software, the instruction, and the like may be transmitted and received through a transmission medium. For example, when the software is transmitted from a website, a server, or another remote source by using a wired technique, such as a coaxial cable, an optical fiber cable, a twisted pair, and a digital subscriber line (DSL), and/or a radio technique, such as an infrared ray, a radio wave, and a microwave, the wired technique and/or the radio technique is included in the definition of the transmission medium.

The information, the signals, and the like described herein may be expressed by using any of various different techniques. For example, data, instructions, commands, information, signals, bits, symbols, chips, and the like that may be mentioned throughout the entire description may be expressed by one or an arbitrary combination of voltage, current, electromagnetic waves, magnetic fields, magnetic particles, optical fields, and photons.

Note that the terms described herein and/or the terms necessary for understanding the present specification may be replaced with terms with the same or similar meaning. For example, the channel and/or the symbol may be a signal. The signal may be a message. The component carrier (CC) may be called as a carrier frequency, a cell, or the like.

The terms "system" and "network" used herein can be interchangeably used.

The information, the parameters, and the like described herein may be expressed by absolute values, by values relative to predetermined values, or by other corresponding information. For example, radio resources may be indicated by indices.

The names used for the parameters are not limited in any respect. Furthermore, the numerical formulas and the like using the parameters may be different from the ones explicitly disclosed in the present specification. Various channels (for example, PUCCH and PDCCH) and information elements (for example, TPC) can be identified by any suitable names, and various names assigned to these various channels and information elements are not limited in any respect.

The base station can accommodate one cell or a plurality of (for example, three) cells (also called sector). When the base station accommodates a plurality of cells, the entire coverage area of the base station can be divided into a plurality of smaller areas, and each of the smaller areas can provide a communication service on the basis of a base station subsystem (for example, small base station for indoor, remote radio head (RRH)). The term "cell" or "sector" denotes part or all of the coverage area of the base station and/or of the base station subsystem that provides the communication service in the coverage. Furthermore, the terms "base station", "eNB", "cell", and "sector" can be interchangeably used in the present specification. The base station may be called as a fixed station, a NodeB, an eNodeB (eNB), an access point, a femto cell, a small cell, or the like.

The mobile station may be called, by those skilled in the art, a subscriber station, a mobile unit, a subscriber unit, a wireless unit, a remote unit, a mobile device, a wireless device, a wireless communication device, a remote device, a mobile subscriber station, an access terminal, a mobile terminal, a wireless terminal, a remote terminal, a handset, a user agent, a mobile client, a client, or by some other appropriate terms.

As used herein, the term "determining" may encompass a wide variety of actions. For example, "determining" may be regarded as judging, calculating, computing, processing, deriving, investigating, looking up (for example, looking up in a table, a database or another data structure), ascertaining and the like. Furthermore, "determining" may be regarded as receiving (for example, receiving information), transmitting (for example, transmitting information), inputting, outputting, accessing (for example, accessing data in a memory) and the like. Also, "determining" may be regarded as resolving, selecting, choosing, establishing and the like. That is, "determining" may be regarded as a certain type of action related to determining.

The terms "connected" and "coupled" as well as any modifications of the terms mean any direct or indirect connection and coupling between two or more elements, and the terms can include cases in which one or more intermediate elements exist between two "connected" or "coupled" elements. The coupling or the connection between elements may be physical or logical coupling or connection or may be a combination of physical and logical coupling or connection. When the terms are used in the present specification, two elements can be considered to be "connected" or "coupled" to each other by using one or more electrical wires, cables, and/or printed electrical connections or by using electromagnetic energy, such as electromagnetic energy with a wavelength of a radio frequency domain, a microwave domain, or an optical (both visible and invisible) domain that are non-limiting and non-inclusive examples.

The reference signal can also be abbreviated as an RS and may also be called as a pilot depending on the applied standard.

The description "on the basis of" used herein does not mean "on the basis only of," unless otherwise specifically stated. In other words, the description "on the basis of" can mean both of "on the basis of only" and "on the basis of at least.

Any reference to elements by using the terms "first," "second," and the like that are used in the present specification does not generally limit the quantities of or the order of these elements. The terms can be used as a convenient method of distinguishing between two or more elements in the present specification. Therefore, reference to first and second elements does not mean that only two elements can be employed there, or that the first element has to precede the second element somehow.

The "means" in the configuration of each apparatus described above may be replaced with "section," "circuit," "device," or the like.

The terms "including," "comprising," and modifications of these terms are intended to be inclusive just like the term "having," as long as the terms are used in the present specification or the appended claims. Furthermore, the term "or" used herein or the appended claims is not intended to be an exclusive or.

The radio frame may be constituted by one frame or a plurality of frames in the time domain. The one frame or each of the plurality of frames may be called a subframe in the time domain. The subframe may be further constituted by one slot or a plurality of slots in the time domain. The slot may be further constituted by one symbol or a plurality of symbols (OFDM symbol, SC-FDMA symbol, or the like) in the time domain. The radio frame, the subframe, the slot, and the symbol indicate time units in transmitting signals. The radio frame, the subframe, the slot, and the symbol may be called by other corresponding names. For example, in the LTE system, the base station creates a schedule for assigning radio resources to each mobile station (such as frequency bandwidth that can be used by each mobile station and/or transmission power). The minimum time unit of scheduling may be called as a Transmission Time Interval (TTI). For example, one subframe, a plurality of continuous subframes, or one slot may be called as a TTI. The resource block (RB) is a resource assignment unit in the time domain and the frequency domain, and the resource block may include one subcarrier or a plurality of continuous subcarriers in the frequency domain. In addition, the resource block may include one symbol or a plurality of symbols in the time domain, and may have a length of one slot, one subframe, or one TTI. One TTI and one subframe may be constituted by one resource block or a plurality of resource blocks. The structure of the radio frame is illustrative only, and the number of subframes included in the radio frame, the number of slots included in the subframe, the numbers of symbols and resource blocks included in the slot, and the number of subcarriers included in the resource block can be changed in various ways.

The "maximum transmit power" described in the present examples may mean a maximum value of the transmit power, but is not limited to the maximum value of the transmit power and may also be the nominal UE maximum transmit power or the rated UE maximum transmit power.

When articles, such as "a," "an," and "the" in English, are added by translation in the entire disclosure, the articles include plural forms unless otherwise clearly indicated by the context.

Claim 1:
An Integrated Access and Backhaul, IAB, node (<NUM>: 10A), comprising:
a Mobile Termination, MT section, (<NUM>) configured to receive a master information block, and a system information block <NUM>, SIB1; and
a control section (<NUM>) configured to ignore, in the master information block, a first parameter for indicating that initial access to a cell is barred and to determine whether or not the initial access to the cell is barred based on a second parameter, in the SIB <NUM>, indicating whether or not the initial access to the cell is barred.