Sub-band operation in unlicensed spectrum for new radio

Abstract

To provide an apparatus that adjusts communications between devices such as wireless terminals and base stations using Sub-band (SB) indications and Listen-Before-Talk (LBT) outcomes.SOLUTION: A wireless terminal receives SB indications including SB configurations and LBT outcomes of a base station, and other information such as a remapped Control Resource Set (CORESET). Similarly, the wireless terminal determines that a physical resource block (PRB) is invalid based at least in part on whether the PRB overlaps with a guard band. The wireless terminal adjusts its searches and transmissions based on the received SB indications and provides the base station with LBT outcomes of the terminal.SELECTED DRAWING: None

Description

Summary of the Invention

[0001] Sub-band (SB) interference is used to coordinate communications between devices such as wireless terminals and base stations. Digitization and listen-before-talk (LBT) results can be used. A wireless terminal device such as a user equipment (UE) transmits SB information including the SB configuration and LBT results of the base station. After receiving an indication, such information can be used in a variety of ways.

[0002] For example, the UE may use the remapped control resource set (CORESET) Similarly, the UE can receive the physical resources in the CORESET from the base station. Based on whether a PRB in a group of blocks (PRBs) overlaps with a guard band Similarly, the UE may determine that the PRB overlaps with a guard band. Based on whether the PRBs overlap, the group of PRBs can be determined to be invalid. Furthermore, the device may determine that the invalid PRB does not carry a physical downlink control channel (PDCCH). It can be assumed.

[0003] The device is configured to transmit MSG3 in the Random Access Channel (RACH) procedure. The method may be configured to select a transmission opportunity, such transmission opportunity being in a frequency domain, The transmission opportunities may be separated in the time domain, or both. For example, the transmission opportunities may be separated in the random access The RAR can be selected based on the MSG3 sub-band or band Width Part (BWP) is a guard band shift that is used to Opportunities can be inferred. Opportunities are provided by one or more MSG2 messages. By random selection from multiple MSG3 transmission opportunities available or by device identification. It can be determined based on an identifier (ID).

[0004] Similarly, the transmission opportunity for RACH MSG3 may be selected in the time domain. The session may be selected based on a random access response (RAR).

[0005] The equipment shall be able to receive an indication of LBT type in MSG3 of the RACH procedure. For example, the LBT type schedules a Random Access Response (RAR). This may be indicated in the downlink control information (DCI) or in the RAR itself.

[0006] The device passes the boundary between available and unavailable LBT subbands. The Channel State Information Reference Signal (CS For I-RS), whether the CSI-RS subband is omitted completely or partially , it can be determined whether the signal falls within the available subband. The band may be, for example, a guard band or bands that are indicated as unavailable based on the base station's LBT results. may be an LBT subband.

[0007] The device may, for example, receive a CSI-RS belonging to the base station prior to successful channel acquisition. By omitting one or more orthogonal frequency division multiplexing (OFDM) symbols that carry When the base station acquires the channel, it transmits one or more OFDM symbols carrying CSI-RS or CSI-RS. Based at least in part on the success of the CSI-RS, the assumptions can be adjusted.

[0008] The terminal device can provide assistance information to the base station, and the assistance information is related to the LBT result of the device. After that, the device can receive, for example, an adjusted SB indication from the base station. One or more SB indications and assistance information can be exchanged between the device and the base station during a period of a first part of the maximum channel occupancy time (MCOT). For example, the adjusted SB indication is received during a period of a second part of the MCOT. The assistance information can include one or more suitable downlink (DL) sub-bands.

[0009] The SB indication can be carried in group communication. For example, one or more SB indications include a group identifier.

[0010] Furthermore, the device can adjust the search space based at least in part on the available sub-bands.

[0011] This summary is provided to introduce, in a simplified form, a selection of concepts that are further described in the following detailed description. This summary is not intended to identify key features or essential features of the claimed subject matter, nor is it intended to be used to limit the scope of the claimed subject matter. Furthermore, the claimed subject matter is not limited to limitations that solve any or all of the disadvantages described in any part of this disclosure.

[0012] A more detailed understanding can be obtained from the following description, which is presented by way of example in conjunction with the accompanying drawings.

Brief Description of the Drawings

[0013]

Figure 1

Figure 2

Figure 3

Figure 4

Figure 5

Figure 6

Figure 7

Figure 8

Figure 9

Figure 10

Figure 11

Figure 12

Figure 13

Figure 14

Figure 15

Figure 16

Figure 17

Figure 18

Figure 19

Figure 20

Figure 21

Figure 22

Figure 23

Figure 24

Figure 25

Figure 26

Figure 27A

Figure 27B

Figure 27C

Figure 27D

Figure 27E

Figure 27F

Figure 27G

Figure 28

Figure 29

Figure 30A

Figure 30B

Figure 31

Figure 32

Figure 33

Figure 34

Figure 35

Figure 36

Figure 37

Figure 38

Figure 39

[0014] Some of the acronyms used in this specification are listed in Table 1 of the appendix.

[0015] The term "procedure" generally refers to a way of performing operations to achieve a specific purpose. That is. The term "procedure" applies to machine-to-machine (M2M) and mo In the context of Internet-of-Things (IoT) applications To avoid confusion with the special meaning of the term "method" in this context, the term "way" is used instead The steps described for the procedure are often optional and can be performed in various ways and in various orders. Therefore, in this specification, the term "procedure" should not be construed as referring to a fixed set and sequence of steps, but rather should be construed as referring to a general methodology for achieving results that can be adapted in various ways and should be interpreted as such

[0016] (Unlicensed spectrum in NR) Millimeter waves have a wider range of unlicensed spectrum available for further use to achieve higher data rates than can be achieved by operating in frequency bands below 6 GHz There is. Previous study items (SIs) and current work items (WIs) related to NR unlicensed have considered procedures to enhance coexistence with other technologies operating unlicensed, such as NR-U and, for example, WiFi devices, LTE -based LAA devices, other NR-U devices, etc., and to meet regulatory requirements, without significantly degrading NR-U devices in terms of throughput and latency and will be specified over a wide range without significantly degrading NR-U devices in terms of throughput and latency and will be considered and specified over a wide range will be

[0017] (NR bandwidth adaptation) According to bandwidth adaptation (BA), the receive and transmit bandwidths of the UE do not need to be as large as the cell bandwidth and are adjustable That is, to change the width (e.g., electrical It can be instructed to shrink during periods of low activity to conserve power, and the position can move in the frequency region (e.g., to increase scheduling flexibility), and it can be instructed to change the subcarrier spacing (e.g., to enable different services). A subset of the total cell bandwidth of a cell is called a bandwidth part (BWP). BA is achieved by configuring the UE with BWPs and informing the UE which of the configured BWPs is currently active. A serving cell can be composed of up to 4 BWPs. In the case of an activated serving cell, there is always one active BWP at any given time.

[0018] Figure 1 illustrates a scenario in which three different BWPs are configured. · BWP1 with a width of 40 MHz and a subcarrier spacing of 15 kHz. · BWP2 with a width of 10 MHz and a subcarrier spacing of 15 kHz. · BWP3 with a width of 20 MHz and a subcarrier spacing of 60 kHz.

[0019] (NR Random Access Procedure) The random access procedure is described, for example, in 3GPP TS38.300, NR, NR and N G-RAN Overview, Stage 2 (Release 15), V15.0.0 (3GPP TS 38.300, N R; NR and NG-RAN Overall Description; Stage 2 (Release 15), V15.0.0) and 3GPP TS38.213, Physical layer procedures for control (Release 15), V15 .1.0 (3GPP TS 38.213, Physical layer procedures for control (Release ​​​​​15), as described in V15.1.0), is triggered by several events . ·Initial access from RRC idle (RRC_IDLE). ·RRC connection re-establishment procedure. ·Handover. ·DL or UL data arrival during RRC connected (RRC_CONNECTED) when the UL synchronization state is "asynchronous". ·Transition from RRC inactive (RRC_INACTIVE). ·Request for other SI. ·Recovery from beam failure.

[0020] Furthermore, the random access procedure takes two different forms, contention-based and contention-free, as shown in Figure 2. Normal DL / UL transmission can be performed after the random access procedure. .

[0021] In the case of initial access in a cell composed of Supplementary Uplink (SUL), the UE selects the SUL carrier only when the measured quality of the DL is lower than the broadcast threshold. All uplink transmissions of the random access procedure remain on the selected carrier once started.

[0022] (Example of problem) (Problem 1: Sub-band configuration and indication of LBT result) In NR-U, to increase the possibility of accessing the channel and to cope with the inaccessibility of the channel that may be experienced when Listen Before Talk (LBT) is executed over the entire frequency band assigned to the BWP and only a part of this band is occupied by other nodes, a frequency granularity smaller than the Bandwidth Part (BWP), i.e., operating in sub-bands, ​ This is beneficial. Therefore, it is interesting to describe an efficient procedure for configuring sub-bands within a BWP. Furthermore, it is important to develop a procedure for indicating the results of LBT across all sub-bands within a BWP so that the UE can adjust its own operations when monitoring various signaling and channels.

[0023] (Problem 2: Configuration of CORESET during sub-band-based LBT) In NR, a control resource set (CORESET) is defined for a BWP that includes the frequency resources of the CORESET. When adopting sub-band-based LBT, depending on the relative position between the frequency domain resources of the CORESET and the sub-bands, further problems arise. For example, a sub-band that includes all the frequency domain resources of the CORESET may not be available, while other sub-bands within the same BWP may be available. Furthermore, in a large-scale CORESET with frequency domain resources spanning multiple sub-bands, if some of those sub-bands are unavailable, the UE is very likely to fail to decode the associated downlink control information (DCI). Next, a method for configuring the CORESET to increase its transmission opportunities and a method for indicating those configurations to the UE for proper CORESET monitoring are described.

[0024] (Problem 3: Uplink BWP switching for RACH and Beam Failure Recovery (BFR)) Enabling dynamic UL BWP switching is also beneficial for increasing the UE's access probability to the channel and reducing the impact of channel unavailability due to LBT failures. ​ To achieve this objective, it is necessary to address the issue of UL BWP switching during the random access procedure or during the beam failure recovery procedure. Furthermore, it is necessary to address the issue of UL resource allocation to the UE for MSG3 transmission or for the transmission of beam failure recovery request (BFRQ) that supports UL BWP switching during the random access procedure or during the beam failure recovery procedure. To address the issue of UL BWP switching during the random access procedure or during the beam failure recovery procedure. To address the issue of UL resource allocation to the UE for MSG3 transmission or for the transmission of beam failure recovery request (BFRQ) that supports UL BWP switching during the random access procedure or during the beam failure recovery procedure. To address the issue of UL resource allocation to the UE for MSG3 transmission or for the transmission of beam failure recovery request (BFRQ) that supports UL BWP switching during the random access procedure or during the beam failure recovery procedure. To address the issue of UL resource allocation to the UE for MSG3 transmission or for the transmission of beam failure recovery request (BFRQ) that supports UL BWP switching during the random access procedure or during the beam failure recovery procedure.

[0025] (Sub-band configuration and indication procedure) (Sub-band configuration) In NR-U, channel access depends on the result of the extended channel sensing procedure, and thus there is uncertainty as to whether the channel has been successfully acquired when either the gNB or the UE is transmitting at least one of the signals and channels. Sub-band operation helps to mitigate the adverse effects of channel unavailability, especially when a small part of the allocated frequency band operating BWP is occupied by other nodes and the rest is available. In sub-band operation, the BWP can be divided into equal bandwidths or unequal bandwidths, as shown in FIGS. 3A and 3B, respectively. The essence of adopting sub-bands is to operate at a finer frequency granularity than the BWP in order to increase the likelihood that the gNB or the UE can acquire the channel. In NR-U, channel access depends on the result of the extended channel sensing procedure, and thus there is uncertainty as to whether the channel has been successfully acquired when either the gNB or the UE is transmitting at least one of the signals and channels. Sub-band operation helps to mitigate the adverse effects of channel unavailability, especially when a small part of the allocated frequency band operating BWP is occupied by other nodes and the rest is available. In sub-band operation, the BWP can be divided into equal bandwidths or unequal bandwidths, as shown in FIGS. 3A and 3B, respectively. The essence of adopting sub-bands is to operate at a finer frequency granularity than the BWP in order to increase the likelihood that the gNB or the UE can acquire the channel. In NR-U, channel access depends on the result of the extended channel sensing procedure, and thus there is uncertainty as to whether the channel has been successfully acquired when either the gNB or the UE is transmitting at least one of the signals and channels. Sub-band operation helps to mitigate the adverse effects of channel unavailability, especially when a small part of the allocated frequency band operating BWP is occupied by other nodes and the rest is available. In sub-band operation, the BWP can be divided into equal bandwidths or unequal bandwidths, as shown in FIGS. 3A and 3B, respectively. The essence of adopting sub-bands is to operate at a finer frequency granularity than the BWP in order to increase the likelihood that the gNB or the UE can acquire the channel. In NR-U, channel access depends on the result of the extended channel sensing procedure, and thus there is uncertainty as to whether the channel has been successfully acquired when either the gNB or the UE is transmitting at least one of the signals and channels. Sub-band operation helps to mitigate the adverse effects of channel unavailability, especially when a small part of the allocated frequency band operating BWP is occupied by other nodes and the rest is available. In sub-band operation, the BWP can be divided into equal bandwidths or unequal bandwidths, as shown in FIGS. 3A and 3B, respectively. The essence of adopting sub-bands is to operate at a finer frequency granularity than the BWP in order to increase the likelihood that the gNB or the UE can acquire the channel. In NR-U, channel access depends on the result of the extended channel sensing procedure, and thus there is uncertainty as to whether the channel has been successfully acquired when either the gNB or the UE is transmitting at least one of the signals and channels. Sub-band operation helps to mitigate the adverse effects of channel unavailability, especially when a small part of the allocated frequency band operating BWP is occupied by other nodes and the rest is available. In sub-band operation, the BWP can be divided into equal bandwidths or unequal bandwidths, as shown in FIGS. 3A and 3B, respectively. The essence of adopting sub-bands is to operate at a finer frequency granularity than the BWP in order to increase the likelihood that the gNB or the UE can acquire the channel. In NR-U, channel access depends on the result of the extended channel sensing procedure, and thus there is uncertainty as to whether the channel has been successfully acquired when either the gNB or the UE is transmitting at least one of the signals and channels. Sub-band operation helps to mitigate the adverse effects of channel unavailability, especially when a small part of the allocated frequency band operating BWP is occupied by other nodes and the rest is available. In sub-band operation, the BWP can be divided into equal bandwidths or unequal bandwidths, as shown in FIGS. 3A and 3B, respectively. The essence of adopting sub-bands is to operate at a finer frequency granularity than the BWP in order to increase the likelihood that the gNB or the UE can acquire the channel. In NR-U, channel access depends on the result of the extended channel sensing procedure, and thus there is uncertainty as to whether the channel has been successfully acquired when either the gNB or the UE is transmitting at least one of the signals and channels. Sub-band operation helps to mitigate the adverse effects of channel unavailability, especially when a small part of the allocated frequency band operating BWP is occupied by other nodes and the rest is available. In sub-band operation, the BWP can be divided into equal bandwidths or unequal bandwidths, as shown in FIGS. 3A and 3B, respectively. The essence of adopting sub-bands is to operate at a finer frequency granularity than the BWP in order to increase the likelihood that the gNB or the UE can acquire the channel. In NR-U, channel access depends on the result of the extended channel sensing procedure, and thus there is uncertainty as to whether the channel has been successfully acquired when either the gNB or the UE is transmitting at least one of the signals and channels. Sub-band operation helps to mitigate the adverse effects of channel unavailability, especially when a small part of the allocated frequency band operating BWP is occupied by other nodes and the rest is available. In sub-band operation, the BWP can be divided into equal bandwidths or unequal bandwidths, as shown in FIGS. 3A and 3B, respectively. The essence of adopting sub-bands is to operate at a finer frequency granularity than the BWP in order to increase the likelihood that the gNB or the UE can acquire the channel. In NR-U, channel access depends on the result of the extended channel sensing procedure, and thus there is uncertainty as to whether the channel has been successfully acquired when either the gNB or the UE is transmitting at least one of the signals and channels. Sub-band operation helps to mitigate the adverse effects of channel unavailability, especially when a small part of the allocated frequency band operating BWP is occupied by other nodes and the rest is available. In sub-band operation, the BWP can be divided into equal bandwidths or unequal bandwidths, as shown in FIGS. 3A and 3B, respectively. The essence of adopting sub-bands is to operate at a finer frequency granularity than the BWP in order to increase the likelihood that the gNB or the UE can acquire the channel.

[0026] The solutions developed for configuring sub-bands fall into two main categories. In the first set of solutions, a set of sub-bands within the active DL BWP is configured for the UE. The UE configures a set of sub-bands within the active DL BWP based on the LBT result at the gNB. The solutions developed for configuring sub-bands fall into two main categories. In the first set of solutions, a set of sub-bands within the active DL BWP is configured for the UE. The UE configures a set of sub-bands within the active DL BWP based on the LBT result at the gNB. The solutions developed for configuring sub-bands fall into two main categories. In the first set of solutions, a set of sub-bands within the active DL BWP is configured for the UE. The UE configures a set of sub-bands within the active DL BWP based on the LBT result at the gNB. Monitor the available sub-bands within the set of sub-bands initially configured within P (associated with a successful LBT). The UE cannot monitor other sub-bands outside the set of configured sub-bands within the active DL BWP until this configuration is updated. Therefore, this category of solutions is called LBT-independent sub-band configuration. In a second category, this document proposes a set of alternative solutions. Thus, the gNB may indicate only the available sub-bands within the active DL BWP among the set of sub-band configurations based on the LBT results at the gNB. Therefore, when a particular set of sub-bands within the active DL BWP is shown to be available, the UE is expected to monitor all of them. This category of solutions is called LBT-dependent sub-band configuration. The main difference between the two categories is that in the former set of solutions, some of the configured sub-bands may be unavailable due to LBT failures, whereas in the latter set of solutions, all the indicated sub-bands are always available. Further, in the former set of solutions, the gNB can explicitly indicate to the UE that some sub-bands are always discarded, whereas in the latter set of solutions, such an indication is implicitly achieved as described in this text. until this configuration is updated. outside the set of configured sub-bands within the active DL BWP. Therefore, this category of solutions is called LBT-independent sub-band configuration. In a second category, this document proposes a set of alternative solutions. Thus, the gNB may indicate only the available sub-bands within the active DL BWP among the set of sub-band configurations based on the LBT results at the gNB. Therefore, when a particular set of sub-bands within the active DL BWP is shown to be available, the UE is expected to monitor all of them. This category of solutions is called LBT-dependent sub-band configuration. The main difference between the two categories is that in the former set of solutions, some of the configured sub-bands may be unavailable due to LBT failures, whereas in the latter set of solutions, all the indicated sub-bands are always available. Further, in the former set of solutions, the gNB can explicitly indicate to the UE that some sub-bands are always discarded, whereas in the latter set of solutions, such an indication is implicitly achieved as described in this text. In the former set of solutions, some of the configured sub-bands may be unavailable due to LBT failures, whereas in the latter set of solutions, all the indicated sub-bands are always available. Further, in the former set of solutions, the gNB can explicitly indicate to the UE that some sub-bands are always discarded, whereas in the latter set of solutions, such an indication is implicitly achieved as described in this text. In addition to both categories of solutions, another set of solutions that may be adopted is called UE-assisted sub-band selection, where the UE assists the gNB in determining suitable downlink sub-bands. Such assistance may be that some of them are unavailable from the UE's perspective.

[0027] In addition to both categories of solutions, another set of solutions that may be adopted is called UE-assisted sub-band selection, where the UE assists the gNB in determining suitable downlink sub-bands. Such assistance may be that some of them are unavailable from the UE's perspective. In such assistance, some of them are unavailable from the UE's perspective. When capable of indicating those selected sub - bands, it may be beneficial to avoid the problem of hidden nodes where the UE may further narrow down the provided downlink sub - bands. Furthermore, in the operation of time - division duplex (TDD) or frequency - division duplex (FDD), the UE can monitor the downlink sub - bands only when the downlink sub - bands are available from the UE's perspective (LBT at the UE is successful). Alternatively or additionally, the UE can monitor the downlink sub - bands when the downlink sub - bands are available from the UE's perspective (LBT at the UE is successful) and there is at least one UL sub - band where LBT is successful. Similarly, if the UE has no available UL sub - bands, the UE may not monitor the downlink sub - bands even if they are available. Figure 4 shows the main differences between two categories of solutions. In Figure 4A, the UE receives a sub - band configuration that does not depend on LBT, where SB0, SB2, and SB3 are allocated within the active DL BWP. In this case, the UE monitors only these sub - bands. If any of them is unavailable, the gNB can indicate the unavailable sub - bands, and the UE monitors only the available sub - bands among those initially configured. To monitor new sub - bands, the UE needs to receive a new configuration. On the other hand, Figure 4B shows an overview of a solution in the second category, for example, a sub - band configuration that depends on LBT. There, the gNB indicates the sub - bands that the UE can monitor hereafter each time LBT is successful at the gNB.

[0028]

[0029] ​​​​​​​​​​​​​​Figure 4 is a schematic diagram of the differences between two categories of solutions. Figure 4A shows a sub-band configuration that does not depend on LBT and Figure 4B shows a sub-band configuration solution that depends on LBT.

[0030] (Static configuration of sub-bands) (Sub-band configuration that does not depend on LBT) When the sub-bands (SBs) have equal bandwidths, for each configured BWP, the UE can be configured using, for example, higher layer parameters such as NumEqSB and BandwidthSB, to determine the number of equal SBs and the associated SB bandwidths. The UE can assume that the SB with the lowest sub-band index occupies the lowest physical resource block (PRB) within the BWP that contains the sub-bands, and that the next sub-band index occupies the next set of PRBs incrementally. The index of the SBs can be arranged in ascending order with respect to the occupied PRBs, as shown in, for example, Figure 3A. Alternatively, in this document, a higher layer

[0031] configuration message such as an SB information element (IE) is proposed, and an example is given in Information Element 1 of the appendix. This can be used to configure each SB separately using, for example, unequal bandwidths and non-uniform frequency domain positions, as shown in Figure 3B. Each BWP can be composed of multiple SBs configured via multiple information elements. See Information Element 1 of the appendix for an example of the SB information element. Table 2 includes an explanation of the SB IE parameters.

[0032]

[0033]

[0034] If discontinuous sub-bands are applicable, in order to allow for them, in this document, locati​​​​ Instead of onAndBandwidth, it is proposed to configure their frequency domain resources via upper layer parameters such as frequencyDomainResources and RRC parameters. For example, these parameters may be bit strings of 45-bit size, and each bit may correspond to a group of 6 PRBs grouped starting from PRB0 that is completely included in the BWP including the subband. Further, the most significant bit may correspond to the lowest frequency group that is completely included in the BWP in which the subband is configured, and if there are subsequent lower bits, each of them may correspond to the next lower frequency group that is completely included in the BWP in which the subband is configured. Bits corresponding to groups that are not completely included in the BWP in which the subband is configured are set to zero. Further, the parameter frequencyDomainResources may be for the actual component carrier including the BWP and its subbands.

[0035] Furthermore, in this specification, a compact upper layer message such as an SB-List that can be used to configure a plurality of subbands at once, for example, an RRC IE, is proposed. The message SB-List may be composed of a plurality of blocks of the above SB IE, each of which configures a single subband.

[0036] See Appendix Information Element Example 1, an example of the SB-List information element.

[0037] (Subband configuration depending on LBT) In this specification, in this solution, an upper layer message is used to have a potential BWP ​​​​​​​​​​​​It is proposed to configure the UE using a list of sub-band configurations. Then, based on the LBT result , one configuration is selected. The proposed message can carry information regarding frequency domain resources, sub-carrier spacing, cyclic prefix, etc. for each configuration. For example, Table 3 shows how various configuration indexes are sub-bands. Configuration index 0 indicates the same frequency domain resource as the frequency domain resource occupied by SB0 in FIG. 3, and configuration index 5 of the configuration indicates the same frequency domain resource as the frequency domain resources occupied by SB0 and SB3 in the same figure.

[0038] To achieve this purpose, for example, a higher layer message can be a BWP_SB_Configs, such as Information Element 3 in the appendix, which can be called, for example, an RRC IE. The parameter SB-Config-Id represents the configuration index as in Table 3, and other parameters are defined in the same way as in the case of the above SB IE.

[0039] Refer to the BWP_SB_Config information element in Information Element Example 3 of the appendix.

[0040] (SB semi-static configuration) (Sub-band configuration independent of LBT) As another embodiment, the UE can be configured by a higher layer, such as an RRC message including a plurality of SB configurations for each BWP, such as SB-ConfigLists. For example, SB-ConfigLis ts can carry a plurality of SB-List-Ids. Next, by expanding a Media Access Control Element (MAC-CE) message and selecting an appropriate index within the SB-ConfigLists, a specific configuration can be semi-statically activated. For example, FIG. 5 shows that the UE has a MAC-C Indicates receiving the upper layer configuration of the SB activated by E. Next, the UE receives another activation MAC-CE that changes the SB from an equal bandwidth to an unequal bandwidth SB. After that, another MAC-CE selects a different SB configuration and divides the BWP into 3 SBs instead of 4 SBs. Therefore, using the MAC-CE, SBs can be semi-statically added or removed for the initially configured SB. Furthermore, the UE can be configured with a default SB configuration. It can be the SB configuration with the lowest index in the SB-ConfigLists or individually configured by upper layer signaling. The UE can use the default SB configuration as a fallback state when there is no activation MAC-CE or after the expiration of the SB inactivity timer configured by upper layer parameters such as the SB-InactivityTimer. The SB inactivity timer is reset when an activation MAC-CE or other signal or channel is received and can be decremented when no signal or channel is received. When the SB inactivity timer expires, the UE can assume that the gNB has switched to the default SB configuration. For example, in Figure 6, when the UE receives an activation MAC-CE, it sets the SB inactivity timer. Then, the UE receives other signals / channels or other MAC-CEs, and then the UE resets the SB inactivity timer. If no signal / channel is received for a sufficiently long period until the SB inactivity timer expires, the UE can fallback to the default SB configuration.

[0041] ​​​​​​​​​​​​​​(Sub-band configuration depending on LBT) In the solutions of this category, upper layer parameters such as the above BWP_SB_Configs information element can provide the UE with a very large number of configurations. Therefore, in this specification, for example, in order to select a subset of these configurations that can be identified by the ID of the parameter SB-Config-Id it is proposed to deploy MAC-CE. (Signaling of sub-band configuration in NR-U) In this section, several procedures for signaling sub-band configuration are proposed, regardless of whether these configurations belong to the solutions for sub-band configurations that do not depend on LBT or for sub-band configurations that depend on LBT. (Broadcast sub-band configuration) The SB configuration via RRC or RRC+MAC-CE can be signaled on the Physical Downlink Shared Channel (PDSCH) carrying the Remaining Minimum System Information (RMSI) scheduled by the SI-RNTI-scrambled Cyclic Redundancy Checksum (CRC) of the DCI format type 0-PDCCH common search space. Also, the SB configuration can be signaled on the PDSCH carrying the Other System Information (OSI) scheduled by the type 0A-PDCCH common search space with a DCI format using a CRC scrambled by the SI-RNTI.

[0042] (Unicast Sub - Band Configuration) Alternatively, the SB configuration can be scheduled by PDCCH in a UE - specific search space for a UE having DCI Format 1_0 or DCI Format 1_1 scrambled by a Cell Radio Network Temporary Identifier (C_RNTI). The PDSCH carrying either RRC or RRC + MAC - CE can send signals. In the case of the SB configuration via RRC + MAC - CE, the RRC message can be scheduled by DCI in the common search space, and the MAC - CE can be scheduled using DCI in the UE - specific search space (dedicated UE message). In the case of the SB configuration via RRC + MAC - CE, the RRC message can be scheduled by DCI in the common search space, and the MAC - CE can be scheduled using DCI in the UE - specific search space (dedicated UE message). The PDSCH carrying either RRC or RRC + MAC - CE can send signals. In the case of the SB configuration via RRC + MAC - CE, the RRC message can be scheduled by DCI in the common search space, and the MAC - CE can be scheduled using DCI in the UE - specific search space (dedicated UE message). To increase the possibility of acquiring channels, the search space can be composed of several Control Resource Sets (CORESETs) with different bandwidths as shown in FIG. 7. A narrow - bandwidth CORESET is more suitable for UEs with low capabilities, and a wide - bandwidth CORESET is more suitable for PDCCHs with a high aggregation level. The PDSCH carrying RRC or RRC + MAC - CE can be assigned to the same SB that the CORESET spans. If the CORESET spans multiple SBs, the related PDSCH carrying the RRC or RRC + MAC configuration may also span multiple SBs, for example, as shown in FIG. 7. To increase the possibility of acquiring channels, the search space can be composed of several Control Resource Sets (CORESETs) with different bandwidths as shown in FIG. 7. A narrow - bandwidth CORESET is more suitable for UEs with low capabilities, and a wide - bandwidth CORESET is more suitable for PDCCHs with a high aggregation level. The PDSCH carrying RRC or RRC + MAC - CE can be assigned to the same SB that the CORESET spans. If the CORESET spans multiple SBs, the related PDSCH carrying the RRC or RRC + MAC configuration may also span multiple SBs, for example, as shown in FIG. 7. To increase the possibility of acquiring channels, the search space can be composed of several Control Resource Sets (CORESETs) with different bandwidths as shown in FIG. 7. A narrow - bandwidth CORESET is more suitable for UEs with low capabilities, and a wide - bandwidth CORESET is more suitable for PDCCHs with a high aggregation level. The PDSCH carrying RRC or RRC + MAC - CE can be assigned to the same SB that the CORESET spans. If the CORESET spans multiple SBs, the related PDSCH carrying the RRC or RRC + MAC configuration may also span multiple SBs, for example, as shown in FIG. 7.

[0043] To increase the possibility of acquiring channels, the search space can be composed of several Control Resource Sets (CORESETs) with different bandwidths as shown in FIG. 7. A narrow - bandwidth CORESET is more suitable for UEs with low capabilities, and a wide - bandwidth CORESET is more suitable for PDCCHs with a high aggregation level. The PDSCH carrying RRC or RRC + MAC - CE can be assigned to the same SB that the CORESET spans. If the CORESET spans multiple SBs, the related PDSCH carrying the RRC or RRC + MAC configuration may also span multiple SBs, for example, as shown in FIG. 7. To increase the possibility of acquiring channels, the search space can be composed of several Control Resource Sets (CORESETs) with different bandwidths as shown in FIG. 7. A narrow - bandwidth CORESET is more suitable for UEs with low capabilities, and a wide - bandwidth CORESET is more suitable for PDCCHs with a high aggregation level. The PDSCH carrying RRC or RRC + MAC - CE can be assigned to the same SB that the CORESET spans. If the CORESET spans multiple SBs, the related PDSCH carrying the RRC or RRC + MAC configuration may also span multiple SBs, for example, as shown in FIG. 7. To increase the possibility of acquiring channels, the search space can be composed of several Control Resource Sets (CORESETs) with different bandwidths as shown in FIG. 7. A narrow - bandwidth CORESET is more suitable for UEs with low capabilities, and a wide - bandwidth CORESET is more suitable for PDCCHs with a high aggregation level. The PDSCH carrying RRC or RRC + MAC - CE can be assigned to the same SB that the CORESET spans. If the CORESET spans multiple SBs, the related PDSCH carrying the RRC or RRC + MAC configuration may also span multiple SBs, for example, as shown in FIG. 7. To increase the possibility of acquiring channels, the search space can be composed of several Control Resource Sets (CORESETs) with different bandwidths as shown in FIG. 7. A narrow - bandwidth CORESET is more suitable for UEs with low capabilities, and a wide - bandwidth CORESET is more suitable for PDCCHs with a high aggregation level. The PDSCH carrying RRC or RRC + MAC - CE can be assigned to the same SB that the CORESET spans. If the CORESET spans multiple SBs, the related PDSCH carrying the RRC or RRC + MAC configuration may also span multiple SBs, for example, as shown in FIG. 7. To increase the possibility of acquiring channels, the search space can be composed of several Control Resource Sets (CORESETs) with different bandwidths as shown in FIG. 7. A narrow - bandwidth CORESET is more suitable for UEs with low capabilities, and a wide - bandwidth CORESET is more suitable for PDCCHs with a high aggregation level. The PDSCH carrying RRC or RRC + MAC - CE can be assigned to the same SB that the CORESET spans. If the CORESET spans multiple SBs, the related PDSCH carrying the RRC or RRC + MAC configuration may also span multiple SBs, for example, as shown in FIG. 7. To increase the possibility of acquiring channels, the search space can be composed of several Control Resource Sets (CORESETs) with different bandwidths as shown in FIG. 7. A narrow - bandwidth CORESET is more suitable for UEs with low capabilities, and a wide - bandwidth CORESET is more suitable for PDCCHs with a high aggregation level. The PDSCH carrying RRC or RRC + MAC - CE can be assigned to the same SB that the CORESET spans. If the CORESET spans multiple SBs, the related PDSCH carrying the RRC or RRC + MAC configuration may also span multiple SBs, for example, as shown in FIG. 7. To increase the possibility of acquiring channels, the search space can be composed of several Control Resource Sets (CORESETs) with different bandwidths as shown in FIG. 7. A narrow - bandwidth CORESET is more suitable for UEs with low capabilities, and a wide - bandwidth CORESET is more suitable for PDCCHs with a high aggregation level. The PDSCH carrying RRC or RRC + MAC - CE can be assigned to the same SB that the CORESET spans. If the CORESET spans multiple SBs, the related PDSCH carrying the RRC or RRC + MAC configuration may also span multiple SBs, for example, as shown in FIG. 7. To increase the possibility of acquiring channels, the search space can be composed of several Control Resource Sets (CORESETs) with different bandwidths as shown in FIG. 7. A narrow - bandwidth CORESET is more suitable for UEs with low capabilities, and a wide - bandwidth CORESET is more suitable for PDCCHs with a high aggregation level. The PDSCH carrying RRC or RRC + MAC - CE can be assigned to the same SB that the CORESET spans. If the CORESET spans multiple SBs, the related PDSCH carrying the RRC or RRC + MAC configuration may also span multiple SBs, for example, as shown in FIG. 7.

[0044] To further increase the flexibility of channel access and reduce the uncertainty due to LBT, the gNB can configure a set of SBs for a specific UE, even when the CORESET spans one or more sub - bands that may or may not belong to this set. To further increase the flexibility of channel access and reduce the uncertainty due to LBT, the gNB can configure a set of SBs for a specific UE, even when the CORESET spans one or more sub - bands that may or may not belong to this set. To further increase the flexibility of channel access and reduce the uncertainty due to LBT, the gNB can configure a set of SBs for a specific UE, even when the CORESET spans one or more sub - bands that may or may not belong to this set. To further increase the flexibility of channel access and reduce the uncertainty due to LBT, the gNB can configure a set of SBs for a specific UE, even when the CORESET spans one or more sub - bands that may or may not belong to this set.

[0045] (Indication of LBT result) (Sub-band configuration independent of LBT) In NR-U, listen-before-talk (LBT) is performed before accessing a channel As a result, some of the configured sub-bands may not be available, and the gNB may not be able to obtain the SBs configured first. It is beneficial to dynamically indicate which of the initially configured sub-bands are the sub-bands.

[0046] In this specification, it is proposed to use DCI to indicate the SBs successfully acquired by the gNB. To achieve this purpose, any of the following alternatives can be adopted. · UE-specific indication: The DCI can be transmitted within a UE-specific search space using a UE-specific RNTI such as a cell radio network temporary identifier (C-RNTI) with a bitmap field called, for example, the SB-bitmap field. The size of the SB-bitmap is equal to the number of configured SBs, and the most significant bit corresponds to the highest SB index. For example, the UE can expect that the SB is available if the corresponding one is set to 1. This DCI can be configured on each configured sub-band. For example, FIG. 8 shows that the UE is configured using three sub-bands SB1, SB2, and SB3. Further, the UE configures a UE-specific search space for each SB, monitors the DCI using a CRC scrambled by the C_RNTI, and decodes the SB-bitmap field. To enhance the robustness of the DCI, the gNB can transmit the DCI over different SBs at different time instances. At the first transmission opportunity, the SB ​​​​​​​​​​​- The -bitmap is equal to 101, and in the second transmission opportunity, the SB-bitmap is equal to 110. Furthermore, to avoid variable DCI sizes, the size of the SB-bitmap can be set to a fixed value such as the maximum number of sub-bands per BWP, and the bits are mapped according to a specific rule to the pinged sub-bands. For example, the most significant bit can correspond to the sub-band with the highest index, and each of the subsequent less significant bits corresponds to the subsequent sub-band with the next lower index. The remaining bits not mapped to sub-band indices are set to zero. · Indication of groupcast / broadcast UEs: If the same sub-band is configured for multiple UEs, the gNB can indicate the available sub-bands to all UEs sharing the same configuration. To achieve this, a sub-band indication wireless network temporary identifier (SBI-RNTI) can be introduced to scramble the CRC of the DCI transmitted within the common search space. This DCI carries an SB-bitmap field indicating the SBs available for transmission.

[0047] For either UE-specific or group / broadcast indication, the DCI can be transmitted at a period configured to indicate any change in the available sub-bands. The DCIs transmitted across different sub-bands can be time-shifted from one sub-band to another. For example, as shown in Figure 8, the DCI on the sub-band with the highest index comes first, followed by the DCIs on sub-bands with lower indices. To reduce power consumption on the UE side, if the UE has one DCI in a specific sub-band If the decoding of the CI is successful, the UE can ignore the DCI transmitted from other sub-bands until the next monitoring opportunity. The DCI transmission can be restricted to a specific time position, for example, at the beginning of a slot. Even if there is no change in the availability of the configured sub-bands, the DCI can be transmitted periodically. Some sub-bands can be configured as default sub-bands that always carry DCI indicating which sub-bands are available, such as an SB-bitmap. For example, the sub-band with the smallest index can be the default sub-band. Also, in this specification, upper layer parameters such as Default_SB, RRC message can be proposed to indicate the default sub-band.

[0048]

[0049] (Sub-band configuration depending on LBT) In the solutions of this category, this specification proposes to transmit DCI indicating a sub-band configuration index, for example, one of the indexes in Table 3, from those configured by any upper layer parameter of RRC or RRC+MAC-CE. In other words, this specification proposes an RRC+DCI procedure where the RRC message provides multiple sub-band configurations and the DCI selects one of them. Another procedure is RRC+MAC-CE+DCI. In that procedure, the RRC provides multiple sub-band configurations, then the MAC-CE provides a subset from these configurations, and subsequently the DCI selects one configuration based on the LBT result. The DCI can have a bitmap indicating which configuration is selected, and its size can be fixed, for example, equal to the maximum number of sub-band configurations. ​​​​​​​​​​​​​​​It is possible.

[0050] To achieve this purpose, the gNB can configure multiple CORESETs that the gNB can use to transmit activation DCI. These CORESETs may be included in a single SB or, as shown in FIG. 9, may span multiple sub-bands. In the example of FIG. 9, the activation DCI can be transmitted in the UE-specific search space using its CRC scrambled by the C-RNTI. Alternatively, the DCI can be transmitted in the common search space or via a group-common PDCCH with a temporarily identified SB_act radio network temporary identifier (SB_act-RNTI).

[0051]

[0052] Furthermore, the gNB can implicitly indicate that some sub-bands are not used, and thus the UE can avoid monitoring them. This can be achieved by not configuring to discard any CORESET within those sub-bands.

[0053] Some sub-bands can be configured as default sub-bands that can always carry activation DCI. For example, the sub-band with the smallest index can be the default sub-band. Also, this specification proposes upper-layer parameters such as Default_SB and RRC messages that can be used to indicate the default sub-band.

[0054] In the carrier aggregation mode, for any solution category, the activation / indication DCI is the sub-band active in any specific instance. ​ It can be transmitted in the license cell to indicate

[0055] In addition to the two solution categories, as another embodiment that can be used, in this specification, gN When determining the subbands that gNB can obtain for downlink transmission, it is proposed that the UE can assist the gNB This can be very helpful in reducing the hidden node problem. In the case of time division duplexing (TDD), both DL transmission and UL transmission occupy the same frequency band Therefore, if there are some UL subbands that the UE cannot obtain due to LBT interference, the gNB may not obtain them even though they are available from the perspective of the gNB, and the UE monitors only the subbands that are available from the perspective of the UE There are several The UE can indicate the available subbands in several ways. For example, if a procedure such as a handshake is supported, the UE can explicitly indicate the preferred subbands in its response Furthermore, the UE can implicitly indicate the preferred DL subband by performing UL transmission in this band For example, the gNB can configure or schedule the UE using multiple UL resources spanning different subbands. Next, the UE can choose to perform transmission on the UL subband associated with the preferred DL subband These resources can be used for various purposes such as sounding reference signals (SRS), physical uplink shared channels (PUSCH), physical uplink control channels (PUCCH), and preambles of random access channels (RACH)

[0056] In frequency division duplexing (FDD), both DL and UL transmissions occupy different frequency bands ​​​​​​It has. In this case, the UE performs LBT on the DL sub-band and can indicate those sub-bands by UL transmission. If the channel for UL transmission is available, it can be used to indicate the index of the suitable DL sub-band. Also, if procedures such as handshaking are supported, it can be useful for conveying such information. Moreover, some association between the UL sub-band and the DL sub-band can be defined such that when the UE performs UL transmission on any specific UL sub-band, the gNB can determine which DL sub-band is suitable. (UE-assisted sub-band switching) Due to the hidden node problem, the BWP / sub-band selected by the gNB for DL transmission is not always available on the UE side for receiving this DL, and conversely, the BWP / sub-band selected by the UE for UL transmission may not be available on the gNB side for receiving this UL. Therefore, procedures are needed to avoid the selection of BWP / sub-bands that are not available for DL transmission on the UE side or BWP / sub-bands that are not available for UL transmission on the gNB side. To address this issue, this specification proposes to enable the UE to assist the gNB in selecting sub-bands / BWPs that do not face the hidden node problem.

[0057] (UE-assisted sub-band switching) Due to the hidden node problem, the BWP / sub-band selected by the gNB for DL transmission is not always available on the UE side for receiving this DL, and conversely, the BWP / sub-band selected by the UE for UL transmission may not be available on the gNB side for receiving this UL. Therefore, procedures are needed to avoid the selection of BWP / sub-bands that are not available for DL transmission on the UE side or BWP / sub-bands that are not available for UL transmission on the gNB side. To address this issue, this specification proposes to enable the UE to assist the gNB in selecting sub-bands / BWPs that do not face the hidden node problem. Figure 18 is a time and spectrum diagram of an example in TDD where the gNB and the UE can operate on sub-bands available on both the gNB side and the UE side. In the example of Figure 18, several

[0058] To address this issue, this specification proposes to enable the UE to assist the gNB in selecting sub-bands / BWPs that do not face the hidden node problem. Figure 18 is a time and spectrum diagram of an example in TDD where the gNB and the UE can operate on sub-bands available on both the gNB side and the UE side. In the example of Figure 18, several Although those DL sub-bands are available on the gNB side, the UE may not be able to receive on all of them. In particular, FIG. 18 shows that the DL sub-bands available on the gNB side are SB 0, SB1, and SB2, and the sub-bands available for UL on the UE side are SB0, S B2, and SB3. In the TDD operation mode, since the same frequency band is used for both DL and UL, in any successful transmission and reception, the selected sub-band needs to be available simultaneously from the perspectives of both the gNB and the UE.

[0059] In this example, although DL SB1 is available from the gNB side, since SB1 cannot be used for UL transmission, this sub-band may not be available for DL, which means the existence of hidden nodes around the UE that the gNB cannot detect. Similarly, although UL SB3 is available on the UE side, since SB3 cannot be used for DL transmission, SB3 may not be available for use because it cannot be used for UL, which means the existence of hidden nodes around the gNB that the UE cannot detect. Such UE assistance is useful not only for avoiding hidden nodes around the UE, but can also be used by the gNB to provide UL resources on the available sub-bands indicated by the UE to the UE.

[0060] If the DL BWP and the UL BWP consist of a different number of sub-bands or the same number of sub-bands with different bandwidths, the DL sub-band or the UL sub-band can be selected only if it overlaps with the available UL sub-band or DL sub-band respectively.

[0061] ​​​​This is the case. FIG. 19 shows single or multiple sub-bands available on both the gNB side and the UE side and the TDD in which the gNB and the UE can operate on the DL sub-bands and UL sub-bands corresponding to them is a time and spectrum diagram of an example in TDD. In the example of FIG. 19, DL SB1 is available on the g NB side, but overlaps with two UL sub-bands, and since one of them is not available on the UE side's SB1, it may not be usable. Similarly, UL SB 3 overlaps with DL SB3 that is not available on the gNB, so it may not be usable. Furthermore, in the case of TDD, the number of DL sub-bands and UL sub-bands may be different, and each D L sub-band may be associated with multiple UL sub-bands, or each UL sub-band may be associated with multiple DL sub-bands. Furthermore, since the bandwidths of the DL BWP and UL BWP may be different, the associated DL sub-bands and UL bands may not even overlap In this case, this specification proposes to explicitly indicate the DL sub-bands available on the UE side and to develop the procedures proposed for the case of FDD This can also be done In FDD operation, transmission and reception occur in different frequency bands. Therefore, whether a specific sub-band in DL or U

[0062] L is available or not does not necessarily mean whether the associated UL or DL sub-band is available or not. Therefore, in addition to the UL sub-bands available, the UE can explicitly indicate the DL sub-bands that are not affected by hidden nodes FIG. 20 shows an example of an FDD scenario using four DL and UL sub-bands In FDD, the DL sub-bands and UL sub-bands are in different frequency bands In FDD, the DL sub-bands and UL sub-bands are in different frequency bands In FDD, the DL sub-bands and UL sub-bands are in different frequency bands Occupy. The availability of the UL sub-band does not necessarily mean that there is no hidden node in the related DL sub-band. For example, it is necessary to explicitly indicate that it is available on the UE side. In contrast to the TDD case, even if UL SB1 cannot be used for UL transmission on the UE side, since UL SB1 and DL SB1 occupy different frequency bands, it does not necessarily mean that DL SB1 is affected by the hidden node problem. Furthermore, in the case of FDD, the number of DL sub-bands and UL sub-bands may not be equal. In this case, a single DL sub-band can be associated with multiple UL sub-bands, and a single UL sub-band can also be associated with multiple DL sub-bands. Therefore, this specification proposes that the UE should explicitly indicate the DL sub-bands available on the UE side.

[0063] (Procedure for UE-assisted sub-band / BWP switching) The MCOT period can be divided into two parts (not necessarily equal). The first part is called the assistance window and is mainly used, but not limited to, exchanging information about DL and UL sub-bands / BWPs available on the gNB and UE sides. Next, the gNB can use this information to adjust the DL sub-band / BWP and schedule UL transmission on the available UL sub-band / BWP. For example, the second part of the MCOT, called the DL / UL transmission window, can be used for actual DL and UL transmissions composed of data, signals, or control. The DL / UL transmission window can include one or more DL-UL switching points. Furthermore, the assistance window can be at the start of the MCOT or during the MCOT for sub-band / BWP switching ​​​​​ In the case of etching, etc., it may be repeated several times.

[0064] Figure 21 shows an example of a UE-assisted sub-band switching procedure in which a gNB detects a list of DL sub-bands that may be available at the gNB and provides it to the UE. The UE evaluates those DL sub-bands to detect hidden nodes. Next, the UE signals to the sub-bands available on the UE side. In FDD, this can be achieved by explicitly indicating the DL sub-bands that can be used for the UE to receive DL transmissions. In TDD, the UE can signal to the UL sub-bands available on the UE side, and the gNB can select the DL sub-bands that overlap with the UL sub-bands available on the UE side. The same procedure can be used for BWP switching. In TDD, the UE can signal to the UL sub-bands available on the UE side, and the gNB can select the DL sub-bands that overlap with the UL sub-bands available on the UE side. In TDD, the UE can signal to the UL sub-bands available on the UE side, and the gNB can select the DL sub-bands that overlap with the UL sub-bands available on the UE side. In TDD, the UE can signal to the UL sub-bands available on the UE side, and the gNB can select the DL sub-bands that overlap with the UL sub-bands available on the UE side. The same procedure can be used for BWP switching.

[0065] Figure 22A shows a high-level procedure of a UE-assisted sub-band switching procedure in which signaling occurs on the same unlicensed cell suitable for dual connection (DC) and stand-alone (SA) NR-U. Alternatively, in the carrier aggregation (CA) mode, as shown in Figure 22B, signaling can occur on the Pcell. There are four major steps. mode, as shown in Figure 22B, signaling can occur on the Pcell. There are four major steps.

[0066] The first is to signal to the available DL sub-bands. This signal can carry the DL sub-bands available on the gNB side associated with a successful LBT. The first is to signal to the available DL sub-bands. This signal can carry the DL sub-bands available on the gNB side associated with a successful LBT. The first is to signal to the available DL sub-bands. This signal can carry the DL sub-bands available on the gNB side associated with a successful LBT.

[0067] The second is to signal to the DL sub-bands without hidden nodes. This signal is Before transmission, the UE evaluates the channels on the DL sub-bands indicated in the previous signal to determine whether the UE can receive on those sub-bands. Similarly, since there may be hidden nodes that the g NB cannot detect, some of them may not be available. Then, the UE can indicate to the gNB the DL sub-bands available on the UE side.

[0068] The third is to signal the selected DL sub-band. This signal can be used to indicate which sub-band is selected and can be a pre-defined rule-based option that the gNB can use to select the DL to avoid any ambiguity between the UE and the gNB. It can be an option with pre-defined rules.

[0069] Fourth, the gNB can start DL transmission of either data, control, or signals. Further, the gNB may include one or more switch points within the MCOT.

[0070] A procedure similar to the above procedure can be adopted as a high-level procedure for the UE-assisted BWP switching procedure.

[0071] If the UE is configured to use multiple BWPs and only a single BWP is activated at any given time while the entire DL BWP is available, it is proposed herein that the UE can assist the gNB in determining the presence of hidden nodes on this DL BWP. In the case of TDD where a pair of DL BWP (i ) and UL BWP (i DL ) occupy the same frequency band, the gNB signals the availability of the i UL th DL BWP. DL Then, when the UE detects this DL BWP and there is no hidden node occupying this BWP, it transmits a signal indicating its availability. The indication from the UE can be transmitted on the i-th UL BWP paired with the i-th DL BWP in the Scell. Additionally, the UE can transmit this indication on other arbitrary UL BWPs (not paired with the i-th DL BWP) on the Scell or PCell that can be configured by the gNB. In the absence of such a configuration, several UL BWPs with predefined rules / orders can be used to determine a UL BWP, such as the initial or default UL BWP of the Scell or PCell. In the case of FDD where a pair of DL BWP i and UL BWP i occupy different frequency bands, even if the paired UL BWP is unavailable, the DL BWP can be used without hidden nodes. Therefore, in this specification, it is proposed that when the gNB indicates the availability of a specific DL BWP, the gNB can indicate a single or multiple UL BWPs that the UE can use to indicate whether there is a hidden node in the DL BWP. The UE can attempt to transmit the indication (when passing the LBT) on the UL BWP paired with the DL BWP or an additional UL BWP (e.g., the first UL BWP, or the default UL BWP in the Scell or PCell). Furthermore, the UE can select a UL BWP according to a specific rule / order. For example, the UE can use the UL BWP paired with DL BWP i In this case, it transmits a signal indicating its availability. The indication from the UE can be transmitted on the i-th UL BWP paired with the i-th DL BWP in the Scell. i DL th DL BWP in the Scell. UL It can be transmitted on the th UL BWP. Furthermore, the UE can transmit this indication on other arbitrary UL BWPs (not paired with the i-th DL BWP) on the Scell or P cell configured by the gNB. DL In the absence of such a configuration, several UL BWPs with predefined rules / orders can be used to determine a UL BWP, such as the initial or default UL BWP of the Scell or PCell. A pair of DL BWP i and UL BWP i occupy different frequency bands in FDD. i DL and UL BWP i UL occupy different frequency bands in FDD. Even if the paired UL BWP is unavailable, the DL BWP can be used without hidden nodes. Therefore, in this specification, it is proposed that when the gNB indicates the availability of a specific DL BWP, the g NB can indicate a single or multiple UL BWPs that the UE can use to indicate whether there is a hidden node in the DL BWP. The UE can attempt to transmit the indication (when passing the LBT) on the UL BWP paired with the DL BWP or an additional UL BWP (e.g., the first UL BWP, or the default UL BWP in the Scell or Pcel l). Furthermore, the UE can select a UL BWP according to a specific rule / order. For example, the UE can use the UL BWP paired with DL BWP i and UL BWP i DL paired with DL BWP i ULThe use can be attempted, and then, for example, if available on the default UL BWP, and subsequently, on the first UL BWP, the indication transmission can be attempted.

[0072] If the UE is configured to use multiple DL BWPs and multiple of those DL BWPs are activated at once, if each of the activated DL BWPs forms a one-to-one pair with a single UL BWP, the above procedure can be adopted. If the pairing between DL and UL BWPs is close to a many-to-one relationship, i.e., when multiple activated DL BWPs form a pair with a single UL BWP, the above procedure can still be adopted, but the UE can indicate additional information that the DL BWP has no hidden nodes. For example, the UE can provide the DL BWP ID.

[0073] In the next section, several possible alternatives for the above signals

[0074] (Signaling of Available DL Subbands / BWPs) If the available DL subbands change dynamically for each MCOT, dynamic PHY indication can be adopted. If the available subbands remain available for a long time in a semi-static or static channel, higher layer

[0075] (Channel Acquisition Request) In this specification, it is proposed that the gNB can send a Channel Acquisition Request (CAR) to indicate which subbands in the gNB. For example, as shown in Figure 23, the CAR signal, to keep the CAR small, To indicate that the subbands carrying the signal are available at the gNB, each available DL subband can be transmitted on.

[0076] Alternatively, the CAR signal can be transmitted only on one subband available at the gNB, which has, for example, a bitmap field named Avai_SBs, and each bit represents the availability of one subband. The most significant bit can correspond to the subband with the highest ID, and the subsequent lower bits correspond to the next subband IDs. The size of Avai_SBs can be the same as the maximum number of DL subbands per DL BWP. In another embodiment, the CAR signal can be transmitted on the Pcell for the CA mode. In this case, this specification proposes an additional parameter or field indicating the Scell ID, which can be called, for example, ScellID and includes the DL subband. When the UE is configured using multiple unlicensed Scells, such a parameter enables the gNB to indicate to which Scell the available DL subbands belong. The size of the parameter or field ScellID can be log2 (the maximum number of Scells configurable for the UE).

[0077] The CAR signal can be carried in a UE-specific search space scrambled by the C-RNTI, or in a common search space with a DCI format scrambled by a pre-defined RNTI, such as, for example, the CAR-RNTI. Since the gNB may simultaneously broadcast the subbands available to multiple UEs, the common

[0078] search space is used. It is beneficial to use the search space. The CORESET carrying the PDCCH can be configured within each sub-band or can be configured to span multiple sub-bands. Further , the DCI can provide the UE with UL authorization for transmitting feedback from the UE . Various UEs can derive UL authorization based on predefined rules. For example , the UE can apply specific time and frequency shifts with respect to the received DCI and the function of the UE ID to reduce the possibility of collisions. Further, if the UE is configured to use multiple grant-free (authorization-free) UL resources, the UE can derive which grant-free UL resource ID can be used by the UE to transmit feedback .

[0079] To reduce the overhead of signaling to the DL sub-bands / BWPs available at the gNB and collecting the evaluation of the presence of hidden nodes of various UEs, in this specification, it is proposed that the gNB can group UEs based on the source signal used to indicate the spatial quasi-collocation (QCL) of signals / channels indicating the DL sub-bands / BWPs available at the gNB . When UEs belong to the same group, those UEs are on the same beam and, if there are hidden nodes, are affected by the same hidden node. In this case, the gNB can determine the DL sub-band / BWP to be used by obtaining feedback from only one UE. Other methods of grouping UEs can also be adopted. To achieve this purpose, in this specification, it is proposed that the signal / channel indicating the available DL is UE-specific , for example, transmitted in a UE-specific search space. P.

[0080] If the UE is configured with multiple BWPs and the entire DL BWP is available, If only a single BWP is activated at any given time, the CAR signal is used herein. The signal is transmitted on an activated BWP on the Scell ​​for DC and SA NR-U. Alternatively, the CAR signal may convey the identity of the activated BWP. This can be useful in the case of CA. One possibility is The gNB must then transmit a bitmap indicating which DL BWPs are available at the gNB. The size of the bitmap can be equal to the number of configured BWPs. If there is only one active DL BWP, the UE shall not expect multiple bits to be set to 1. Don't expect anything.

[0081] If the UE is configured with multiple DL BWPs and more than one of the DL BWPs When activated at once, the CAR signal indicates the DL BWP available at the gNB. A bitmap may be used to transmit on one BWP. In this case, the UE may It can be expected that the UE will set the CAR bit to 1. The BWP carrying the CAR signal is It may be one of the DL BWPs that needs to check the existence of a node. WP, e.g., the initial or default BWP in the Pcell. The AR signal may be transmitted on each DL BWP that the gNB wishes to acquire.

[0082] (Implicit indication of available DL sub-bands) Also, it is understood herein that gNBs require low-complexity correlators for detection, e.g. It is proposed that by transmitting a signal with low decoding complexity, the DL sub-bands available at the gNB can be implicitly indicated. Such signals can be, for example, the Primary Synchronization Signal (PSS), the Secondary Synchronization Signal (SSS), the preamble, etc., and the UE can use it to infer the availability of the sub-band carrying this signal, which is called a sequence-based signal. Instead of transmitting signals with low decoding complexity on each available sub-band, it is possible to indicate a bitmap for the DL sub-bands available at the gNB by a sequence-based signal. For example, the initial value of the sequence-based signal can be mapped to a specific code point in the bitmap. When the UE is configured to use multiple BWPs and only one or multiple BWPs are activated at any given time while the entire DL BWP is available, it is also proposed in this specification that a sequence-based signal can be used to indicate the DL BWP that the gNB is trying to acquire. The sequence-based signal can be similar to the sequence-based signal used to indicate the available DL sub-bands.

[0083]

[0084]

[0085] (Signaling for DL Sub-bands / BWPs without Hidden Nodes) In this section, several procedures are proposed that enable the UE to indicate a suitable DL sub-band / BWP that is not affected by hidden nodes, for example, the DL sub-bands available on the UE side. In the case of TDD, the UE can indicate the UL sub-bands / BWPs available on the UE side. Next, the gNB can estimate a DL sub-band / BWP without hidden nodes. In the case of FDD, the UE can explicitly indicate the DL sub-bands / BWPs available on the UE side. In one embodiment, in this specification, not only can the gNB signal the DL sub-bands / BWPs available on the gNB side, but this signal can also provide UL resources that can be used for the UE to send an indication to a DL sub-band / BWP without hidden nodes, for example, a DL sub-band / BWP available on the UE side. For example, when the gNB uses DCI to indicate the DL sub-bands / BWPs available at the gNB, the gNB can use this DCI to provide UL resources for PUCCH or PUSCH, as shown in FIG. 24, for example. When the available DL sub-band / BWP is indicated by a signal that cannot provide UL resources, such as a sequence-based signal, the UE can transmit using a configured grant. Also, when the gNB uses DCI to indicate the DL sub-bands / BWPs available at the gNB, it can activate a configured grant that provides multiple UL opportunities that the UE can use to handle the unavailability of the UL channel. Further, in this specification, it is proposed that the configured grant can be activated after a pre-defined period has elapsed (without activating the DCI) after receiving an indication of the DL sub-band / BWP available at the gNB.

[0086] In one embodiment, in this specification, not only can the gNB signal the DL sub-bands / BWPs available on the gNB side, but this signal can also provide UL resources that can be used for the UE to send an indication to a DL sub-band / BWP without hidden nodes, for example, a DL sub-band / BWP available on the UE side. BWP, but this signal can also provide UL resources that can be used for the UE to send an indication to a DL sub-band / BWP without hidden nodes, for example, a DL sub-band / BWP available on the UE side. For example, when the gNB uses DCI to indicate the DL sub-bands / BWPs available at the gNB, the gNB can use this DCI to provide UL resources for PUCCH or PUSCH, as shown in FIG. 24, for example. When the available DL sub-band / BWP is indicated by a signal that cannot provide UL resources, such as a sequence-based signal, the UE can transmit using a configured grant. Also, when the gNB uses DCI to indicate the DL sub-bands / BWPs available at the gNB, it can activate a configured grant that provides multiple UL opportunities that the UE can use to handle the unavailability of the UL channel. Further, in this specification, it is proposed that the configured grant can be activated after a pre-defined period has elapsed (without activating the DCI) after receiving an indication of the DL sub-band / BWP available at the gNB. For example, when the gNB uses DCI to indicate the DL sub-bands / BWPs available at the gNB, the gNB can use this DCI to provide UL resources for PUCCH or PUSCH, as shown in FIG. 24, for example. When the available DL sub-band / BWP is indicated by a signal that cannot provide UL resources, such as a sequence-based signal, the UE can transmit using a configured grant. Also, when the gNB uses DCI to indicate the DL sub-bands / BWPs available at the gNB, it can activate a configured grant that provides multiple UL opportunities that the UE can use to handle the unavailability of the UL channel. Further, in this specification, it is proposed that the configured grant can be activated after a pre-defined period has elapsed (without activating the DCI) after receiving an indication of the DL sub-band / BWP available at the gNB. For example, when the gNB uses DCI to indicate the DL sub-bands / BWPs available at the gNB, the gNB can use this DCI to provide UL resources for PUCCH or PUSCH, as shown in FIG. 24, for example. When the available DL sub-band / BWP is indicated by a signal that cannot provide UL resources, such as a sequence-based signal, the UE can transmit using a configured grant. Also, when the gNB uses DCI to indicate the DL sub-bands / BWPs available at the gNB, it can activate a configured grant that provides multiple UL opportunities that the UE can use to handle the unavailability of the UL channel. Further, in this specification, it is proposed that the configured grant can be activated after a pre-defined period has elapsed (without activating the DCI) after receiving an indication of the DL sub-band / BWP available at the gNB. When the available DL sub-band / BWP is indicated by a signal that cannot provide UL resources, such as a sequence-based signal, the UE can transmit using a configured grant. Also, when the gNB uses DCI to indicate the DL sub-bands / BWPs available at the gNB, it can activate a configured grant that provides multiple UL opportunities that the UE can use to handle the unavailability of the UL channel. Further, in this specification, it is proposed that the configured grant can be activated after a pre-defined period has elapsed (without activating the DCI) after receiving an indication of the DL sub-band / BWP available at the gNB. When the available DL sub-band / BWP is indicated by a signal that cannot provide UL resources, such as a sequence-based signal, the UE can transmit using a configured grant. Also, when the gNB uses DCI to indicate the DL sub-bands / BWPs available at the gNB, it can activate a configured grant that provides multiple UL opportunities that the UE can use to handle the unavailability of the UL channel. Further, in this specification, it is proposed that the configured grant can be activated after a pre-defined period has elapsed (without activating the DCI) after receiving an indication of the DL sub-band / BWP available at the gNB. When the available DL sub-band / BWP is indicated by a signal that cannot provide UL resources, such as a sequence-based signal, the UE can transmit using a configured grant. Also, when the gNB uses DCI to indicate the DL sub-bands / BWPs available at the gNB, it can activate a configured grant that provides multiple UL opportunities that the UE can use to handle the unavailability of the UL channel. Further, in this specification, it is proposed that the configured grant can be activated after a pre-defined period has elapsed (without activating the DCI) after receiving an indication of the DL sub-band / BWP available at the gNB. When the available DL sub-band / BWP is indicated by a signal that cannot provide UL resources, such as a sequence-based signal, the UE can transmit using a configured grant. Also, when the gNB uses DCI to indicate the DL sub-bands / BWPs available at the gNB, it can activate a configured grant that provides multiple UL opportunities that the UE can use to handle the unavailability of the UL channel. Further, in this specification, it is proposed that the configured grant can be activated after a pre-defined period has elapsed (without activating the DCI) after receiving an indication of the DL sub-band / BWP available at the gNB. When the available DL sub-band / BWP is indicated by a signal that cannot provide UL resources, such as a sequence-based signal, the UE can transmit using a configured grant. Also, when the gNB uses DCI to indicate the DL sub-bands / BWPs available at the gNB, it can activate a configured grant that provides multiple UL opportunities that the UE can use to handle the unavailability of the UL channel. Further, in this specification, it is proposed that the configured grant can be activated after a pre-defined period has elapsed (without activating the DCI) after receiving an indication of the DL sub-band / BWP available at the gNB. When the available DL sub-band / BWP is indicated by a signal that cannot provide UL resources, such as a sequence-based signal, the UE can transmit using a configured grant. Also, when the gNB uses DCI to indicate the DL sub-bands / BWPs available at the gNB, it can activate a configured grant that provides multiple UL opportunities that the UE can use to handle the unavailability of the UL channel. Further, in this specification, it is proposed that the configured grant can be activated after a pre-defined period has elapsed (without activating the DCI) after receiving an indication of the DL sub-band / BWP available at the gNB. When the available DL sub-band / BWP is indicated by a signal that cannot provide UL resources, such as a sequence-based signal, the UE can transmit using a configured grant. Also, when the gNB uses DCI to indicate the DL sub-bands / BWPs available at the gNB, it can activate a configured grant that provides multiple UL opportunities that the UE can use to handle the unavailability of the UL channel. Further, in this specification, it is proposed that the configured grant can be activated after a pre-defined period has elapsed (without activating the DCI) after receiving an indication of the DL sub-band / BWP available at the gNB. When the available DL sub-band / BWP is indicated by a signal that cannot provide UL resources, such as a sequence-based signal, the UE can transmit using a configured grant. Also, when the gNB uses DCI to indicate the DL sub-bands / BWPs available at the gNB, it can activate a configured grant that provides multiple UL opportunities that the UE can use to handle the unavailability of the UL channel. Further, in this specification, it is proposed that the configured grant can be activated after a pre-defined period has elapsed (without activating the DCI) after receiving an indication of the DL sub-band / BWP available at the gNB. When the available DL sub-band / BWP is indicated by a signal that cannot provide UL resources, such as a sequence-based signal, the UE can transmit using a configured grant. Also, when the gNB uses DCI to indicate the DL sub-bands / BWPs available at the gNB, it can activate a configured grant that provides multiple UL opportunities that the UE can use to handle the unavailability of the UL channel. Further, in this specification, it is proposed that the configured grant can be activated after a pre-defined period has elapsed (without activating the DCI) after receiving an indication of the DL sub-band / BWP available at the gNB.

[0087] The UE can send an indication of an available DL sub-band / BWP without hidden nodes on either PUCCH or PUSCH. A DL sub - band / BWP, e.g., a bitmap indicating the DL sub - bands / BWPs available at the UE side, can be transmitted. The most significant bit may correspond to the sub - band / BWP with the highest ID, and the subsequent lower - order bits may each correspond to the next sub - band ID. The size of the bitmap can be the same as the maximum number of DL sub - bands per DL BWP or the maximum number of DL BWPs per component carrier (CC). Further, when using separate PUCCH or PUSCH to indicate the availability of each DL sub - band / BWP, one bit may be sufficient to indicate whether the DL sub - band has a hidden node, e.g., whether the DL sub - band / BWP is unavailable at the UE side. If the PUCCH / PUSCH is scheduled or configured on the Pcell and those PUCCH / PUSCH resources are associated with a DL sub - band / BWP having a hidden node, e.g., a DL sub - band / BWP that is unavailable at the UE side, the UE can for power - saving purposes, abandon the transmission of the hidden - node indication. Alternatively, if the gNB uses DCI to indicate the DL sub - bands / BWPs available at the gNB, it may also initiate a PRACH transmission, e.g., a PDCCH order. Different sub - bands / BWPs may be associated with different time - frequency resources or different preambles, i.e., different PRACH resources. To achieve this purpose, this specification may include time and frequency resources and preambles for RACH transmission. The size of the bitmap can be the same as the maximum number of DL sub - bands per DL BWP or the maximum number of DL BWPs per component carrier (CC). Further, when using separate PUCCH or PUSCH to indicate the availability of each DL sub - band / BWP, one bit may be sufficient to indicate whether the DL sub - band has a hidden node, e.g., whether the DL sub - band / BWP is unavailable at the UE side. If the PUCCH / PUSCH is scheduled or configured on the Pcell and those PUCCH / PUSCH resources are associated with a DL sub - band / BWP having a hidden node, e.g., a DL sub - band / BWP that is unavailable at the UE side, the UE can for power - saving purposes, abandon the transmission of the hidden - node indication. Alternatively, if the gNB uses DCI to indicate the DL sub - bands / BWPs available at the gNB, it may also initiate a PRACH transmission, e.g., a PDCCH order. Different sub - bands / BWPs may be associated with different time - frequency resources or different preambles, i.e., different PRACH resources. To achieve this purpose, this specification may include time and frequency resources and preambles for RACH transmission. The size of the bitmap can be the same as the maximum number of DL sub - bands per DL BWP or the maximum number of DL BWPs per component carrier (CC). Further, when using separate PUCCH or PUSCH to indicate the availability of each DL sub - band / BWP, one bit may be sufficient to indicate whether the DL sub - band has a hidden node, e.g., whether the DL sub - band / BWP is unavailable at the UE side.

[0088] If the PUCCH / PUSCH is scheduled or configured on the Pcell and those PUCCH / PUSCH resources are associated with a DL sub - band / BWP having a hidden node, e.g., a DL sub - band / BWP that is unavailable at the UE side, the UE can for power - saving purposes, abandon the transmission of the hidden - node indication. Alternatively, if the gNB uses DCI to indicate the DL sub - bands / BWPs available at the gNB, it may also initiate a PRACH transmission, e.g., a PDCCH order. Different sub - bands / BWPs may be associated with different time - frequency resources or different preambles, i.e., different PRACH resources. To achieve this purpose, this specification may include time and frequency resources and preambles for RACH transmission. The size of the bitmap can be the same as the maximum number of DL sub - bands per DL BWP or the maximum number of DL BWPs per component carrier (CC). Further, when using separate PUCCH or PUSCH to indicate the availability of each DL sub - band / BWP, one bit may be sufficient to indicate whether the DL sub - band has a hidden node, e.g., whether the DL sub - band / BWP is unavailable at the UE side.

[0089] If the PUCCH / PUSCH is scheduled or configured on the Pcell and those PUCCH / PUSCH resources are associated with a DL sub - band / BWP having a hidden node, e.g., a DL sub - band / BWP that is unavailable at the UE side, the UE can for power - saving purposes, abandon the transmission of the hidden - node indication. Alternatively, if the gNB uses DCI to indicate the DL sub - bands / BWPs available at the gNB, it may also initiate a PRACH transmission, e.g., a PDCCH order. Different sub - bands / BWPs may be associated with different time - frequency resources or different preambles, i.e., different PRACH resources. To achieve this purpose, this specification may include time and frequency resources and preambles for RACH transmission. The size of the bitmap can be the same as the maximum number of DL sub - bands per DL BWP or the maximum number of DL BWPs per component carrier (CC). Further, when using separate PUCCH or PUSCH to indicate the availability of each DL sub - band / BWP, one bit may be sufficient to indicate whether the DL sub - band has a hidden node, e.g., whether the DL sub - band / BWP is unavailable at the UE side. If the PUCCH / PUSCH is scheduled or configured on the Pcell and those PUCCH / PUSCH resources are associated with a DL sub - band / BWP having a hidden node, e.g., a DL sub - band / BWP that is unavailable at the UE side, the UE can for power - saving purposes, abandon the transmission of the hidden - node indication. Non - competing random access opportunities for sub - band / BWP selection (but not limited thereto) To configure this association, for example, RRC IEs such as rach - ConfigSBs are taken as an example It is proposed that it be configured via upper layer parameters. This RRC parameter can be transmitted as part of the sub - band / BWP configuration. A one - to - one mapping procedure or a one - to - many mapping procedure can be used

[0090] In the case of a one - to - one mapping procedure, the UE can transmit a PRACH preamble on the relevant resources for each DL sub - band without hidden nodes. For example, the DL sub - band is available on the UE side. Figure 25 shows an example of four DL sub - bands and their associated UL sub - bands. The gNB can start RACH transmission on the associated UL sub - band for each available DL sub - band. The UE can transmit a RACH preamble when the DL sub - band is not affected by hidden nodes, for example, when the DL sub - band is available on the UE side. This can be applicable to both TDD and FDD cases

[0091] Figure 25 shows an example of the use of one - to - one CFRA transmission to show the availability of DL sub - bands in the case of TDD. In the example of Figure 25, the gNB cannot start non - competing RACH (CFRA) on UL SB3 associated with the unavailable DL SB3. Also, the gNB can start CFRA on UL SB1 associated with DL SB1 available on the gNB side. However, since there is a hidden node in SB1, the UE does not transmit a RACH preamble. Each time the gNB starts CFRA on a specific sub - band ​​​​​​​​​​​​​​ The gNB can trigger a timer, for example, called SB_switchingTimer, to monitor the RACH preamble. If this timer expires without the RACH preamble being received, the gNB can infer that there are hidden nodes in this DL sub-band around the UE. For example, it can be inferred that the DL sub-band cannot be used on the UE side. In this specification, in addition to the PDCCH commands scrambled by C-RNTI, it is also proposed that the PDCCH commands can be transmitted in a common search space scrambled by a new RNTI, such as DL_SB_check-RNTI. This can be beneficial when there is a DL sub-band intended for use by multiple UEs. In this case, the gNB can send PDCCH commands to the target group of UEs to obtain an assessment of the hidden nodes on this sub-band. When the UE is configured with multiple BWPs and only a single BWP or multiple BWPs are activated at any given time, and in the TDD operating mode, the PRACH time-frequency resources are on the paired UL BWP. However, in the case of FDD, due to LBT interference on the UE side, if the UL BWP paired with the DL BWP under evaluation is not available, this DL BWP under evaluation may not be affected by hidden nodes. For example, the DL BWP may be available on the UE side. Therefore, this specification proposes that the UE can switch the active UL BWP to another available UL BWP. To achieve this purpose, the gNB can... For example, it can be inferred that the DL sub-band cannot be used on the UE side.

[0092] In this specification, in addition to the PDCCH commands scrambled by C-RNTI, it is also proposed that the PDCCH commands can be transmitted in a common search space scrambled by a new RNTI, such as DL_SB_check-RNTI. This can be beneficial when there is a DL sub-band intended for use by multiple UEs. In this case, the gNB can send PDCCH commands to the target group of UEs to obtain an assessment of the hidden nodes on this sub-band. To obtain an assessment of the hidden nodes on this sub-band, the gNB can send PDCCH commands to the target group of UEs. This can be beneficial when there is a DL sub-band intended for use by multiple UEs.

[0093] When the UE is configured with multiple BWPs and only a single BWP or multiple BWPs are activated at any given time, and in the TDD operating mode, the PRACH time-frequency resources are on the paired UL BWP. However, in the case of FDD, due to LBT interference on the UE side, if the UL BWP paired with the DL BWP under evaluation is not available, this DL BWP under evaluation may not be affected by hidden nodes. For example, the DL BWP may be available on the UE side. Therefore, this specification proposes that the UE can switch the active UL BWP to another available UL BWP. To achieve this purpose, the gNB can... To achieve this purpose, the gNB can... RACH resources can be provided across different UL BWPs. Further, the gNB To reduce the burden of detecting the PRACH preamble on it, for each UL BWP After the expiration of the configured timer, e.g., BWP_access_timer, the UE can attempt to transmit the PRACH preamble in a specific order across different UL BWPs For example, The UE can attempt to access the UL BWP paired with the DL BWP under evaluation until the timer BWP_access_timer expires. When this timer expires, the UE can switch to another UL BWP according to a predefined order. Next, the UE can continue to attempt to access the new UL BWP until the timer associated with it expires

[0094] In the case of one-to-many mapping procedures, instead of transmitting the PRACH preamble for each available DL sub-band / BWP without hidden nodes, e.g., the DL sub-band / BWP available at the UE side, the UE can use a specific time-frequency resource or preamble indicating multiple sub-bands / BWP without hidden nodes available at the UE side For example, the UE can transmit one PRACH preamble on a CFRA resource associated with one available DL sub-band / BWP at the UE side. However, different preambles can be used for different combinations of DL sub-bands / BWP available at the UE side. Therefore, when the gNB receives the RACH preamble, the gNB can infer which combinations of DL sub-bands / BWP are not affected by hidden nodes ​​​​​​​​​​​​

[0095] In this specification, for example, a DL sub-band / BW without hidden nodes that is available on the UE side It is also proposed to adopt a sounding reference signal (SRS) as an indicator to P To achieve this purpose, this specification proposes to further add use cases to the SRS upper layer parameter usage method such as SB_indication / BWP_indication. The main feature of this S RS usage method is that the UE can choose not to transmit the SRS associated with the DL sub-band That is. For example, for each available DL sub-band, the gNB As shown in FIG. 26, the SRS can be activated by using SB_indication so that each SRS is associated with a specific DL sub-band / BWP In this way. The UE can, for example Transmit only the SRS associated with the DL sub-band without hidden nodes that is available on the UE side The gNB can, for example, set a timer called SRS_SB-timer to Receive the SRS. If this timer expires and the gNB does not detect SRS transmission The gNB may infer that the DL sub-band is not available on the UE side. If the UL sub-band Does not overlap with the DL sub-band, procedures similar to those used for FDD can be adopted In the case of FDD, when there are no hidden nodes in the DL sub-band / BWP, but the UE cannot access the UL sub-band / BWP that is supposed to carry the SRS If the gNB provides resources for another UL sub-band / BWP, the UE can attempt to use another UL sub-band / B

[0096] WP. The UE can use another UL sub-band such as the sub-band / BWP ID If the UL sub-band / BWP that the UE is supposed to carry the SRS cannot be accessed, and the gNB provides resources for another UL sub-band / BWP The UE can attempt to use another UL sub-band / B WP. The UE can use another UL sub-band such as the sub-band / BWP ID When attempting to transmit SRS on the DL / BWP, specific instructions can be followed. The UE can continue to attempt access to each UL sub-band / BWP for a specific period. To achieve this, this specification proposes a timer that can be used by the UE to switch to other UL sub-bands / BWP upon expiration.

[0097] (Signaling of the selected DL sub-band / BWP) After exchanging information with the UE, the gNB may need to select one or more from the sub-bands indicated by the UE as having no hidden nodes. One possible solution is to signal the sub-band configuration adopting the aforementioned solution and indicating the LBT result. As another set of solutions, the selected DL sub-band can be selected according to specific rules so that both the gNB and the UE have the same understanding of which DL sub-band is used for transmission. For example, the DL sub-band with the lowest ID is the sub-band that the gNB can use.

[0098] After information is exchanged between the UE and the gNB, if a single DL BWP is not affected by hidden nodes and only one active DL BWP can be activated at any time, the UE can switch to this DL BWP. On the other hand, if multiple DL BWPs are not affected by hidden nodes and only one active DL BWP can be activated at any time, the UE can expect to receive BWP activation on the PCell that can be used in CA mode. In the case of DL or SA NR-U, the UE can monitor the BWP using an ID according to specific rules. For example, the UE can assume that there are no hidden nodes and monitor the BWP using the ID according to specific rules. For example, the UE can assume that there are no hidden nodes ​The BWP having the smallest ID among those shown can be monitored.

[0099] After information is exchanged between the UE and the gNB, if the UE is configured using a plurality of DL BWPs and multiple DL BWPs can be activated at any given time when the entire DL BWP is available, the UE monitors those DL BWPs if they do not have hidden nodes. If there are no hidden nodes in a subset of the first activated DL BWPs, the UE monitors this subset of DL BWPs. Also, herein, it is proposed that the UE can receive on the Pcell the DCI that activates a plurality of BWPs on the SCell. This DCI may include a bitmap field indicating which DL BWPs are being activated (which can be called "one-shot multiple DL BWP activation") on the Scell.

[0100] Furthermore, herein, it is proposed that the gNB can transmit a plurality of DCIs to sequentially activate those multiple DL BWPs (for example, one DCI activates one DL BWP). Herein, a 1-bit field is proposed. This indication bit field indicates that if it is not switched, the UE should monitor the newly activated DL BWP in addition to the previously activated DL BWP. When this bit field is switched, the UE interprets the DCI activation command as a DL BWP switching command, and the UE can deactivate the old active BWP and activate the indicated new BWP.

[0101] ​​​​​​​​​​​​​​​ In DC or SA NR-U, the UE only has one DL BWP with no hidden nodes. This DL BWP can be, for example, the DL BWP with the smallest ID or the hidden If there is no node, it can be selected according to certain rules, such as the first DL BWP. Next, using a similar procedure as above, the DCI will create a Scell ​​for this special DL BWP. Multiple DL BWPs can be added when sent over the

[0102] (Enhanced sub-band indication) Explicit or implicit indicators may be used to indicate available or unavailable DL subbands. Different information about the available subbands can be used. For example, a gNB may indicate to a group of UEs that it has LBT access to a particular BWP. Successfully acquires the entire subband and indicates such information to a group of UEs, while A subset of the available LBT subbands may be indicated to another group of UEs.

[0103] Each UE is informed by several criteria such as its capabilities, power saving requirements, channel quality, and UE location. UEs can be grouped based on their available Each UE is expected to receive the same indication in one or more of the subbands. The group index of the number is determined by higher layer signaling, RRC parameters such as SBgroupID, etc. Alternatively, multiple group IDs may be configured in the UE by higher layer signaling. and uses the MAC-CE to group UEs into one or more groups by indicating their identity. Additionally or alternatively, DCI can be used to semi-statically assign Introduce a new field in DCI to provide UL / DL authorization for indicating group IDs By doing so, the UE can be dynamically assigned to a specific group. Such a field can be, for example, a bitmap indicating the group to which the UE belongs.

[0104] The available LBT subbands can be indicated to various UEs or groups of UEs using GC-PDCCH. The GC-PDCCH can include dedicated bit fields for each UE or each group of UEs to indicate the available subbands. For example, assuming that the gNB constructs N groups of UEs represented by G1, …, G respectively. As an example, setting M to 4 bits, as shown in FIG. 36, M bits can be used for each UE or UE group N to indicate the available LBT subbands. The total number of constructed groups and the number of bits required to indicate the available LBT subbands, i.e., N and M respectively, can be indicated via upper layer signaling. This fixes the size of the GC-PDCCH, and all UEs configured to receive the GC-PDCCH and all UEs belonging to any group can recognize it and know which LBT subband indication bits to read. For example, G1 UEs read the lowest 4 bits, G2 UEs read the next 4 bits, and so on. The GC-PDCCH can include other fields carrying other information that is common to all UEs or specialized for only some groups of UEs. For example, a single MCOT value can be indicated to all UEs, or each field can be specialized for each group of UEs. This way, all UEs configured to receive the GC-PDCCH and all UEs belonging to any group can recognize it and know which LBT subband indication bits to read. For example, G1 UEs read the lowest 4 bits, G2 UEs read the next 4 bits, and so on. The GC-PDCCH can include other fields carrying other information that is common to all UEs or specialized for only some groups of UEs. For example, a single MCOT value can be indicated to all UEs, or each field can be specialized for each group of UEs. This way, all UEs configured to receive the GC-PDCCH and all UEs belonging to any group can recognize it and know which LBT subband indication bits to read. For example, G1 UEs read the lowest 4 bits, G2 UEs read the next 4 bits, and so on. The GC-PDCCH Therefore, different MCOT values can be indicated to different groups of UEs.

[0105] Alternatively, the GC-PDCCH may include two fields. For example, as shown in FIG. 37 the first field may indicate the available LBT subbands, e.g., called the SB indication field, and the second field may indicate which UE or group of UEs is addressed by this GC-PDCCH, e.g., called the group indication field. The group indication field can carry a group ID that enables the GC-PDCCH to indicate the available LBT subbands to a single UE or a group of UEs, and is composed of log2(number of groups) bits and can be called the group-specific PDCCH. The group indication field can be a bit string of a length equal to the number of UEs or groups of UEs, and each bit can indicate a specific UE or group of UEs. For example, the most significant bit can represent G and the least significant bit can represent G1. Thereby, the gNB can signal the same available LBT subbands to multiple UEs or groups of UEs at any time when applicable. The sizes of the first and second fields of the GC-PDCCH can be configured by upper layer signaling. The GC-PDCCH may include other fields that carry information for all UEs or groups of UEs, or only for some UEs or groups of UEs. For example, a single MCOT value can be indicated to all UEs or groups of UEs, or a single MCOT value can be indicated to a group when applicable at any time of UEs or groups of UEs. For example, the most significant bit can represent G N and the least significant bit can represent G1. Thus, the gNB can signal the same available LBT subbands to multiple UEs or groups of UEs at any time when applicable. The first and second fields of the GC-PDCCH can be configured by upper layer signaling. The GC-PDCCH may include other fields that carry information for all UEs or groups of UEs, or only for some UEs or groups of UEs. For example, a single MCOT value can be indicated to all UEs or groups of UEs, or a single MCOT value can be indicated to a group of UEs or groups of UEs. The sizes of the first and second fields of the GC-PDCCH can be configured by upper layer signaling. The GC-PDCCH may include other fields that carry information for all UEs or groups of UEs, or only for some UEs or groups of UEs. For example, a single MCOT value can be indicated to all UEs or groups of UEs, or a single MCOT value can be indicated to a group of UEs or groups of UEs only when applicable at any time. For example, a single MCOT value can be indicated to all UEs or groups of UEs, or alternatively, a single MCOT value can be indicated to a group Can be indicated to a subset of UEs or UE groups indicated by the indication field Can be

[0106] Another possible solution is that the gNB can assume that a plurality of group IDs and UEs are available, and can constitute a 2-tuple of available sub-band IDs, for example, (group ID, available sub-band ID), and the gNB can activate or trigger single or multiple tuples via GC-PDCCH, reference signals, etc. For example, Table 4 shows a method of associating K different tuples and group IDs with specific available LBT sub-bands. Such a configuration can be signaled via upper layer signaling. Next, based on the result of LBT, single or multiple rows can be indicated to the UE. For example, the GC-PDCCH may include a K-bit bitfield where each bit corresponds to a specific configuration. Next, the GC-PDCCH can indicate a plurality of configurations that are simultaneously activated. Alternatively, instead of using a K-bit bitmap, the GC-PDCCH can use a log2(K)-bit field to indicate the tuple ID. If other signals or channels are deployed to carry single or multiple tuple IDs, the same method can be adopted. For example, the characteristics of these reference signals (such as DMRS, CSI-RS, SSS, PSSS, etc.), such as the initialization sequence, pattern, etc., are mapped to a specific tuple ID. This mapping can be indicated by upper layer signaling. Can be Sub-band ID), and the gNB can activate or trigger single or multiple tuples via GC-PDCCH, reference signals, etc. For example, Table 4 shows a method of associating K different tuples and group IDs with specific available LBT sub-bands. Such a configuration can be signaled via upper layer signaling. Next, based on the result of LBT, single or multiple rows can be indicated to the UE. For example, the GC-PDCCH may include a K-bit bitfield where each bit corresponds to a specific configuration. Next, the GC-PDCCH can indicate a plurality of configurations that are simultaneously activated. Alternatively, instead of using a K-bit bitmap, the GC-PDCCH can use a log2(K)-bit field to indicate the tuple ID. If other signals or channels are deployed to carry single or multiple tuple IDs, the same method can be adopted. For example, the characteristics of these reference signals (such as DMRS, CSI-RS, SSS, PSSS, etc.), such as the initialization sequence, pattern, etc., are mapped to a specific tuple ID. This mapping can be indicated by upper layer signaling. Sub-band ID), and the gNB can activate or trigger single or multiple tuples via GC-PDCCH, reference signals, etc. For example, Table 4 shows a method of associating K different tuples and group IDs with specific available LBT sub-bands. Such a configuration can be signaled via upper layer signaling. Next, based on the result of LBT, single or multiple rows can be indicated to the UE. For example, the GC-PDCCH may include a K-bit bitfield where each bit corresponds to a specific configuration. Next, the GC-PDCCH can indicate a plurality of configurations that are simultaneously activated. Alternatively, instead of using a K-bit bitmap, the GC-PDCCH can use a log2(K)-bit field to indicate the tuple ID. If other signals or channels are deployed to carry single or multiple tuple IDs, the same method can be adopted. For example, the characteristics of these reference signals (such as DMRS, CSI-RS, SSS, PSSS, etc.), such as the initialization sequence, pattern, etc., are mapped to a specific tuple ID. This mapping can be indicated by upper layer signaling. 4 shows a method of associating K different tuples and group IDs with specific available LBT sub-bands. Such a configuration can be signaled via upper layer signaling. Next, based on the result of LBT, single or multiple rows can be indicated to the UE. For example, the GC-PDCCH may include a K-bit bitfield where each bit corresponds to a specific configuration. Next, the GC-PDCCH can indicate a plurality of configurations that are simultaneously activated. Alternatively, instead of using a K-bit bitmap, the GC-PDCCH can use a log2(K)-bit field to indicate the tuple ID. If other signals or channels are deployed to carry single or multiple tuple IDs, the same method can be adopted. For example, the characteristics of these reference signals (such as DMRS, CSI-RS, SSS, PSSS, etc.), such as the initialization sequence, pattern, etc., are mapped to a specific tuple ID. This mapping can be indicated by upper layer signaling. 4 shows a method of associating K different tuples and group IDs with specific available LBT sub-bands. Such a configuration can be signaled via upper layer signaling. Next, based on the result of LBT, single or multiple rows can be indicated to the UE. For example, the GC-PDCCH may include a K-bit bitfield where each bit corresponds to a specific configuration. Next, the GC-PDCCH can indicate a plurality of configurations that are simultaneously activated. Alternatively, instead of using a K-bit bitmap, the GC-PDCCH can use a log2(K)-bit field to indicate the tuple ID. If other signals or channels are deployed to carry single or multiple tuple IDs, the same method can be adopted. For example, the characteristics of these reference signals (such as DMRS, CSI-RS, SSS, PSSS, etc.), such as the initialization sequence, pattern, etc., are mapped to a specific tuple ID. This mapping can be indicated by upper layer signaling. 4 shows a method of associating K different tuples and group IDs with specific available LBT sub-bands. Such a configuration can be signaled via upper layer signaling. Next, based on the result of LBT, single or multiple rows can be indicated to the UE. For example, the GC-PDCCH may include a K-bit bitfield where each bit corresponds to a specific configuration. Next, the GC-PDCCH can indicate a plurality of configurations that are simultaneously activated. Alternatively, instead of using a K-bit bitmap, the GC-PDCCH can use a log2(K)-bit field to indicate the tuple ID. If other signals or channels are deployed to carry single or multiple tuple IDs, the same method can be adopted. For example, the characteristics of these reference signals (such as DMRS, CSI-RS, SSS, PSSS, etc.), such as the initialization sequence, pattern, etc., are mapped to a specific tuple ID. This mapping can be indicated by upper layer signaling. 4 shows a method of associating K different tuples and group IDs with specific available LBT sub-bands. Such a configuration can be signaled via upper layer signaling. Next, based on the result of LBT, single or multiple rows can be indicated to the UE. For example, the GC-PDCCH may include a K-bit bitfield where each bit corresponds to a specific configuration. Next, the GC-PDCCH can indicate a plurality of configurations that are simultaneously activated. Alternatively, instead of using a K-bit bitmap, the GC-PDCCH can use a log2(K)-bit field to indicate the tuple ID. If other signals or channels are deployed to carry single or multiple tuple IDs, the same method can be adopted. For example, the characteristics of these reference signals (such as DMRS, CSI-RS, SSS, PSSS, etc.), such as the initialization sequence, pattern, etc., are mapped to a specific tuple ID. This mapping can be indicated by upper layer signaling. 4 shows a method of associating K different tuples and group IDs with specific available LBT sub-bands. Such a configuration can be signaled via upper layer signaling. Next, based on the result of LBT, single or multiple rows can be indicated to the UE. For example, the GC-PDCCH may include a K-bit bitfield where each bit corresponds to a specific configuration. Next, the GC-PDCCH can indicate a plurality of configurations that are simultaneously activated. Alternatively, instead of using a K-bit bitmap, the GC-PDCCH can use a log2(K)-bit field to indicate the tuple ID. If other signals or channels are deployed to carry single or multiple tuple IDs, the same method can be adopted. For example, the characteristics of these reference signals (such as DMRS, CSI-RS, SSS, PSSS, etc.), such as the initialization sequence, pattern, etc., are mapped to a specific tuple ID. This mapping can be indicated by upper layer signaling. 4 shows a method of associating K different tuples and group IDs with specific available LBT sub-bands. Such a configuration can be signaled via upper layer signaling. Next, based on the result of LBT, single or multiple rows can be indicated to the UE. For example, the GC-PDCCH may include a K-bit bitfield where each bit corresponds to a specific configuration. Next, the GC-PDCCH can indicate a plurality of configurations that are simultaneously activated. Alternatively, instead of using a K-bit bitmap, the GC-PDCCH can use a log2(K)-bit field to indicate the tuple ID. If other signals or channels are deployed to carry single or multiple tuple IDs, the same method can be adopted. For example, the characteristics of these reference signals (such as DMRS, CSI-RS, SSS, PSSS, etc.), such as the initialization sequence, pattern, etc., are mapped to a specific tuple ID. This mapping can be indicated by upper layer signaling. 4 shows a method of associating K different tuples and group IDs with specific available LBT sub-bands. Such a configuration can be signaled via upper layer signaling. Next, based on the result of LBT, single or multiple rows can be indicated to the UE. For example, the GC-PDCCH may include a K-bit bitfield where each bit corresponds to a specific configuration. Next, the GC-PDCCH can indicate a plurality of configurations that are simultaneously activated. Alternatively, instead of using a K-bit bitmap, the GC-PDCCH can use a log2(K)-bit field to indicate the tuple ID. If other signals or channels are deployed to carry single or multiple tuple IDs, the same method can be adopted. For example, the characteristics of these reference signals (such as DMRS, CSI-RS, SSS, PSSS, etc.), such as the initialization sequence, pattern, etc., are mapped to a specific tuple ID. This mapping can be indicated by upper layer signaling. 4 shows a method of associating K different tuples and group IDs with specific available LBT sub-bands. Such a configuration can be signaled via upper layer signaling. Next, based on the result of LBT, single or multiple rows can be indicated to the UE. For example, the GC-PDCCH may include a K-bit bitfield where each bit corresponds to a specific configuration. Next, the GC-PDCCH can indicate a plurality of configurations that are simultaneously activated. Alternatively, instead of using a K-bit bitmap, the GC-PDCCH can use a log2(K)-bit field to indicate the tuple ID. If other signals or channels are deployed to carry single or multiple tuple IDs, the same method can be adopted. For example, the characteristics of these reference signals (such as DMRS, CSI-RS, SSS, PSSS, etc.), such as the initialization sequence, pattern, etc., are mapped to a specific tuple ID. This mapping can be indicated by upper layer signaling. 4 shows a method of associating K different tuples and group IDs with specific available LBT sub-bands. Such a configuration can be signaled via upper layer signaling. Next, based on the result of LBT, single or multiple rows can be indicated to the UE. For example, the GC-PDCCH may include a K-bit bitfield where each bit corresponds to a specific configuration. Next, the GC-PDCCH can indicate a plurality of configurations that are simultaneously activated. Alternatively, instead of using a K-bit bitmap, the GC-PDCCH can use a log2(K)-bit field to indicate the tuple ID. If other signals or channels are deployed to carry single or multiple tuple IDs, the same method can be adopted. For example, the characteristics of these reference signals (such as DMRS, CSI-RS, SSS, PSSS, etc.), such as the initialization sequence, pattern, etc., are mapped to a specific tuple ID. This mapping can be indicated by upper layer signaling. 4 shows a method of associating K different tuples and group IDs with specific available LBT sub-bands. Such a configuration can be signaled via upper layer signaling. Next, based on the result of LBT, single or multiple rows can be indicated to the UE. For example, the GC-PDCCH may include a K-bit bitfield where each bit corresponds to a specific configuration. Next, the GC-PDCCH can indicate a plurality of configurations that are simultaneously activated. Alternatively, instead of using a K-bit bitmap, the GC-PDCCH can use a log2(K)-bit field to indicate the tuple ID. If other signals or channels are deployed to carry single or multiple tuple IDs, the same method can be adopted. For example, the characteristics of these reference signals (such as DMRS, CSI-RS, SSS, PSSS, etc.), such as the initialization sequence, pattern, etc., are mapped to a specific tuple ID. This mapping can be indicated by upper layer signaling. 4 shows a method of associating K different tuples and group IDs with specific available LBT sub-bands. Such a configuration can be signaled via upper layer signaling. Next, based on the result of LBT, single or multiple rows can be indicated to the UE. For example, the GC-PDCCH may include a K-bit bitfield where each bit corresponds to a specific configuration. Next, the GC-PDCCH can indicate a plurality of configurations that are simultaneously activated. Alternatively, instead of using a K-bit bitmap, the GC-PDCCH can use a log2(K)-bit field to indicate the tuple ID. If other signals or channels are deployed to carry single or multiple tuple IDs, the same method can be adopted. For example, the characteristics of these reference signals (such as DMRS, CSI-RS, SSS, PSSS, etc.), such as the initialization sequence, pattern, etc., are mapped to a specific tuple ID. This mapping can be indicated by upper layer signaling. Can be indicated by upper layer signaling.

[0107]

Table 4

[0108] Another possible solution is to associate each UE or UE group with, for example, a dedicated RNTI, a sub-band group RNTI (Sub-Band Group RNTI: SBG-RNTI). The group ID and the related SBG-RNTI can be configured by upper layer signaling. Furthermore, some group IDs and their related SBG-RNT I can be configured by upper layer signaling, and at least one of their MAC-CE and DCI can be used for the UE to semi-statically / dynamically select the group it belongs to. Alternatively, the UE may be able to infer the SBG-RNTI from its group ID. For example, S BG-RNTI may be equal to the group ID + a common reference RNTI (e.g., SI-RNTI, paging ing RNTI (Paging RNTI: P-RNTI), etc.). Also, any truncated version of those RNTI can be used to calculate an SBG-RNTI with some bits removed from SI-RNTI, P- RNTI, etc. For example, the top / bottom K bits are truncated so that the remaining bit length is the same as that of a normal RNT I. The common reference RNTI can also be set or specified by upper layer signaling for all UEs. The UE can only attempt to decode the GC-PDCCH scrambled by the RNTI associated with its group .

[0109] A UE can belong to multiple groups simultaneously, and the available LBT sub-bands indicated for those UEs or UE groups may be different. In that case, U ​​​​It can be assumed that E indicates that a specific combination of LBT sub-bands is available for different groups. For example, the UE can assume that the common LBT sub-bands in all indications are available, or the UE can assume that the combined LBT sub-bands shown are available. As yet another solution, this specification proposes to develop a two-step sub-band indication. In the first step, the gNB can explicitly or implicitly indicate all possible LBT sub-bands, for example, to all UEs, via at least one of the GC-PDCCH, DMRS, and other reference signals. Next, in the second step, the gNB can indicate a subset of the available LBT sub-bands to individual UEs or groups of UEs, enabling those UEs to monitor only those LBT sub-bands for the remaining time of the COT. For example, the UE can assume that a subset of the available LBT sub-bands carrying at least one of the first DL transmission, signal, and channel is the subset of LBT sub-bands that the UE may need to monitor for the remaining time of the COT. Alternatively, for example, the BWP ID field of the DCI, such as Format 1-1 DCI, can be interpreted as an LBT sub-band ID, and an additional 1-bit field can be introduced to distinguish whether the BWP ID field is used for BWP switching or for indicating a subset of the available sub-bands.

[0110] Furthermore, as yet another solution, this specification proposes to develop a two-step sub-band indication. In the first step, the gNB can explicitly or implicitly indicate all possible LBT sub-bands, for example, to all UEs, via at least one of the GC-PDCCH, DMRS, and other reference signals. Next, in the second step, the gNB can indicate a subset of the available LBT sub-bands to individual UEs or groups of UEs, enabling those UEs to monitor only those LBT sub-bands for the remaining time of the COT. For example, the UE can assume that a subset of the available LBT sub-bands carrying at least one of the first DL transmission, signal, and channel is the subset of LBT sub-bands that the UE may need to monitor for the remaining time of the COT. Alternatively, for example, the BWP ID field of the DCI, such as Format 1-1 DCI, can be interpreted as an LBT sub-band ID, and an additional 1-bit field can be introduced to distinguish whether the BWP ID field is used for BWP switching or for indicating a subset of the available sub-bands. Furthermore, the available LBT sub-bands It can be assumed that E indicates that a specific combination of LBT sub-bands is available for different groups. For example, the UE can assume that the common LBT sub-bands in all indications are available, or the UE can assume that the combined LBT sub-bands shown are available. As yet another solution, this specification proposes to develop a two-step sub-band indication. In the first step, the gNB can explicitly or implicitly indicate all possible LBT sub-bands, for example, to all UEs, via at least one of the GC-PDCCH, DMRS, and other reference signals. Next, in the second step, the gNB can indicate a subset of the available LBT sub-bands to individual UEs or groups of UEs, enabling those UEs to monitor only those LBT sub-bands for the remaining time of the COT. For example, the UE can assume that a subset of the available LBT sub-bands carrying at least one of the first DL transmission, signal, and channel is the subset of LBT sub-bands that the UE may need to monitor for the remaining time of the COT. Alternatively, for example, the BWP ID field of the DCI, such as Format 1-1 DCI, can be interpreted as an LBT sub-band ID, and an additional 1-bit field can be introduced to distinguish whether the BWP ID field is used for BWP switching or for indicating a subset of the available sub-bands.

[0111] Alternatively, for example, the BWP ID field of the DCI, such as Format 1-1 DCI, can be interpreted as an LBT sub-band ID, and an additional 1-bit field can be introduced to distinguish whether the BWP ID field is used for BWP switching or for indicating a subset of the available sub-bands. Furthermore, the available LBT sub-bands It can be assumed that E indicates that a specific combination of LBT sub-bands is available for different groups. For example, the UE can assume that the common LBT sub-bands in all indications are available, or the UE can assume that the combined LBT sub-bands shown are available. As yet another solution, this specification proposes to develop a two-step sub-band indication. In the first step, the gNB can explicitly or implicitly indicate all possible LBT sub-bands, for example, to all UEs, via at least one of the GC-PDCCH, DMRS, and other reference signals. A new field can be introduced that indicates a selected subset of the BWP, and the subset can be configured by upper layer signaling or set to be equal to the number of subbands within the activated BWP. This bit field may only indicate the indices of the available LBT subbands. This bit field may also be a bitmap that can indicate multiple LBT subbands. When other reference signals such as DMRS, CSI-RS, SSS, and PSS are used to indicate available LBT subbands, the same ideas in the above embodiments can be extended. For example, each UE or group of UEs can be associated with a specific initialization sequence, antenna port, or pattern. In NR, CORESETs other than CORESET0 are configured via upper layer parameters such as RRC IE, ControlResourceSet, etc. ControlResourceSet includes the parameter frequencyDomainResources that configures the frequency domain resources within the BWP where the CORESET is configured. The parameter frequencyDomainResources is a bit string of a size equal to 45 bits, each bit of which corresponds to a group of 6 PRBs, and the looping starts from PRB0 and is completely included in the bandwidth part where the CORESET is configured. The most significant bit corresponds to the lowest frequency group that is completely included in the bandwidth part where the CORESET is configured, and if there are subsequent lower bits, each of them corresponds to... (CORESET Monitoring) In NR, CORESETs other than CORESET0 are configured via upper layer parameters such as RRC IE, ControlResourceSet, etc. ControlResourceSet includes the parameter frequencyDomainResources that configures the frequency domain resources within the BWP where the CORESET is configured. The parameter frequencyDomainResources is a bit string of a size equal to 45 bits, each bit of which corresponds to a group of 6 PRBs, and the looping starts from PRB0 and is completely included in the bandwidth part where the CORESET is configured. The most significant bit corresponds to the lowest frequency group that is completely included in the bandwidth part where the CORESET is configured, and if there are subsequent lower bits, each of them corresponds to...

[0112] A new field can be introduced that indicates a selected subset of the BWP, and the subset can be configured by upper layer signaling or set to be equal to the number of subbands within the activated BWP. This bit field may only indicate the indices of the available LBT subbands. This bit field may also be a bitmap that can indicate multiple LBT subbands. When other reference signals such as DMRS, CSI-RS, SSS, and PSS are used to indicate available LBT subbands, the same ideas in the above embodiments can be extended. For example, each UE or group of UEs can be associated with a specific initialization sequence, antenna port, or pattern. In NR, CORESETs other than CORESET0 are configured via upper layer parameters such as RRC IE, ControlResourceSet, etc. ControlResourceSet includes the parameter frequencyDomainResources that configures the frequency domain resources within the BWP where the CORESET is configured. The parameter frequencyDomainResources is a bit string of a size equal to 45 bits, each bit of which corresponds to a group of 6 PRBs, and the looping starts from PRB0 and is completely included in the bandwidth part where the CORESET is configured. The most significant bit corresponds to the lowest frequency group that is completely included in the bandwidth part where the CORESET is configured, and if there are subsequent lower bits, each of them corresponds to... (CORESET Monitoring)

[0113] (CORESET Monitoring) In NR, CORESETs other than CORESET0 are configured via upper layer parameters such as RRC IE, ControlResourceSet, etc. ControlResourceSet includes the parameter frequencyDomainResources that configures the frequency domain resources within the BWP where the CORESET is configured. The parameter frequencyDomainResources is a bit string of a size equal to 45 bits, each bit of which corresponds to a group of 6 PRBs, and the looping starts from PRB0 and is completely included in the bandwidth part where the CORESET is configured. The most significant bit corresponds to the lowest frequency group that is completely included in the bandwidth part where the CORESET is configured, and if there are subsequent lower bits, each of them corresponds to... In NR, CORESETs other than CORESET0 are configured via upper layer parameters such as RRC IE, ControlResourceSet, etc. ControlResourceSet includes the parameter frequencyDomainResources that configures the frequency domain resources within the BWP where the CORESET is configured. The parameter frequencyDomainResources is a bit string of a size equal to 45 bits, each bit of which corresponds to a group of 6 PRBs, and the looping starts from PRB0 and is completely included in the bandwidth part where the CORESET is configured. The most significant bit corresponds to the lowest frequency group that is completely included in the bandwidth part where the CORESET is configured, and if there are subsequent lower bits, each of them corresponds to... In NR, CORESETs other than CORESET0 are configured via upper layer parameters such as RRC IE, ControlResourceSet, etc. ControlResourceSet includes the parameter frequencyDomainResources that configures the frequency domain resources within the BWP where the CORESET is configured. The parameter frequencyDomainResources is a bit string of a size equal to 45 bits, each bit of which corresponds to a group of 6 PRBs, and the looping starts from PRB0 and is completely included in the bandwidth part where the CORESET is configured. The most significant bit corresponds to the lowest frequency group that is completely included in the bandwidth part where the CORESET is configured, and if there are subsequent lower bits, each of them corresponds to... In NR, CORESETs other than CORESET0 are configured via upper layer parameters such as RRC IE, ControlResourceSet, etc. ControlResourceSet includes the parameter frequencyDomainResources that configures the frequency domain resources within the BWP where the CORESET is configured. The parameter frequencyDomainResources is a bit string of a size equal to 45 bits, each bit of which corresponds to a group of 6 PRBs, and the looping starts from PRB0 and is completely included in the bandwidth part where the CORESET is configured. The most significant bit corresponds to the lowest frequency group that is completely included in the bandwidth part where the CORESET is configured, and if there are subsequent lower bits, each of them corresponds to... In NR, CORESETs other than CORESET0 are configured via upper layer parameters such as RRC IE, ControlResourceSet, etc. ControlResourceSet includes the parameter frequencyDomainResources that configures the frequency domain resources within the BWP where the CORESET is configured. The parameter frequencyDomainResources is a bit string of a size equal to 45 bits, each bit of which corresponds to a group of 6 PRBs, and the looping starts from PRB0 and is completely included in the bandwidth part where the CORESET is configured. The most significant bit corresponds to the lowest frequency group that is completely included in the bandwidth part where the CORESET is configured, and if there are subsequent lower bits, each of them corresponds to... In NR, CORESETs other than CORESET0 are configured via upper layer parameters such as RRC IE, ControlResourceSet, etc. ControlResourceSet includes the parameter frequencyDomainResources that configures the frequency domain resources within the BWP where the CORESET is configured. The parameter frequencyDomainResources is a bit string of a size equal to 45 bits, each bit of which corresponds to a group of 6 PRBs, and the looping starts from PRB0 and is completely included in the bandwidth part where the CORESET is configured. The most significant bit corresponds to the lowest frequency group that is completely included in the bandwidth part where the CORESET is configured, and if there are subsequent lower bits, each of them corresponds to... In NR, CORESETs other than CORESET0 are configured via upper layer parameters such as RRC IE, ControlResourceSet, etc. ControlResourceSet includes the parameter frequencyDomainResources that configures the frequency domain resources within the BWP where the CORESET is configured. The parameter frequencyDomainResources is a bit string of a size equal to 45 bits, each bit of which corresponds to a group of 6 PRBs, and the looping starts from PRB0 and is completely included in the bandwidth part where the CORESET is configured. The most significant bit corresponds to the lowest frequency group that is completely included in the bandwidth part where the CORESET is configured, and if there are subsequent lower bits, each of them corresponds to... In NR, CORESETs other than CORESET0 are configured via upper layer parameters such as RRC IE, ControlResourceSet, etc. ControlResourceSet includes the parameter frequencyDomainResources that configures the frequency domain resources within the BWP where the CORESET is configured. The parameter frequencyDomainResources is a bit string of a size equal to 45 bits, each bit of which corresponds to a group of 6 PRBs, and the looping starts from PRB0 and is completely included in the bandwidth part where the CORESET is configured. The most significant bit corresponds to the lowest frequency group that is completely included in the bandwidth part where the CORESET is configured, and if there are subsequent lower bits, each of them corresponds to... The group corresponding to the next lower frequency that is completely included in the bandwidth part in which the CORESET is configured. Corresponds to the loop. Bits corresponding to groups that are not completely included in the bandwidth part in which the CORESET is configured are set to zero. In NR-U, when LBT is performed in subbands within a BWP, such a configuration may not be appropriate. If the PRBs configured as part of the CORESET are included in subbands that are unavailable due to LBT impairments, this CORESET is punctured.

[0114] If the method of mapping the CORESET time / frequency resources to only available subbands is not known, the probability of successful PDCCH decoding is significantly reduced. In the above embodiments, various solutions are proposed that enable the gNB to indicate which subbands within the configured BWP are available and which subbands are unavailable for subband configurations that do not depend on LBT or subband configurations that depend on LBT. However, a different set of decisions and procedures may be required to define the behavior of the UE that monitors various configured CORESETs. For example, Figure 10A shows that the CORESET is configured to span three consecutive subbands, SB1, SB2, and SB3. Since the channel is unavailable in SB2, this CORESET may be remapped to other available SBs. One solution is to maintain the period of the new CORESET. For example, fix the number of symbols of the CORESET, the number of frequency domain resources, etc. For example, as shown in Figure 10B, while keeping the period of the new CORESET the same as the period of the original CORESET, the CORE is spread across the available subbands. ​​​​​​​​​​​ Remap the frequency domain resources of the SET so that both the original CORESET and the new CORE SET have the same number of frequency domain resources. Another possible solution is to C hange both the duration of the ORESET and the number of frequency domain resources. For example, in FIGS. 10C and 10D, the new CORESET can have a longer duration and fewer frequency domain resources than the original CORESET. In both FIGS. 10C and 1 0D, the frequency domain resources are distributed over discontinuous subbands. Alternatively, the frequency domain resources can be distributed over discontinuous subbands as shown, for example, in FIG. 10E. Another configuration of the new CORESET can be the same as the original CORESET, or a different set of configurations may be required for the new CORESET. Such configurations include, for example, 1) the mapping method to resource element groups (REGs) of control channel elements (CCEs), 2) the number of REGs within a REG bundle, 3) the interleaver-related parameters, 4) the quasi-collocation (QCL) configuration, 5) the initialization of the pseudo-random noise (PN) scrambling of the physical downlink control channel (PDCCH) demodulation reference signal (DMRS), etc. In addition to other configurations that may need to be changed, there are many possibilities to remap the time and frequency domain resources of the old CORESET to the new CORESET. Therefore, it is assumed that both the gNB and the UE need to have the same understanding of the remapping of the CORESET and its configuration based on the result of the subband LBT. Next, some procedures for establishing such an understanding between the gNB and the UE are proposed. Another configuration of the new CORESET can be the same as the original CORESET, or a different set of configurations may be required for the new CORESET. Such configurations include, for example, 1) the mapping method to resource element groups (REGs) of control channel elements (CCEs), 2) the number of REGs within a REG bundle, 3) the interleaver-related parameters, 4) the quasi-collocation (QCL) configuration, 5) the initialization of the pseudo-random noise (PN) scrambling of the physical downlink control channel (PDCCH) demodulation reference signal (DMRS), etc. In addition to other configurations that may need to be changed, there are many possibilities to remap the time and frequency domain resources of the old CORESET to the new CORESET. Therefore, it is assumed that both the gNB and the UE need to have the same understanding of the remapping of the CORESET and its configuration based on the result of the subband LBT. Next, some procedures for establishing such an understanding between the gNB and the UE are proposed. In addition to other configurations that may need to be changed, there are many possibilities to remap the time and frequency domain resources of the old CORESET to the new CORESET. Therefore, it is assumed that both the gNB and the UE need to have the same understanding of the remapping of the CORESET and its configuration based on the result of the subband LBT. Next, some procedures for establishing such an understanding between the gNB and the UE are proposed. In addition to other configurations that may need to be changed, there are many possibilities to remap the time and frequency domain resources of the old CORESET to the new CORESET. Therefore, it is assumed that both the gNB and the UE need to have the same understanding of the remapping of the CORESET and its configuration based on the result of the subband LBT. Next, some procedures for establishing such an understanding between the gNB and the UE are proposed. In addition to other configurations that may need to be changed, there are many possibilities to remap the time and frequency domain resources of the old CORESET to the new CORESET. Therefore, it is assumed that both the gNB and the UE need to have the same understanding of the remapping of the CORESET and its configuration based on the result of the subband LBT. Next, some procedures for establishing such an understanding between the gNB and the UE are proposed. In addition to other configurations that may need to be changed, there are many possibilities to remap the time and frequency domain resources of the old CORESET to the new CORESET. Therefore, it is assumed that both the gNB and the UE need to have the same understanding of the remapping of the CORESET and its configuration based on the result of the subband LBT. Next, some procedures for establishing such an understanding between the gNB and the UE are proposed.

[0115] In addition to other configurations that may need to be changed, there are many possibilities to remap the time and frequency domain resources of the old CORESET to the new CORESET. Therefore, it is assumed that both the gNB and the UE need to have the same understanding of the remapping of the CORESET and its configuration based on the result of the subband LBT. Next, some procedures for establishing such an understanding between the gNB and the UE are proposed. In addition to other configurations that may need to be changed, there are many possibilities to remap the time and frequency domain resources of the old CORESET to the new CORESET. Therefore, it is assumed that both the gNB and the UE need to have the same understanding of the remapping of the CORESET and its configuration based on the result of the subband LBT. Next, some procedures for establishing such an understanding between the gNB and the UE are proposed. In addition to other configurations that may need to be changed, there are many possibilities to remap the time and frequency domain resources of the old CORESET to the new CORESET. Therefore, it is assumed that both the gNB and the UE need to have the same understanding of the remapping of the CORESET and its configuration based on the result of the subband LBT. Next, some procedures for establishing such an understanding between the gNB and the UE are proposed. In addition to other configurations that may need to be changed, there are many possibilities to remap the time and frequency domain resources of the old CORESET to the new CORESET. Therefore, it is assumed that both the gNB and the UE need to have the same understanding of the remapping of the CORESET and its configuration based on the result of the subband LBT. Next, some procedures for establishing such an understanding between the gNB and the UE are proposed. In addition to other configurations that may need to be changed, there are many possibilities to remap the time and frequency domain resources of the old CORESET to the new CORESET. Therefore, it is assumed that both the gNB and the UE need to have the same understanding of the remapping of the CORESET and its configuration based on the result of the subband LBT. Next, some procedures for establishing such an understanding between the gNB and the UE are proposed.

[0116] (Configuration-based CORESET Remapping) The UE may be configured using information related to CORESET remapping or the information may be signaled. To achieve this purpose, the following method is proposed herein. To achieve this purpose, the following method is proposed herein. To achieve this purpose, the following method is proposed herein. · Static Configuration: In this case, upper layer parameters such as RRC IE, for example, ControlResourceSetReMapping described in Information Element 4 of the appendix, are used to configure the remapping information of the CORESET identified by the controlResourceSetId initially assigned to the subband ID identified by OldSB-Id. Since subband-based LBT is being performed, those subbands identified by OldSB-Id are not always available. The gNB may remap the CORESET identified by the controlResourceSetId to the subband identified by the NewSB-ID based on the result of the subband LBT. · Static Configuration: In this case, upper layer parameters such as RRC IE, for example, ControlResourceSetReMapping described in Information Element 4 of the appendix, are used to configure the remapping information of the CORESET identified by the controlResourceSetId initially assigned to the subband ID identified by OldSB-Id. Since subband-based LBT is being performed, those subbands identified by OldSB-Id are not always available. The gNB may remap the CORESET identified by the controlResourceSetId to the subband identified by the NewSB-ID based on the result of the subband LBT. · Static Configuration: In this case, upper layer parameters such as RRC IE, for example, ControlResourceSetReMapping described in Information Element 4 of the appendix, are used to configure the remapping information of the CORESET identified by the controlResourceSetId initially assigned to the subband ID identified by OldSB-Id. Since subband-based LBT is being performed, those subbands identified by OldSB-Id are not always available. The gNB may remap the CORESET identified by the controlResourceSetId to the subband identified by the NewSB-ID based on the result of the subband LBT. · Static Configuration: In this case, upper layer parameters such as RRC IE, for example, ControlResourceSetReMapping described in Information Element 4 of the appendix, are used to configure the remapping information of the CORESET identified by the controlResourceSetId initially assigned to the subband ID identified by OldSB-Id. Since subband-based LBT is being performed, those subbands identified by OldSB-Id are not always available. The gNB may remap the CORESET identified by the controlResourceSetId to the subband identified by the NewSB-ID based on the result of the subband LBT. · Static Configuration: In this case, upper layer parameters such as RRC IE, for example, ControlResourceSetReMapping described in Information Element 4 of the appendix, are used to configure the remapping information of the CORESET identified by the controlResourceSetId initially assigned to the subband ID identified by OldSB-Id. Since subband-based LBT is being performed, those subbands identified by OldSB-Id are not always available. The gNB may remap the CORESET identified by the controlResourceSetId to the subband identified by the NewSB-ID based on the result of the subband LBT. · Static Configuration: In this case, upper layer parameters such as RRC IE, for example, ControlResourceSetReMapping described in Information Element 4 of the appendix, are used to configure the remapping information of the CORESET identified by the controlResourceSetId initially assigned to the subband ID identified by OldSB-Id. Since subband-based LBT is being performed, those subbands identified by OldSB-Id are not always available. The gNB may remap the CORESET identified by the controlResourceSetId to the subband identified by the NewSB-ID based on the result of the subband LBT. · Static Configuration: In this case, upper layer parameters such as RRC IE, for example, ControlResourceSetReMapping described in Information Element 4 of the appendix, are used to configure the remapping information of the CORESET identified by the controlResourceSetId initially assigned to the subband ID identified by OldSB-Id. Since subband-based LBT is being performed, those subbands identified by OldSB-Id are not always available. The gNB may remap the CORESET identified by the controlResourceSetId to the subband identified by the NewSB-ID based on the result of the subband LBT. · Static Configuration: In this case, upper layer parameters such as RRC IE, for example, ControlResourceSetReMapping described in Information Element 4 of the appendix, are used to configure the remapping information of the CORESET identified by the controlResourceSetId initially assigned to the subband ID identified by OldSB-Id. Since subband-based LBT is being performed, those subbands identified by OldSB-Id are not always available. The gNB may remap the CORESET identified by the controlResourceSetId to the subband identified by the NewSB-ID based on the result of the subband LBT. The parameters OldSB-Id and NewSB-Id are composed of a single subband ID or a plurality of subband IDs that can be used when the frequency domain resources of the CORESET are distributed across multiple subbands. The parameters OldSB-Id and NewSB-Id are composed of a single subband ID or a plurality of subband IDs that can be used when the frequency domain resources of the CORESET are distributed across multiple subbands. The parameters OldSB-Id and NewSB-Id are composed of a single subband ID or a plurality of subband IDs that can be used when the frequency domain resources of the CORESET are distributed across multiple subbands. The CORESET configuration covering the new subband may include parameters such as frequencyDomainResources that can configure the frequency domain resources of the CORESET covering the new subband. The parameter frequencyDomainResources may also use a 45-bit bit string, similar to the similar parameter in the ControlResourceSetIE. Each bit The CORESET configuration covering the new subband may include parameters such as frequencyDomainResources that can configure the frequency domain resources of the CORESET covering the new subband. The parameter frequencyDomainResources may also use a 45-bit bit string, similar to the similar parameter in the ControlResourceSetIE. Each bit The CORESET configuration covering the new subband may include parameters such as frequencyDomainResources that can configure the frequency domain resources of the CORESET covering the new subband. The parameter frequencyDomainResources may also use a 45-bit bit string, similar to the similar parameter in the ControlResourceSetIE. Each bit The CORESET configuration covering the new subband may include parameters such as frequencyDomainResources that can configure the frequency domain resources of the CORESET covering the new subband. The parameter frequencyDomainResources may also use a 45-bit bit string, similar to the similar parameter in the ControlResourceSetIE. Each bit T corresponds to a group of 6 PRBs, starting from PRB0 belonging to the BWP, and the grouping includes a subset. The most significant bit corresponds to the lowest frequency group that is fully included in the BWP containing the subband in which the CORESET is configured, and for each subsequent lower bit , if any, each corresponds to the next lower frequency group that is fully included in the BWP containing the subband in which the CORESET is configured. Bits corresponding to groups that are not fully included in the BWP containing the subband in which the CORESET is configured are set to zero . Further, the parameter frequencyDomainResources can be for the BWP including the CORESET, or absolute with respect to the component carrier carrying this CORESET. Using the parameter duration, the period of the CORESET covering the new subband can be configured. The remaining parameters can be interpreted in the same way as the corresponding parameters in the ControlResourceSetIE. However, in the ControlResourceSetReMappingIE, all of these parameters are optional, and if there is no parameter, the UE can use the values in the ControlResourceSetIE corresponding to the CORESET identified by the ControlResourceSetId. See Information Element Example 4 in the appendix, the ControlResourceSetReMapping information element. Alternatively, in this specification, rather than including the index of the old subband that originally included the frequency domain resources of the CORESET, it is based only on the available subbands . Using the parameter duration, the period of the CORESET covering the new subband can be configured. The remaining parameters can be interpreted in the same way as the corresponding parameters in the ControlResourceSetIE. However, in the ControlResourceSetReMappingIE, all of these parameters are optional, and if there is no parameter, the UE can use the values in the ControlResourceSetIE corresponding to the CORESET identified by the ControlResourceSetId. See Information Element Example 4 in the appendix, the ControlResourceSetReMapping information element. That is, in the ControlResourceSetReMappingIE, all of these parameters are optional, and when there is no parameter, the UE can use the values in the ControlResourceSetIE corresponding to the CORESET identified by the ControlResourceSetId. Refer to Appendix Information Element Example 4, the ControlResourceSetReMapping information element. . Alternatively, in this specification, instead of including the index of the old subband that originally included the frequency domain resources of the CORESET, it is based only on the available subbands . It is proposed to define CORESET remapping rules. Basically, in this solution , first, remove the dependency on the indices of the old subbands that originally included the frequency domain resources of the CORESET . Upper layer parameters such as ControlResourceSetReMappingV 2 that set the remapping configuration, for example, the RRC IE, can cover all subband configurations within the relevant B WP. In this specification, a compact version of the RRC I E is proposed. Refer to the ControlResourceSetRe MappingV2 information element in Appendix Information Element Example 5. When a subband is configured and the CORESET remapping information is received by the UE , the UE can adapt to the results of the subband-based LBT at the gNB and can adjust the various CORESET configurations that the UE is supposed to monitor . FIG. 11 shows the procedure for adjusting the configuration of this CO RESET. An example of CORESET_x configured to transmit on SB2 is shown in FIG. 12. Then , due to LBT interference, SB2 becomes unavailable. Assume that the UE receives a ControlResourceSetReMappingIE with OldSB-Id and NewSB-Id set to {0, 1, 2, 3} and {0, 1, 3} respectively , or a ControlResourceSetReMappingV2IE with a BWP-SB-Confis-Id whose index is associated with SB0+SB1+SB3 . Next, when the UE recognizes that SB2 is unavailable and other subbands are available, the UE immediately recognizes on which subbands CORESET_x can be transmitted and the related configuration. In this example , Then, it is SB0. The UE continues to monitor CORESET_x until this subband becomes unavailable. If this occurs, the UE can use the ControlResourceSetReMapping IE where OldSB-Id and NewSB-Id are set to {0, 1, 3} and {1, 2, 3} respectively, or the ControlResourceSetReMappingV2 IE with the BWP-SB-Confis-Id whose index is associated with SB1+SB2+SB3. Then, the UE immediately recognizes on which subband CORESET_x can be transmitted and the related configuration. In this example, it is SB1. To avoid any ambiguity, for any tuple composed of CORESET Id, the indexes of the old and new subbands used in the ControlResourceSetReMapping IE, e.g., (controlResourceSetId, OldSB-Id, NewSB-Id), there is a unique set of configurations that defines the mapping of the CORESET, identified by controlResourceSetId, where the assigned subbands are indexed by OldSB-Id and the available subbands are indexed by NewSB-Id. Similarly, for the case of the ControlResourceSetReMappingV2 IE, when mapped to the subbands associated with the BWP-SB-Confis-Id, there is a unique set of configurations that defines the mapping of the CORESET, identified by controlResourceSetId. · Semi-static configuration: To further enhance flexibility, the same tuple composed of CORESET Id is used. The UE can use the ControlResourceSetReMapping IE where OldSB-Id and NewSB-Id are set to {0, 1, 3} and {1, 2, 3} respectively, or the ControlResourceSetReMappingV2 IE with the BWP-SB-Confis-Id whose index is associated with SB1+SB2+SB3. Then, the UE immediately recognizes on which subband CORESET_x can be transmitted and the related configuration. In this example, it is SB1. Immediately, the UE can recognize on which subband CORESET_x can be transmitted and the related configuration. In this example, it is SB1. In this example, it is SB1. To avoid any ambiguity, for any tuple composed of CORESET Id, the indexes of the old and new subbands used in the ControlResourceSetReMapping IE, e.g., (controlResourceSetId, OldSB-Id, NewSB-Id), there is a unique set of configurations that defines the mapping of the CORESET, identified by controlResourceSetId, where the assigned subbands are indexed by OldSB-Id and the available subbands are indexed by NewSB-Id. The indexes of the old and new subbands used in the ControlResourceSetReMapping IE, e.g., (controlResourceSetId, OldSB-Id, NewSB-Id), there is a unique set of configurations that defines the mapping of the CORESET, identified by controlResourceSetId, where the assigned subbands are indexed by OldSB-Id and the available subbands are indexed by NewSB-Id. (controlResourceSetId, OldSB-Id, NewSB-Id), there is a unique set of configurations that defines the mapping of the CORESET, identified by controlResourceSetId, where the assigned subbands are indexed by OldSB-Id and the available subbands are indexed by NewSB-Id. identified by controlResourceSetId, there is a unique set of configurations that defines the mapping of the CORESET, where the assigned subbands are indexed by OldSB-Id and the available subbands are indexed by NewSB-Id. The assigned subbands are indexed by OldSB-Id and the available subbands are indexed by NewSB-Id. Similarly, for the case of the ControlResourceSetReMappingV2 IE, when mapped to the subbands associated with the BWP-SB-Confis-Id, there is a unique set of configurations that defines the mapping of the CORESET, identified by controlResourceSetId. when mapped to the subbands associated with the BWP-SB-Confis-Id, there is a unique set of configurations that defines the mapping of the CORESET, identified by controlResourceSetId. identified by controlResourceSetId, there is a unique set of configurations that defines the mapping of the CORESET. There is a unique set of configurations that defines the mapping of the CORESET. To further enhance flexibility, the same tuple composed of CORESET Id , the indexes of the old and new sub-bands used in the ControlResourceSetReMappingIE, For example, (controlResourceSetId, OldSB-Id, NewSB-Id) or CORESET Id and , in order to enable the sub-bands associated with BWP-SB-Confis-Id to be associated with multiple CORESET remapping configurations, in this specification, it is proposed to use MAC-CE to narrow down the selection range of those configurations. In other words, the upper layer parameter ControlR esourceSetReMapping or ControlResourceSetReMappingV2 provides the UE with multiple CORESET remapping information of the same tuple (controlRes ourceSetId, OldSB-Id, NewSB-Id) or BWP-SB-Confis-Id, and then the MAC-CE, for example, selects which configuration among ControlResourceSetReMa ppingId or CORESET_Remapping-Id the UE can follow. If there is no MAC-CE, the UE can use the configuration with the smallest ID, for example, Cont rolResourceSetReMappingId or CORESET_Remapping-Id. · DCI for scheduling configurations: For both static and semi-static configurations, the DCI that schedules the PDSCH carried by RRC and RRC+MAC-CE respectively is signaled in the UE-specific search space using the C-RNTI, or using a dedicated RNTI such as CORESET_Remapping_RNTI, it can be signaled in the common search space or the group common PDCCH.

[0117] (CORESET Remapping Based on Pre-Specification) Alternatively, the CORESET remapping information can be pre-specified and executed according to pre-defined rules to reduce signaling overhead. In this specification, the following rules are proposed. · All of the CORESET is allocated in a single sub-band: The UE may assume that the configuration of all CORESETs except for the frequency domain resources remains unchanged. For the PRB of CORESET x allocated to the sub-band identified by SB-Id y, and when this sub-band becomes unavailable, the UE can assume that the PRB of the CORESET is centered in the sub-band closest to the sub-band where CORESET x was first configured. If there are two available sub-bands around the unavailable sub-band, the CORESET can be remapped to the sub-band with the smallest ID. For example, in Figure 13, CORESET x is first configured to be allocated to SB2 which is unavailable due to LBT. Assuming that SB0, SB2, and SB3 are available and the sub-bands closest to SB2 are SB1 and SB3, CORESET x can be remapped near the center of SB1. Using other sub-band orders, the CORESET configured first on the unavailable sub-band can be remapped. For example, instead of remapping the CORESET to the center of the sub-band closest to the sub-band where it was first configured, the CORESET can be remapped to the center of the available sub-band with the smallest ID. In Figure 1 assuming that SB0, SB2, and SB3 are available and the sub-bands closest to SB2 are SB1 and SB3, CORESET x can be remapped near the center of SB1. Using other sub-band orders, the CORESET configured first on the unavailable sub-band can be remapped. For example, instead of remapping the CORESET to the center of the sub-band closest to the sub-band where it was first configured, the CORESET can be remapped to the center of the available sub-band with the smallest ID. For example, instead of remapping the CORESET to the center of the sub-band closest to the sub-band where it was first configured, the CORESET can be remapped to the center of the available sub-band with the smallest ID. In Figure 1 In the example of 3, CORESET x is remapped to SB0 instead of SB1. Furthermore , when remapping the CORESET to a new sub-band, it is not necessary to remap it near the center of the sub-band. Any other point can be used as a reference. For example, the frequency domain resources of the CORESET may start from the lowest PRB of the selected sub-band. The frequency domain resources of the CORESET may end at, for example, the highest PRB in the selected sub-band. ·CORESET spans multiple sub-bands: If the frequency domain resources of the CORESET span multiple sub-bands and some of those sub-bands are unavailable, the frequency domain of the CORESET can be remapped to the center of all available sub-bands. For example, in Figure 14, the frequency resources of CORESET x are initially mapped across SB2 and S B3, but SB2 is unavailable due to LBT interference. Since SB0 , SB1, and SB3 are available, as shown, the same number initially configured for CORESET x can be evenly remapped near the center of all available sub-bands. Instead of remapping the CORESET across all available sub-bands , according to specific rules, the CORESET can be remapped to a subset of the available sub-bands. For example, if the CORESET is mapped across two sub-bands , it can be remapped to the center of the two available sub-bands with the smallest IDs. In the above example, SB0 and SB1 are applicable. Furthermore, the CORESET can be remapped to continuous frequency domain resources starting from a specific reference point within the selected sub-band. ​​​​​​Can be mapped. Generally, the reference point can be any PRB or frequency point inside or outside the selected sub-band. For example, it can be the lowest or highest PRB within the selected sub-band. For example, it can be the lowest or highest PRB within the selected sub-band. PRB.

[0118] In another embodiment, this document proposes to combine the signaling of the CO RESET remapping configuration via RRC or RRC+MAC-CE, or to deploy the pre-specified rules without any signaling. For example, when there is no CORESET remapping configuration, the pre-specified CORESET remapping rules can be used. Fig. 15 shows the procedure of combining both methods. When receiving an indication of sub-band change, if a static or semi-static CORESET remapping configuration is received by the UE for a specific CORESET identified by controlResoruceSetId, both the gNB and the UE use the signaled configuration. However, when there is no remapping configuration, the gNB and the UE can use the pre-specified rules. For example, when there is no CORESET remapping configuration, the pre-specified CORESET remapping rules can be used. Fig. 15 shows the procedure of combining both methods. When receiving an indication of sub-band change, if a static or semi-static CORESET remapping configuration is received by the UE for a specific CORESET identified by controlResoruceSetId, both the gNB and the UE use the signaled configuration. However, when there is no remapping configuration, the gNB and the UE can use the pre-specified rules. ring, or to deploy the pre-specified rules without any signaling. For example, when there is no CORESET remapping configuration, the pre-specified CORESET remapping rules can be used. Fig. 15 shows the procedure of combining both methods. When receiving an indication of sub-band change, if a static or semi-static CORESET remapping configuration is received by the UE for a specific CORESET identified by controlResoruceSetId, both the gNB and the UE use the signaled configuration. However, when there is no remapping configuration, the gNB and the UE can use the pre-specified rules. ring, or to deploy the pre-specified rules without any signaling. For example, when there is no CORESET remapping configuration, the pre-specified CORESET remapping rules can be used. Fig. 15 shows the procedure of combining both methods. When receiving an indication of sub-band change, if a static or semi-static CORESET remapping configuration is received by the UE for a specific CORESET identified by controlResoruceSetId, both the gNB and the UE use the signaled configuration. However, when there is no remapping configuration, the gNB and the UE can use the pre-specified rules. ring, or to deploy the pre-specified rules without any signaling. For example, when there is no CORESET remapping configuration, the pre-specified CORESET remapping rules can be used. Fig. 15 shows the procedure of combining both methods. When receiving an indication of sub-band change, if a static or semi-static CORESET remapping configuration is received by the UE for a specific CORESET identified by controlResoruceSetId, both the gNB and the UE use the signaled configuration. However, when there is no remapping configuration, the gNB and the UE can use the pre-specified rules. ring, or to deploy the pre-specified rules without any signaling. For example, when there is no CORESET remapping configuration, the pre-specified CORESET remapping rules can be used. Fig. 15 shows the procedure of combining both methods. When receiving an indication of sub-band change, if a static or semi-static CORESET remapping configuration is received by the UE for a specific CORESET identified by controlResoruceSetId, both the gNB and the UE use the signaled configuration. However, when there is no remapping configuration, the gNB and the UE can use the pre-specified rules. ring, or to deploy the pre-specified rules without any signaling. For example, when there is no CORESET remapping configuration, the pre-specified CORESET remapping rules can be used. Fig. 15 shows the procedure of combining both methods. When receiving an indication of sub-band change, if a static or semi-static CORESET remapping configuration is received by the UE for a specific CORESET identified by controlResoruceSetId, both the gNB and the UE use the signaled configuration. However, when there is no remapping configuration, the gNB and the UE can use the pre-specified rules. ring, or to deploy the pre-specified rules without any signaling. For example, when there is no CORESET remapping configuration, the pre-specified CORESET remapping rules can be used. Fig. 15 shows the procedure of combining both methods. When receiving an indication of sub-band change, if a static or semi-static CORESET remapping configuration is received by the UE for a specific CORESET identified by controlResoruceSetId, both the gNB and the UE use the signaled configuration. However, when there is no remapping configuration, the gNB and the UE can use the pre-specified rules. ring, or to deploy the pre-specified rules without any signaling. For example, when there is no CORESET remapping configuration, the pre-specified CORESET remapping rules can be used. Fig. 15 shows the procedure of combining both methods. When receiving an indication of sub-band change, if a static or semi-static CORESET remapping configuration is received by the UE for a specific CORESET identified by controlResoruceSetId, both the gNB and the UE use the signaled configuration. However, when there is no remapping configuration, the gNB and the UE can use the pre-specified rules. ring, or to deploy the pre-specified rules without any signaling. For example, when there is no CORESET remapping configuration, the pre-specified CORESET remapping rules can be used. Fig. 15 shows the procedure of combining both methods. When receiving an indication of sub-band change, if a static or semi-static CORESET remapping configuration is received by the UE for a specific CORESET identified by controlResoruceSetId, both the gNB and the UE use the signaled configuration. However, when there is no remapping configuration, the gNB and the UE can use the pre-specified rules.

[0119] (Indication of Guard Band and Its Impact on CORESET Configuration) To reduce the power leakage to adjacent frequency bands, guard bands may be required at the ends of the available sub-bands. Some methods are proposed to indicate the guard bands to the UEs operating in NR-U based on the available LBT sub-bands. To reduce the power leakage to adjacent frequency bands, guard bands may be required at the ends of the available sub-bands. Some methods are proposed to indicate the guard bands to the UEs operating in NR-U based on the available LBT sub-bands. To reduce the power leakage to adjacent frequency bands, guard bands may be required at the ends of the available sub-bands. Some methods are proposed to indicate the guard bands to the UEs operating in NR-U based on the available LBT sub-bands.

[0120] The size of the guard band is, for example, GB PRB is reserved at the ends of the available LBT sub-bands, and it can be assumed that there is no guard band between consecutive available LBT sub-bands. PRB is reserved at the ends of the available LBT sub-bands, and it can be assumed that there is no guard band between consecutive available LBT sub-bands. can be specified. FIG. 38 shows an example of a BWP divided into four sub-bands SB0, SB1, SB2, and SB3. Among them, the inner sub-bands SB1 and SB2 are available while the outer sub-bands SB0 and SB3 are not available. In this case, the L guard band PRB GB is reserved between (SB0 and SB1) and between (SB2 and SB3). Also, there is no guard band between the consecutive available sub-bands (SB1 and SB2). For any available sub-band, for example, the upper guard band width indicated by L can be different from the lower guard band width indicated by L GB,UP for this sub-band. And both L and L GB,Down can be specified. When an available LBT sub-band G B,UP is at the upper or lower end of an active BWP, there may be no need for a guard band at the upper or lower GB,Down end of this sub-band. end of this sub-band. end of this sub-band.

[0121] Alternatively, the guard band size can be configured by upper layer signaling, for example, UpperGB and L owerGB, or both the upper and lower GBs, for example, RRC parameters. When only one parameter is indicated to the UE, the UE can assume that the guard band sizes at the upper and lower ends of the available LBT sub-bands are equal and both are set to be equal to the indicated size. sub-bands are equal and both are set to be equal to the indicated size. size.

[0122] The starting point of the guard band can be indicated by upper layer signaling regarding a specific PRB such as the first PRB, BWP, or available sub-band within the carrier.

[0123] Some of the PRBs of the CORESET may overlap with the guard band. New Radio Release As specified in S15, the CORESET can be composed of consecutive or non-consecutive groups of PRBs and each group is composed of 6 consecutive PRBs and can be changed. Therefore in this specification, any group of 6 PRBs is configured for the CORESET and if it completely overlaps with the guard band, it is proposed that the UE can assume that this group of 6 PRBs is invalid and does not carry the PDCCH. This is equivalent to changing the configured frequencyDomainResources, RRC parameter that constitutes the frequency domain resource of the CORESET by setting the bit associated with the group of PRBs to zero instead of one

[0124] Furthermore, if any group of 6 PRBs is configured for the CORESET and it partially overlaps with the guard band, the UE can assume that the entire group of 6 PRBs is invalid and does not carry the PDCCH, or the UE can assume that only the PRBs that completely or partially overlap with the guard band are invalid and do not carry the PDCCH, but the other PRBs that do not overlap with the guard band can be used to carry the PDCCH

[0125] The CORESET can be configured to span multiple sub-bands, but the PDCCH can only be transmitted within the CORESET part within the available sub-band. The PDCCH can be completely restricted within the sub-band or interleaved across multiple sub-bands

[0126] ​​​​​​​​​If the PDCCH is confined to a subband, the UE detects LBT failure at the gNB side. If it is indicated that this subband is unavailable for use due to Alternatively, the UE may use other available In this case, it may be possible to attempt to decode the PDCCH within the subbands.

[0127] The UE is informed by higher layer signaling that the PDCCH is, for example, SB_Confined_PDCCH. An indication of which RRC parameters are confined to the subband In addition, higher layer signaling such as RRC parameters can be received via the PDCC. The UE may provide the subband index including H to the UE. Assume that the PDCCH is not transmitted if the CCH subband is unavailable, or Whether it is considered that it may be transmitted on other available sub-bands in the CORESET , for example, may be indicated by higher layer signaling.

[0128] The PDCCH is interleaved across several subbands, some of which are utilized. If not available, the UE shall use the interleaved parts of the PDCCH in those subbands. It can be assumed that no PDCCH interleaving is transmitted. Alternatively or additionally, the UE may indicate the subbands that carry the CORE All subbands covered by the SET carry a portion of the interleaved PDCCH. It can be assumed that this can be achieved.

[0129] (Subband search space) Since CORESET can vary based on the available subbands, this The search space related to ET can also change. For example, as the available sub-bands change based on the result of LBT, the monitoring slots, periodicity, offset, aggregation level, etc. can change. Therefore, in this specification, the following embodiments are proposed to address this issue.

[0130] It is proposed to associate the search space (SS) configuration not only with CORESET Id but also with sub-band ID. To achieve this purpose, upper-layer parameters such as the RRCSearchSpac eSBIE in Information Element Example 6 of the appendix can be used to include the sub-bands containing the frequency domain resources of the CORESET identified by ControlResourceSetId. For example, this can be incorporated into the parameter SB-Id carrying one or

[0131] more sub-band IDs containing the frequency domain resources of the CORESET.

[0132] In NR Release 15, the search space is associated with the CORESET via upper-layer signaling. Due to the uncertainty of channel access, some or all of the CORESET may not be available. Therefore, multiple CORESETs with different IDs can be configured for the UE. Next, based on the result of LBT at the gNB, the search space can be associated with an appropriate CORESET

[0133] ID. The UE can be configured to use the appropriate CORESET ID associated with the search space by upper-layer signaling for each possible result at When sub - band 0 is available, a specific search space is associated with CORESET1, and when sub - band 3 is available, it is associated with CORESET2. To achieve this purpose, for example, assuming that the BWP is composed of M sub - bands, the following RRC parameters can be introduced: SB_0, SB_1, …, SB_M - 1 . However, each indicates the appropriate CORESET ID when this sub - band is available.

[0134] Alternatively, the UE can infer the CORESET ID associated with the search space based on specific rules according to some parameters such as the search space ID and the available sub - band ID.

[0135] (Uplink BWP / Sub - band Switching for RACH and BFR) (Uplink BWP / Sub - band Switching for RACH) In NR, the initial access process starts in the UL BWP with the transmission of a physical random access channel (PRACH) preamble, which is generally known as message 1 (Msg1). When this occurs, it is assumed that message 3 (Msg3) of the RACH procedure is transmitted on the same UL BWP as the UL BWP used for Msg1 transmission. The time and frequency resources of Msg3 are known as the random access response (RAR) and are indicated in the gNB response to Msg1, which is referred to as message 2 (Msg2). In particular, in Msg2, the gNB transmits DCI format 1_0 scrambled by the RACH - RNTI (RA - RNTI), and the UE monitors a time window called the RAR window. It needs to be decoded therein. When the DCI is correctly decoded, the UE can then continue with M decode the PDSCH carrying the RAR indicating the time / frequency resources of the Sg3 The frequency domain resources of Msg3 are scheduled within the active UL BWP and allocated to the UE using uplink resource allocation type 1 indicating the resources.

[0136] In NR-U, the time between the transmission of Msg1 and the transmission of Msg3 can be long enough to reach the limit where other nodes may acquire channels that include the UL BWP / subband of the frequency domain resources and may become unavailable. To address this issue, the following embodiments are proposed in this specification. The UE can receive multiple RARs within the RAR window and can also extend this. Each RAR can provide time and frequency resources within a specific BWP. The reserved bits in the RAR can be used to indicate the BWP index, or new bits can be introduced to achieve this purpose. FIG. 16 shows an example of multiple RARs providing frequency and time domain resources on various BWPs / subbands. Next, depending on the LBT result, the UE can transmit Msg3 on the relevant uplink grant available BWP / subband. To suppress the overhead due to each UE having multiple Msg3 resources and to suppress the risk of Msg3 collision and thus the risk of detection failure at the gNB, the following is proposed in this specification. In this specification, the following embodiments are proposed.

[0137] The UE can receive multiple RARs within the RAR window and can also extend this. Each RAR can provide time and frequency resources within a specific BWP. The reserved bits in the RAR can be used to indicate the BWP index, or new bits can be introduced to achieve this purpose. FIG. 16 shows an example of multiple RARs providing frequency and time domain resources on various BWPs / subbands. Next, depending on the LBT result, the UE can transmit Msg3 on the relevant uplink grant available BWP / subband. The UE can receive multiple RARs within the RAR window and can also extend this. Each RAR can provide time and frequency resources within a specific BWP. The reserved bits in the RAR can be used to indicate the BWP index, or new bits can be introduced to achieve this purpose. FIG. 16 shows an example of multiple RARs providing frequency and time domain resources on various BWPs / subbands. Next, depending on the LBT result, the UE can transmit Msg3 on the relevant uplink grant available BWP / subband. The UE can receive multiple RARs within the RAR window and can also extend this. Each RAR can provide time and frequency resources within a specific BWP. The reserved bits in the RAR can be used to indicate the BWP index, or new bits can be introduced to achieve this purpose. FIG. 16 shows an example of multiple RARs providing frequency and time domain resources on various BWPs / subbands. Next, depending on the LBT result, the UE can transmit Msg3 on the relevant uplink grant available BWP / subband. The reserved bits in the RAR can be used to indicate the BWP index, or new bits can be introduced to achieve this purpose. FIG. 16 shows an example of multiple RARs providing frequency and time domain resources on various BWPs / subbands. Next, depending on the LBT result, the UE can transmit Msg3 on the relevant uplink grant available BWP / subband. FIG. 16 shows an example of multiple RARs providing frequency and time domain resources on various BWPs / subbands. Next, depending on the LBT result, the UE can transmit Msg3 on the relevant uplink grant available BWP / subband. Next, depending on the LBT result, the UE can transmit Msg3 on the relevant uplink grant available BWP / subband. Next, depending on the LBT result, the UE can transmit Msg3 on the relevant uplink grant available BWP / subband.

[0138] To suppress the overhead due to each UE having multiple Msg3 resources and to suppress the risk of Msg3 collision and thus the risk of detection failure at the gNB, the following is proposed in this specification. To suppress the overhead due to each UE having multiple Msg3 resources and to suppress the risk of Msg3 collision and thus the risk of detection failure at the gNB, the following is proposed in this specification. In this specification, the following is proposed. 1. The UE shall not transmit Msg3 if there are multiple available UL BWPs / sub-bands. The resources used can be divided into multiple Msg3 resources (e.g. BWP or subbands). You can choose randomly from among them. 2. Msg3 resources can be selected deterministically based on UE ID. For example, K Msg3 resources are signaled to the UE, and Msg3 resources are 0, 1, 2, …, K Assume that the UE has an index of -1. The UE selects a resource index that satisfies the following: Select: Selected resource index = UE_ID Mod K.

[0139] In another embodiment, the present specification provides a link provided on another UL BWP / sub-band. Based on the source, it may indicate time and frequency domain resources on other BWPs / subbands. It is proposed to define resource remapping rules for a particular UL. By simply shifting the resources configured on the BWP / subband, the UL BW The frequency domain resource for Msg3 can be derived on the P / subband. ,RAR explicitly provides frequency and time domain resources for Msg3 on BWP0 From this, the UE can allocate frequency domain resources to the same time position. Direct resources onto other BWPs by shifting them to the same position as on BWP0 You can allocate resources for Msg3 on a BWP other than the one with the explicit configuration. For implicit provisioning, various rules may be applied. For example, The time domain resources can be shifted to the center of other BWPs / subbands. may be the same across all BWPs, but may not be based on any BWP / subband ID, for example. It may also vary depending on that shift.

[0140] Alternatively, in this specification, the gNB can transmit only a single RAR, but proposes that it can transmit on multiple BWPs / sub-bands, with a size larger than the original size of the RAR carrying the frequency and time domain resources for Msg3. Here, it is proposed that a single RAR can carry the time and frequency resources for various BWPs / sub-bands. It is proposed that it can.

[0141] Regarding Msg4, if the UE selects a BWP other than the BWP first used for Msg1 transmission, this means that it can be surrounded by other nodes using the frequency domain corresponding to this BWP. Therefore, Msg4 may be better transmitted on the DL BWP associated with the UL BWP selected by the UE for Msg3 transmission in some cases.

[0142] (Enhancement of MSG3) To increase the possibility of accessing the channel, it may be beneficial to provide multiple transmission opportunities for MSG3 in at least one of the time and frequency domains. To provide multiple time domains, this specification proposes the following procedures or combinations thereof.

[0143] The MSG3 PUSCH time resource allocation field in the RAR, that is, the MAC Protocol Data Unit (PDU) can be extended. Different from the specification for New Radio Release 15, this field is used to carry the time domain allocation list TimeDomainAllocationList provided by the upper layer signaling or the default ​​​​​​​Rather than indicating a single line of the list specified by the slot, in this specification, this field is extended to, for example, 16 bits and used to indicate multiple lines of the time domain allocation list. In other words, this field can be regarded as a bitmap, and its length can be set to be equal to, for example, the number of lines of the time domain allocation

[0144] list. Each bit can correspond to a single line or multiple lines. The UE can consider the indicated lines as alternatives to each other and select only one candidate start position based on the LBT result. For example, Table 5 shows an example where the time resource allocation bitmap field is extended to 16 bits. Each bit corresponds to a specific slot offset K2, start symbol S,

[0145] and allocation length L. For example, if the bit corresponding

[0146] to the setup of the first and second lines is set to 1, the UE can consider that two candidate start positions are indicated at OFDM symbols 0 and 1, and the UE can select one of them based on the LBT result. Or, the size of the time resource allocation bit field in the RAR can be kept the same as the It is possible to select the PUSCH configuration.

[0147]

Table 6

[0148] Furthermore, a row representing the new configuration of the PUSCH can be added to expand the size of the configured or default time domain allocation list. The PUSCH configuration can be grouped such that each row represents a plurality of configurations. In this case, the time resource allocation bitfield continues to indicate the row index, but each row provides a plurality of starting positions of the PUSCH. For example, 4 bits of the time resource allocation bitfield can indicate the index of 16 rows, and each row can carry a plurality of configurations. For example, 4 bits of the time resource allocation bitfield can indicate the index of 16 rows, and each row can carry a plurality of configurations. For example, 4 bits of the time resource allocation bitfield can indicate the index of 16 rows, and each row can carry a plurality of configurations. For example, 4 bits of the time resource allocation bitfield can indicate the index of 16 rows, and each row can carry a plurality of configurations. For example, 4 bits of the time resource allocation bitfield can indicate the index of 16 rows, and each row can carry a plurality of configurations. For example, 4 bits of the time resource allocation bitfield can indicate the index of 16 rows, and each row can carry a plurality of configurations.

[0149] As yet another possible solution, it is possible to change, limited to some of the parameters of the time domain allocation list, without adding more rows, reinterpreting the time resource allocation bitfield, or expanding its size. In some rows, multiple K2 values can be used to provide multiple candidate starting positions across different slots. For example, in some rows of Table 7, K2 and K2 + β are two different slot offset values, and the UE can select an appropriate slot offset based on the LBT result. Similarly, multiple starting symbols can be provided in some rows. Table 7 shows an example providing S and S + α as possible starting OFDM symbols, and the UE can select an appropriate starting symbol based on the LBT result. The parameters β and α can be configured by upper layer signaling. As yet another possible solution, it is possible to change, limited to some of the parameters of the time domain allocation list, without adding more rows, reinterpreting the time resource allocation bitfield, or expanding its size. In some rows, multiple K2 values can be used to provide multiple candidate starting positions across different slots. For example, in some rows of Table 7, K2 and K2 + β are two different slot offset values, and the UE can select an appropriate slot offset based on the LBT result. Similarly, multiple starting symbols can be provided in some rows. Table 7 shows an example providing S and S + α as possible starting OFDM symbols, and the UE can select an appropriate starting symbol based on the LBT result. The parameters β and α can be configured by upper layer signaling. As yet another possible solution, it is possible to change, limited to some of the parameters of the time domain allocation list, without adding more rows, reinterpreting the time resource allocation bitfield, or expanding its size. In some rows, multiple K2 values can be used to provide multiple candidate starting positions across different slots. For example, in some rows of Table 7, K2 and K2 + β are two different slot offset values, and the UE can select an appropriate slot offset based on the LBT result. Similarly, multiple starting symbols can be provided in some rows. Table 7 shows an example providing S and S + α as possible starting OFDM symbols, and the UE can select an appropriate starting symbol based on the LBT result. The parameters β and α can be configured by upper layer signaling. As yet another possible solution, it is possible to change, limited to some of the parameters of the time domain allocation list, without adding more rows, reinterpreting the time resource allocation bitfield, or expanding its size. In some rows, multiple K2 values can be used to provide multiple candidate starting positions across different slots. For example, in some rows of Table 7, K2 and K2 + β are two different slot offset values, and the UE can select an appropriate slot offset based on the LBT result. Similarly, multiple starting symbols can be provided in some rows. Table 7 shows an example providing S and S + α as possible starting OFDM symbols, and the UE can select an appropriate starting symbol based on the LBT result. The parameters β and α can be configured by upper layer signaling. As yet another possible solution, it is possible to change, limited to some of the parameters of the time domain allocation list, without adding more rows, reinterpreting the time resource allocation bitfield, or expanding its size. In some rows, multiple K2 values can be used to provide multiple candidate starting positions across different slots. For example, in some rows of Table 7, K2 and K2 + β are two different slot offset values, and the UE can select an appropriate slot offset based on the LBT result. Similarly, multiple starting symbols can be provided in some rows. Table 7 shows an example providing S and S + α as possible starting OFDM symbols, and the UE can select an appropriate starting symbol based on the LBT result. The parameters β and α can be configured by upper layer signaling. As yet another possible solution, it is possible to change, limited to some of the parameters of the time domain allocation list, without adding more rows, reinterpreting the time resource allocation bitfield, or expanding its size. In some rows, multiple K2 values can be used to provide multiple candidate starting positions across different slots. For example, in some rows of Table 7, K2 and K2 + β are two different slot offset values, and the UE can select an appropriate slot offset based on the LBT result. Similarly, multiple starting symbols can be provided in some rows. Table 7 shows an example providing S and S + α as possible starting OFDM symbols, and the UE can select an appropriate starting symbol based on the LBT result. The parameters β and α can be configured by upper layer signaling. As yet another possible solution, it is possible to change, limited to some of the parameters of the time domain allocation list, without adding more rows, reinterpreting the time resource allocation bitfield, or expanding its size. In some rows, multiple K2 values can be used to provide multiple candidate starting positions across different slots. For example, in some rows of Table 7, K2 and K2 + β are two different slot offset values, and the UE can select an appropriate slot offset based on the LBT result. Similarly, multiple starting symbols can be provided in some rows. Table 7 shows an example providing S and S + α as possible starting OFDM symbols, and the UE can select an appropriate starting symbol based on the LBT result. The parameters β and α can be configured by upper layer signaling. As yet another possible solution, it is possible to change, limited to some of the parameters of the time domain allocation list, without adding more rows, reinterpreting the time resource allocation bitfield, or expanding its size. In some rows, multiple K2 values can be used to provide multiple candidate starting positions across different slots. For example, in some rows of Table 7, K2 and K2 + β are two different slot offset values, and the UE can select an appropriate slot offset based on the LBT result. Similarly, multiple starting symbols can be provided in some rows. Table 7 shows an example providing S and S + α as possible starting OFDM symbols, and the UE can select an appropriate starting symbol based on the LBT result. The parameters β and α can be configured by upper layer signaling. As yet another possible solution, it is possible to change, limited to some of the parameters of the time domain allocation list, without adding more rows, reinterpreting the time resource allocation bitfield, or expanding its size. In some rows, multiple K2 values can be used to provide multiple candidate starting positions across different slots. For example, in some rows of Table 7, K2 and K2 + β are two different slot offset values, and the UE can select an appropriate slot offset based on the LBT result. Similarly, multiple starting symbols can be provided in some rows. Table 7 shows an example providing S and S + α as possible starting OFDM symbols, and the UE can select an appropriate starting symbol based on the LBT result. The parameters β and α can be configured by upper layer signaling. If they are not configured, parameters β and α can be specified, and they can be functions of other system parameters such as numerology. Alternatively, RAR may indicate a plurality of slot offsets or start symbol values. To achieve this purpose, a new field may be introduced. This field may indicate the periodicity of candidate start positions, which can be represented by, for example, δ. Specifically, if the indicated slot offset is K2, the UE can assume that the MSG3 PUSCH can be transmitted in slots shifted by K2, K2 + δ, K2 + 2δ,..., or K

[0150] [Table 7]

[0151] ... up to the maximum allowable slot offset. If the indicated start symbol is S, the UE can assume that the MSG3 PUSCH can be transmitted in symbols S, S + δ, S + 2δ, ... up to S ... up to the maximum allowable start symbol index. The field indicating δ has Log2(number of possible values of δ) bits. The various periodicity values of the slot offset and start symbol can be expanded and provided by, for example, δ and δ respectively. In this case, δ max is either indicated by upper layer signaling, derived according to specific rules, or the maximum allowable slot offset specified. If the indicated start symbol is S, the UE can assume that the MSG3 PUSCH can be transmitted in symbols S, S + δ, S + 2δ, ... up to S max is either indicated by upper layer signaling, derived according to specific rules such as S = 14 - L, or the maximum allowable start symbol index specified. The field indicating δ has Log2(number of possible values of δ) bits. The various periodicity values of the slot offset and start symbol can be expanded and provided by, for example, δ and δ respectively. In this case, δ max is either indicated by upper layer signaling, derived according to specific rules, or the maximum allowable start symbol index specified. The field indicating δ has Log2(number of possible values of δ) bits. The various periodicity values of the slot offset and start symbol can be expanded and provided by, for example, δ max and δ respectively. In this case, δ max is either indicated by upper layer signaling, derived according to specific rules such as S = 14 - L, or the maximum allowable start symbol index specified. The field indicating δ has Log2(number of possible values of δ) bits. The various periodicity values of the slot offset and start symbol can be expanded and provided by, for example, δ and δ respectively. In this case, δ K and δ S respectively. In this case, δ and δ Kand δ S Two preliminary fields may be required to indicate S .

[0152] To provide multiple candidate start positions, an additional field in the RAR is used to slot Rather than indicating the offset or the periodicity of the start symbol of the MSG3 PUSCH, δ, δ K δ, S At least one of the periodicities of δ, δ S can be configured by upper layer signaling, or by indication if there is no upper layer signaling ring.

[0153] When the RAR provides multiple candidate start positions for the PUSCH of MSG3, for each or some of the provided PUSCH configurations, it may be necessary to indicate multiple modulation and coding schemes (Modulation and Coding Scheme: MCS) to the UE. Multiple MCS fields in the RAR may each be associated with a specific start position. (Modulation and Coding Scheme:MCS) to the UE. RAR The UE can derive a new MCS using several rules according to the candidate start position and the length of the PUSCH carrying MSG3. For example, if the length of the MSG3 P USCH at the candidate start position is the same as the length of the MSG3 PUSCH at the original start position, the UE can use the same MCS as that provided for the original start position. Another example is that if the length of the MSG3 PUSCH at the candidate start position is half the length of the MSG3 PUSCH at the original start position, the UE can use double the MCS provided for the original start position. For example, the MCS for the candidate start position can be expressed as in Equation 1 below is that if the length of the MSG3 PUSCH at the candidate start position is half the length of the MSG3 PUSCH at the original start position, the UE can use double the MCS provided for the original start position. For example, the MCS for the candidate start position can be expressed as in the following Equation 1 can be done.

[0154]

Equation

[0155] However, L old and M.C.S. old is the length of the original start position of MSG3 PUSCH The MCS shown is L new The new start position of the MSG3 PUS depends on The length of CH.

[0156] MSG2 specifies the channel access procedure type for MSG3 in the RACH procedure. It is useful to show the group of possible starting positions for MSG3. The same channel access procedure type may be deployed. In other cases, the channel access procedure The type may depend on the candidate start position of MSG3.

[0157] A single starting position or multiple candidates for MSG3 that deploy the same channel access procedure For example, for any of the complementary start positions, the D scrambled by the RA RNTI DCI field that schedules RAR PDSCH, such as CI format 1_0 The field can be used to indicate the channel access procedure to MSG3. The size of may be equal to log2(number of channel access procedures).

[0158] The UE accesses the channel for transmission according to the first starting position indicated in the RAR. If not, there are several options: The UE can access the channel and try to start another candidate Similarly, the channel access procedure may For example, the Log2 (number of channel access procedures) field of the RAR MAC PDU. A channel access code can be used for this purpose and indicated in the RAR itself. The indication of order is given to the DCI or RAR to carry this indication alone. DCI and RA for scheduling RAR PDSCH when there are not enough bits It can be divided among R.

[0159] In the present specification, the time domain Add an extra column to the allocation list to indicate, for each possible starting position, the associated channel We propose to display the access procedure type. For example, in Table 8, the channel access A new column has been added to show the type.

[0160] [Table 8]

[0161] In addition, the UE shall ensure that there is no delay between the first symbol carrying MSG3 and the last symbol carrying RAR. to specific rules depending on several factors such as time interval, MSG3 length, numerology, etc. Based on this, the type of channel access procedure can be inferred. For example, If the time interval between the first symbol carrying the RAR and the last symbol carrying the RAR is less than a certain threshold If ,is also smaller or larger, a particular type of channel access procedure can be applied. Figure 39 shows an example where MSG2 provides four candidate starting positions for MSG3. If the access to the cell is successful and the PUSCH is transmitted at the first or second candidate start position, If the UE successfully accesses the channel, a Type 1 channel access procedure may be deployed. If the PUSCH is transmitted at the third or fourth candidate starting position, the type 2 channel access The session procedure can be deployed. The threshold and related channel access type procedures can be configured or specified by upper layer signaling.

[0162] Uplink BWP switching for BFR

[0163] In BFR, in this specification, it is proposed that the gNB configures the UE using PRACH resources across different BWPs / sub-bands to increase the possibility for the UE to obtain a channel for sending a beam failure recovery request (BFRQ). Some of these PRACH resources are associated with non-competitive PRACH, and other resources may be associated with contention-based PRACH.

[0164] Furthermore, in this specification, it is proposed that the gNB response can be sent on a BWP with a different ID from the BWP used for BFRQ transmission. To reduce the power consumption at the UE while monitoring the gNB response, some of the above embodiments are adopted to configure a CORESET associated with recoverySearchSpaceId and monitor the gNB response for each ID of different BWPs / sub-bands.

[0165] As another embodiment, in this specification, it is proposed that the UE can monitor the CORESET associated with recoverySearchSpaceId on different BWPs / sub-bands in a specific order. For example, the UE can start monitoring this CORESET on the initially configured BWP / sub-band. Next, the UE can monitor this CORESET on the BWP. , it can be monitored in the following order: Default BWP → Initial BWP → BWP0 → BW P1 → … etc. Similarly, the UE monitors this CORESET on the subbands in the following order: It can be viewed in the order SB0 → SB1 → SB2 → … etc.

[0166] (Enhancing CSI-RS) CSI-RS is used for channel acquisition, beam management, beam fault recovery, radio link monitoring, and radio It can be configured for multiple purposes, including resource management. For all cases, the CSI-RS may be either the full bandwidth or a portion of the BWP configured for the UE. With wideband operation, the gNB can be configured to occupy only the area carrying the CSI-RS. The entire frequency band may not always be accessible. Therefore, the LBT is successful on a set of subbands that form the CSI-RS. When configured to span multiple sub-bands, all of those sub-bands are always active simultaneously. There is no guarantee that the information will be available. In this paper, we propose several CSI-RS enhancements to improve the performance of the CSI-RS.

[0167] Use the channel acquisition indication to have the UE adjust its receive filters Explicit or implicit channel acquisition indication can be provided by the gNB. In this case, the UE can indicate the subbands obtained by using the available subbands. Only Resource Elements (REs) in the RBF carry the configured CSI-RS. other REs in the unavailable sub-bands are not transmitted and are not taken into account in the measurement process. For example, the UE may not need to use R E should not be averaged.

[0168] For the new radio release 15, CSI-RS can be configured to be transmitted on a part of the DL BWP. Specifically, the BWP is divided into CSI-RS sub-bands (CSRS-SB) of consecutive PRBs, and the size of this CSRS-SB depends on the size of the BWP as shown in Table 9, and CSRS-SBs of various sizes can be introduced. For each BWP size, there are two possible CSRS-SB sizes, and the selected size can be configured by upper layer signaling.

[0169]

Table 9

[0170] The CSRS-SB can straddle the LBT sub-band boundary, for example, as shown in Figure 28. If one of the LBT sub-bands carrying the configured CSRS-SB to the UE, for example, SB3 in Figure 28, is unavailable, the UE can assume any of the following options.

[0171] In the first alternative, if any of the CSRS-SBs straddle two LBT sub-bands and one of them is unavailable, the UE can assume that there is no CSI-RS transmitted on this CSRS-SB. That is, skip the measurement on this CSRS-SB and make the report for this CSRS-SB unnecessary. This is illustrated in Figure 29, where all configured CSRS-SBs that are completely or partially outside the available sub-bands are excluded from the measurement and the report is made unnecessary. Further, the measured values are the UE's DL BWP. ​​​​​​​​​​​​When averaged across all sub-bands within, to avoid corruption of the average value, the UE may not include unavailable SBs in the averaging.

[0172] In another alternative, a configured CSRS-SB that spans two LBT sub-bands may not be completely omitted if any of those LBT sub-bands are unavailable. Instead, CSRS-SB PRBs that are fully or partially included in the unavailable LBT sub-band are omitted, and other PRBs within the same CSRS-SB may continue to carry CSI-RS and contribute to the measurement. This corresponds to shrinking the last CSRS-SB to contain fewer PRBs than other CSRS-SBs far from the sub-band boundary. For example, FIG. 30A shows that the CSRS-SB spanning SB2 and SB3 is partially omitted because SB3 is unavailable. In this case, CSI-RS may be transmitted only on the PRBs within SB2.

[0173] Furthermore, even if multiple consecutive LBT sub-bands are available, this specification proposes to limit the measurement to within the LBT sub-band. If a configured CSRS-SB spans two consecutive available sub-bands, this CSRS-SB is split into two CSRS-SBs, each fully contained in one LBT sub-band. If there is a PRB that crosses the boundary between any consecutive LBT sub-bands, this PRB may be omitted, and the UE may assume that there is no CSI-RS transmitted on this PRB. If there is a PRB that crosses the boundary between any consecutive LBT sub-bands, this PRB may be omitted, and the UE may assume that there is no CSI-RS transmitted on this PRB. FIG. 30B shows the CSRS-SB spanning (SB0, SB1) and (SB1, S Another example of a CSRS-SB spanning B2) is shown, and next, each of these CSRS-SB is split into two CSRS-SB, one for each available LBT sub-band each. If the UE is configured to report CSI for a CSRS-SB spanning two consecutive LBT sub-bands, i.e., the parent CSRS-SB, the CSI report can be assumed to be configured for the child CSRS-SB, i.e., the new CSRS-SB obtained by splitting the parent CSRS-SB each.

[0174] In new radio (NR)-based access to unlicensed spectrum, guard bands can be employed to avoid interference to adjacent channels. As a result, some CSRS-SB may completely or partially overlap with the guard band, as shown, for example, in Figure 31. If any of these CSRS-SB are configured such that the UE performs measurements on them, the UE can assume that, for example, CSI-RS RE is not transmitted on these CSRS-SB. In other words, the UE can omit these CSRS-SB from the configured measurements. Also, if the CSRS-SB is configured to carry CSI-RS RE in unavailable sub-bands, the UE can assume that it should not perform measurements on those CSRS-SB. -RS RE, the UE can assume that it should not perform measurements on those CSRS-SB.

[0175] Alternatively, if the CSRS-SB completely overlaps with the guard band, or if it spans an unavailable LBT sub-band and the guard band, i.e., if the CSRS-SB is at the boundary between an unavailable LBT sub-band and the guard band, the UE should not perform measurements on them ​​It can be assumed that it should not be implemented, and the entire CSRS-SB is omitted. However, for the CSRS-SB that spans the available LBT subbands and the guard bands, the UE can assume that the PRBs completely or partially included in the guard band may not carry CSI-RS, and it can be assumed that measurements on them are not performed and these measurements are not carried out. On the other hand, the UE can assume that the PRBs completely included in the available LBT subbands may carry CSI-RS and can perform measurements. FIG. 32 shows an example where the CSRS-SB completely overlaps or spans both the unavailable LBT subbands or the guard bands, and then the UE can omit them. On the other hand, for the CSRS-SB that spans the available subbands and the guard bands, the UE can assume that the PRBs within the available subbands carry CSI-RS and can assume that measurements can be performed on those PRBs. In other words, the UE can assume that the size of these CSRS-SBs is smaller than that of other CSRS-SBs that are separated from the guard bands.

[0176] The sizes of the first and last CSRS-SBs can be given as a function of the position of the LBT subbands, the size of the guard bands, the position of the BWP, etc. For example, the size of the first CSRS-SB located within the lowest-position available LBT subband j within the BWP can be given by Equation 2 below. However, Equation 3 below is for the size of the CSRS-SB, Equation 4 below is for the number of PRBs from the reference PRB to the first PRB within the BWP i and Equation 5 below is for the number of PRBs from the first PRB within the BWP to the i first available LBT subband jThe number of PRBs up to the first PRB within, and the following Equation 6 is the number of PRBs used as the guard band within the LBT sub-band j There is. FIG. 33 illustrates these terms. If no guard band PRBs are required, the following Equation 6 can be set to zero.

[0177]

Number

[0178]

Number

[0179]

Number

[0180]

Number

[0181]

Number

[0182] When the following Equation 7 holds, the size of the last CSR-SB located within the highest available LBT sub-band within the BWP k within can be given by the following Equation 8. However, M is , the number of consecutive available LBT sub-bands, the following Equation 9 is the size of the LBT sub-band expressed in PRBs , and the following Equation 10 is the number of PRBs used as the guard band within the LBT sub-band k used When the following Equation 11 holds, the highest available LBT sub-band within the BWP available k ​The size of the last CSR-SB located therein can be given by the following Equation 12 and can be given by the following Equation 12. When available LBT sub-bands have different sizes, the terms of the following Equation 13 can be replaced by the following Equation 14. However, the following Equation 15 is the size of the q-th available LBT sub-band.

[0183]

Number

[0184]

Number

[0185]

Number

[0186]

Number

[0187]

Number

[0188]

Number

[0189]

Number

[0190]

Number

[0191]

Number

[0192] In the case of discontinuous available LBT sub-bands, the available LBT sub-bands can be treated separately to apply the above example. By doing so, the above example can be applied.

[0193] In New Radio Release 15, CSI-RS can be configured to occupy multiple OFDM symbols within a slot. Due to the uncertainty of channel access, the gNB may not be able to access the channel at the configured time domain position. To address such issues, the following alternatives or any combination thereof can be adopted. In the first alternative, the UE can assume that the CSI-RS within the OFDM symbol belonging before the gNB successfully acquires the channel is skipped. In other words, the UE can consider that the OFDM symbol is punctured if the gNB fails to acquire the channel before the OFDM symbol carrying the CSI-RS. For example, Figure 3-4 shows an example of CSI-RS configured to be transmitted in OFDM symbols 3 and 9. In this example, the gNB acquires the channel in OFDM symbol 6. Therefore, the UE can consider that OFDM symbol 3 carrying the CSI-RS is punctured, but OFDM symbol 9 continues to carry the CSI-RS as originally configured. In other possible solutions, if any of the symbols carrying the CSI-RS is punctured, the UE can also consider that the other OFDM symbols carrying the CSI-RS, even within the gNB's COT To address such issues, the following alternatives or any combination thereof can be adopted.

[0194] In the first alternative, the UE can assume that the CSI-RS within the OFDM symbol belonging before the gNB successfully acquires the channel is skipped. In other words, the UE can consider that the OFDM symbol is punctured if the gNB fails to acquire the channel before the OFDM symbol carrying the CSI-RS. For example, if the gNB fails to acquire the channel before the OFDM symbol carrying the CSI-RS, the UE can consider that the OFDM symbol is punctured. For example, Figure 3-4 shows an example of CSI-RS configured to be transmitted in OFDM symbols 3 and 9. In this example, the gNB acquires the channel in OFDM symbol 6. Therefore, the UE can consider that OFDM symbol 3 carrying the CSI-RS is punctured, but OFDM symbol 9 continues to carry the CSI-RS as originally configured. For example, Figure 3-4 shows an example of CSI-RS configured to be transmitted in OFDM symbols 3 and 9. In this example, the gNB acquires the channel in OFDM symbol 6. Therefore, the UE can consider that OFDM symbol 3 carrying the CSI-RS is punctured, but OFDM symbol 9 continues to carry the CSI-RS as originally configured.

[0195] As another possible solution, if any of the symbols carrying the CSI-RS is punctured, the UE can also consider that the other OFDM symbols carrying the CSI-RS, even within the gNB's COT Even if it is included, it can be assumed that it will be punctured in the same way. A point to note is that in this specification , when proposing that the OFDM symbol carrying CSI-RS is punctured, this OFDM symbol may carry other DL transmissions. Only the REs configured to carry CSI-RS in this OFD M symbol are punctured. These REs can carry DL transmissions to this UE or any other UE. This solution is particularly interesting when CSI-RS is code division multiplexed (CDM) in the time domain. Alternatively, the UE can assume that the OFDM symbol carrying CSI-RS can be shifted. The shift value can be explicitly indicated to the UE, for example, by dynamic UE-specific DCI or group-common DCI . The UE-specific DCI can be scrambled by the C-RNTI, and the group-common DCI can be scrambled by an RNTI such as the Slot Format Indicator (SFI). The shift value can also be indicated by the MAC-CE. If the time shift of a previously received signal / channel, such as DMRS, PSS, SSS, Synchronization Signal Block (SSB), etc., can serve this purpose, the UE can be implicitly indicated by notifying the time shift. When the OFDM symbol carrying CSI-RS is shifted beyond the gNB MCOT, the UE can consider those OFDM symbols to be punctured. Figure 35 shows that CSI-RS is OFD

[0196] Configured to be transmitted with M symbols 3 and 9, an example is shown where the gNB fails to access the channel due to LBT impairment. Therefore, when the gNB acquires the channel, it may indicate a shift of 3 OFDM symbols, and the UE can assume that the CSI-RS that should be transmitted in OFDM symbols 3 and 9 is transmitted in OFDM symbols 6 and 12 respectively. Furthermore, it may be beneficial to remove the time-dependence in the initial sequence generator of the CSI-RS. For example, the initialization sequence can be given by Equation 16 below.

[0197]

[0198]

[0199]

Equation

[0200]

Equation

[0201]

Equation

[0201] However, Equation 17 above can be the relative slot number with respect to the start of the COT. When the gNB acquires the channel at the center of the slot, this partial slot can be counted as the first slot of the gNB's COT. The parameter l is the OFDM symbol number within the slot, and in the case of the first slot of the gNB's COT, l may not be less than the index of the first OFDM symbol of the gNB's COT. The parameters n and the above Equation 18 are, respectively, equal to the upper layer parameter within the slot and the number of OFDM symbols. ID ID and the above Equation 18 are, respectively, equal to the upper layer parameter within the slot and the number of OFDM symbols. Yes.

[0202] Alternatively, the above Equation 17 can be the slot number within the radio frame, and l can be the relative OFDM symbol number with respect to the start of the COT of the gNB. The other parameters of the equation remain unchanged.

[0203] In the new radio release 15, the CSRS-SBs to be reported can be configured by upper layer signaling carrying a bit map having a size equal to the number of CSRS-SBs within the BWP. In the above solution, if the size of the CSRS-SB is reduced because the CSRS-SB spans an available LBT subband and another unavailable LBT subband, the indication bits corresponding to the original CSRS-SB can be used to indicate the size of the changed CSRS-SB. Also, in the case of a parent CSRS-SB split into two child CSRS-SBs to span an available LBT subband, the same indication bits corresponding to the original CSRS-SB can be used to indicate both child CSRS-SBs.

[0204] The Third Generation Partnership Project (3GPP) develops technical specifications for cellular communication network technologies, including service capabilities including radio access, core transport networks, and efforts related to codecs, security, and quality of service. Recent radio access technology (RAT) specifications include Wideband Code Division Multiple Access: WCDMA (Registered Trademark) (commonly referred to as 3G), LTE (commonly referred to as 4G), and LTE-Advanced specifications. It includes grids. The 3rd Generation Partnership Project (3GPP) has started working on the standardization of the next-generation cellular technology, called New Radio (NR) and also known as "5G". The development of the 3GPP NR standard is expected to include the definition of a new radio access technology (new RAT), which is expected to include provisions for new flexible radio access below 6 GHz and new ultra-mobile broadband radio access above 6 GHz. Flexible radio access is expected to consist of new, non-backward-compatible radio access in new spectrum below 6 GHz and is expected to include different operating modes multiplexable within the same spectrum to address a wide range of 3GPP NR use cases with diverse requirements. Ultra-mobile broadband is expected to include centimeter-wave and millimeter-wave spectra that provide opportunities for ultra-mobile broadband access, for example, for indoor use and hotspots. In particular, ultra-mobile broadband is expected to share a common design framework with optimized designs specific to centimeter-wave and millimeter-wave with flexible radio access below 6 GHz. It is expected to include the definition of a new radio access technology (new RAT), which is expected to include provisions for new flexible radio access below 6 GHz and new ultra-mobile broadband radio access above 6 GHz. Flexible radio access is expected to consist of new, non-backward-compatible radio access in new spectrum below 6 GHz and is expected to include different operating modes multiplexable within the same spectrum to address a wide range of 3GPP NR use cases with diverse requirements. Ultra-mobile broadband is expected to include centimeter-wave and millimeter-wave spectra that provide opportunities for ultra-mobile broadband access, for example, for indoor use and hotspots. In particular, ultra-mobile broadband is expected to share a common design framework with optimized designs specific to centimeter-wave and millimeter-wave with flexible radio access below 6 GHz. It is expected to include the definition of a new radio access technology (new RAT), which is expected to include provisions for new flexible radio access below 6 GHz and new ultra-mobile broadband radio access above 6 GHz. Flexible radio access is expected to consist of new, non-backward-compatible radio access in new spectrum below 6 GHz and is expected to include different operating modes multiplexable within the same spectrum to address a wide range of 3GPP NR use cases with diverse requirements. Ultra-mobile broadband is expected to include centimeter-wave and millimeter-wave spectra that provide opportunities for ultra-mobile broadband access, for example, for indoor use and hotspots. In particular, ultra-mobile broadband is expected to share a common design framework with optimized designs specific to centimeter-wave and millimeter-wave with flexible radio access below 6 GHz. It is expected to include the definition of a new radio access technology (new RAT), which is expected to include provisions for new flexible radio access below 6 GHz and new ultra-mobile broadband radio access above 6 GHz. Flexible radio access is expected to consist of new, non-backward-compatible radio access in new spectrum below 6 GHz and is expected to include different operating modes multiplexable within the same spectrum to address a wide range of 3GPP NR use cases with diverse requirements. Ultra-mobile broadband is expected to include centimeter-wave and millimeter-wave spectra that provide opportunities for ultra-mobile broadband access, for example, for indoor use and hotspots.

[0205] In the 3rd Generation Partnership Project (3GPP), technical standards for cellular communication network technologies are developed, including radio access, core transport network, and service capabilities including efforts related to codec, security, and quality of service. Recent radio access technology (RAT) standards include Wideband Code Division Multiple Access (WCDMA) (commonly In the 3rd Generation Partnership Project (3GPP), technical standards for cellular communication network technologies are developed, including radio access, core transport network, and service capabilities including efforts related to codec, security, and quality of service. Recent radio access technology (RAT) standards include Wideband Code Division Multiple Access (WCDMA) (commonly known as 3G (commonly referred to as such), LTE (commonly referred to as 4G), and LTE-Advanced (LTE-A) standards are included. 3GPP has begun work on standardizing the next-generation cellular technology, called New Radio (NR) and also referred to as "5G". The development of the 3GPP NR standard is expected to include the definition of a next-generation radio access technology (new RAT), which is expected to include provisions for new flexible radio access below 6 GHz and new ultra-mobile broadband radio access above 6 GHz. Flexible radio access is expected to consist of new, non-backward-compatible radio access in new spectrum below 6 GHz and is expected to include different operating modes multiplexable within the same spectrum to address a wide range of 3GPP NR use cases with diverse requirements. Ultra-mobile broadband is expected to include centimeter and millimeter wave spectrum providing opportunities for ultra-mobile broadband access, for example, for indoor use and hotspots. In particular, ultra-mobile broadband is expected to share a common design framework with specific design optimizations for centimeter and millimeter waves with flexible radio access below 6 GHz. Advanced) standards. 3GPP has started working on standardizing the next-generation cellular technology called New Radio (NR), also known as "5G". The development of the 3GPP NR standard is expected to include the definition of a next-generation radio access technology (new RAT), which is expected to include provisions for new flexible radio access below 6 GHz and new ultra-mobile broadband radio access above 6 GHz. Flexible radio access is expected to consist of new, non-backward-compatible radio access in new spectrum below 6 GHz and is expected to include different operating modes multiplexable within the same spectrum to address a wide range of 3GPP NR use cases with diverse requirements. Ultra-mobile broadband is expected to include centimeter and millimeter wave spectrum providing opportunities for ultra-mobile broadband access, for example, for indoor use and hotspots. In particular, ultra-mobile broadband is expected to share a common design framework with specific design optimizations for centimeter and millimeter waves with flexible radio access below 6 GHz. 3GPP has identified the various use cases expected to be supported by NR and, as a result, has defined diverse user experience requirements for data transfer speed, latency, and mobility. The use cases include the following general categories: namely, enhanced mobile broadband (e.g., broadband access in dense areas, indoor ultra-high broadband access, broadband access in crowded places, 50 Mbps or more everywhere).

[0206] band access everywhere), massive machine type communication (e.g., for smart cities, industrial IoT, and connected vehicles), and ultra-reliable low-latency communication (e.g., for mission-critical applications such as autonomous driving and remote surgery).​​​​​​​​​​ Ultra-low-cost broadband access, in-vehicle mobile broadband), critical communications, massive machine type communications, network operation (e.g., network slicing, routing, migration and interworking, and energy saving -), and enhanced vehicle-to-everything (Enhanced Vehicle-to-Everything g:eV2X) communications. eV2X communications can include any of vehicle-to-vehicle (Vehicle-to-Vehicle:V 2V) communications, vehicle-to-infrastructure (Vehicle-to-Infrastructure:V2I ) communications, vehicle-to-network (Vehicle-to-Network:V2N) communications, vehicle-to pedestrian (Vehicle-to-Pedestrian:V2P) communications, and communications between a vehicle and other entities . Specific services and applications within these categories can include, for example, monitoring and sensor networks, device remote control, two-way remote control, personal cloud computing, video streaming , wireless cloud-based office, connectivity to first responders, automotive eCall, disaster alerts, real-time gaming, multi-party video calls, autonomous driving, augmented reality , touch internet, virtual reality, etc. This specification contemplates all of these use cases and others.

[0207] FIG. 27A shows an embodiment of an exemplary communication system 100 that can embody the methods and apparatuses described and claimed herein. As shown, an example of the communication system 100 is Among wireless transmit / receive units (Wireless Transmit / Receive Unit: WTRU) 102a, 102b, 102c, 102d, 102e, 102f, and 102g, at least one (which may generally or collectively also be referred to as WTRU 102), a radio access network (RAN) 103 / 104 / 105 / 103b / 104b / 105b, a core network 106 / 107 / 109, a public switched telephone network (PSTN) 108, the Internet 110, other networks 112, and a V2X server (or proximity-based services (ProSe) function and server) 113 may be included, but it is understood that the disclosed embodiments envision any number of WTRUs, base stations, networks, and network elements. Each of WTRUs 102a, 102b, 102c, 102d, 102e, 102f, 102g may be any type of device or apparatus configured to operate and communicate in a wireless environment. Each of WTRUs 102a, 102b, 102c, 102d, 102e, 102f, 102g is illustrated in FIGS. 1A - 1E as a handheld wireless communication device, but envisioning diverse use cases for 5G wireless communication, each of the WTRUs may, by way of example, be a user equipment (UE), a mobile station, a fixed or mobile subscriber unit, a wireless calling device, a cellular phone, a personal digital assistant (PDA), a smartphone, a laptop, a tablet, a netbook, a notebook computer, a personal computer, a wireless sensor, a home appliance, a smartwatch or smart Each of WTRUs 102a, 102b, 102c, 102d, 102e, 102f, 102g is illustrated in FIGS. 1A - 1E as a handheld wireless communication device, but envisioning diverse use cases for 5G wireless communication, each of the WTRUs may, by way of example, be a user equipment (UE), a mobile station, a fixed or mobile subscriber unit, a wireless calling device, a cellular phone, a personal digital assistant (PDA), a smartphone, a laptop, a tablet, a netbook, a notebook computer, a personal computer, a wireless sensor, a home appliance, a smartwatch or smart phone, etc. phone, etc. Wearable devices such as clothing, medical equipment, eHealth devices, robots This includes vehicles, industrial equipment, drones, and transportation equipment such as cars, trucks, trains, and aircraft. includes any apparatus or device configured to transmit or receive radio signals; or , it is understood that the present invention may be embodied therein.

[0208] The communications system 100 may further include a base station 114a and a base station 114b. The base station 114a may be connected to at least one of the WTRUs 102a, 102b, and 102c. It interfaces wirelessly with the core network 106 / 107 / 109 and the Internet Access to one or more communications networks, such as network 110 or other networks 112 The base station 114b may be any type of device configured to facilitate access to the , Remote Radio Heads (RRH) 118a, 118b, transmitting and receiving points Transmission and Reception Point (TRP) 119a, 119b, and roadside At least one of the Roadside Units (RSUs) 120a and 120b is connected to the network via a wired or wireless connection. 106 / 107 / 109 and Internet 1 10 and other networks 112 and V2X servers (or ProSe functions and servers 113, configured to facilitate access to one or more communications networks, such as The RRHs 118a, 118b may be any type of device. At least one wireless interface with the core network 106 / 107 / 109 One or more communications networks, such as the Internet 110 or other networks 112 It can be any type of device configured to facilitate access to the cell. TRP 119a and 119b wirelessly interface with at least one of the WTRUs 102d to facilitate access to one or more communication networks such as the core network 106 / 107 / 109, the Internet 110, and other networks 112. RSU 120a and 120b wirelessly interface with at least one of the WTRUs 102e and 102f to facilitate access to one or more communication networks such as the core network 106 / 107 / 109, the Internet 110, other networks 112, and the V2X server ( or ProSe function and server) 113. As an example, base stations 114a and 114b can be a Base Transceiver Station (BTS), Node B, eNode B, Home Node B, Home eNode B, a site controller, an Access Point (AP), a wireless router, etc. Base stations 114a and 114b are each shown as a single element, but it will be understood that base stations 114a and 114b can include any number of interconnected base stations and network elements Base station 114a may be part of the RAN 103 / 104 / 105, and the RAN 103 / 104 / 105 may also include a Base Station Controller (BSC), a Radio Network Controller (RNC), a relay node, etc. Although base stations 114a and 114b are each shown as a single element, it will be understood that base stations 114a and 114b can include any number of interconnected base stations and network elements It will be understood that base stations 114a and 114b can include any number of interconnected base stations and network elements It will be understood that base stations 114a and 114b can include any number of interconnected base stations and network elements

[0209] Base station 114a may be part of the RAN 103 / 104 / 105, and the RAN 103 / 104 / 105 may also include a Base Station Controller (BSC), a Radio Network Controller (RNC), a relay node, etc. It may also include other base stations such as Node B and network elements (not shown). The base station 114b may be a part of RAN103b / 104b / 105b, and RAN103b / 104b / 105b may also include other base stations and network elements (not shown) such as a base station controller (BSC), a radio network controller ( RNC), a relay node, etc. The base station 114a may be configured to transmit and receive radio signals within a specific geographical area sometimes referred to as a cell (not shown). The base station 114b may be configured to transmit and receive wired and radio signals within a specific geographical area sometimes referred to as a cell (not shown). A cell can be further divided into cell sectors. For example, the cell associated with the base station 114a can be divided into three sectors. In one embodiment, the base station 114a can include, for example, three transceivers, one for each sector of the cell. In one embodiment, the base station 114a can employ multiple-input multiple-output (MIMO) technology, and thus can utilize multiple transceivers per sector of the cell.

[0210] The base station 114a may communicate with one or more of the WTRUs 102a, 102b, 102c via the air interfaces 115 / 116 / 117, and the air interfaces 115 / 116 / 117 may be any suitable wireless communication link (e.g., radio frequency (RF), microwave, infrared (IR), ultraviolet ( UV), visible light, centimeter wave, millimeter wave, etc.). The air interface 11 5 / 116 / 117 can be constructed using any suitable radio access technology (RAT). It is possible.

[0211] Base station 114b may communicate with one or more of RRH118a, 118b, TRP119a, 119b, RSU1 20a, 120b, and via a wired or air interface 115b / 116 b / 117b. The wired or air interface 115b / 11 6b / 117b may be any suitable wired (e.g., cable, optical fiber, etc.) or wireless communication link (e.g., radio frequency (RF), microwave, infrared (IR), ultraviolet (UV ), visible light, centimeter wave, millimeter wave, etc.). The air interface 115b / 116b / 117b can be constructed using any suitable radio access technology (RAT). It is possible.

[0212] RRH118a, 118b, TRP119a, 119b, RSU120a, 120b may communicate with one or more of WTRU102c, 102d, 102e, 102f via an air interface 115c / 116c / 117c. The air interface 1 15c / 116c / 117c may be any suitable wireless communication link (e.g., radio frequency (R F), microwave, infrared (IR), ultraviolet (UV), visible light, centimeter wave, millimeter wave, etc.) . The air interface 115c / 116c / 117c can be constructed using any suitable radio access technology (RAT).

[0213] WTRU102a, 102b, 102c, 102d, 102e, 102f, and 10 2g at least in part is an air interface 115d / 116d / 117d (not shown They can communicate with each other via ( ). Air interfaces 115d / 116d / 117 d can be any suitable wireless communication link (e.g., radio frequency (RF), microwave, infrared (IR), ultraviolet (UV), visible light, centimeter wave, millimeter wave, etc.). The air interface 115d / 116d / 117d can be constructed using any suitable radio access technology (RAT).

[0214] More specifically, as described above, the communication system 100 may be a multi - access system and, for example, can adopt one or more channel access methods such as Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal Frequency Division Multiple Access (OFDMA), Single Carrier Frequency Division Multiple Access (SC - FDMA), etc. For example, the base station 114a in RAN 103 / 104 / 105 and WTRU102a, 102b, 102c, or the RRH118a, 118b, TRP11 9a, 119b, RSU120a, 120b in RAN103b / 104b / 105b and WTRU102c, 102d, 102e, 102f are Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access (UTRA) or Long Term Evolution (LTE) or LTE - Advanced (LTE - A) or New Radio (NR) air interfaces using one or more of the above - mentioned channel access methods. For example, the base station 114a in RAN 103 / 104 / 105 and WTRU102a, 102b, 102c, or the RRH118a, 118b, TRP11 9a, 119b, RSU120a, 120b in RAN103b / 104b / 105b and WTRU102c, 102d, 102e, 102f are Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access (UTRA)​ Wireless technologies such as may be implemented, and by that technology, wideband CDMA (WCDMA) can be used to construct air interfaces 115 / 116 / 117 or 115c / 116c / 117 c respectively. WCDMA can include communication protocols such as High-Speed Packet Access: HSPA and evolved HSPA (HSPA+). HSPA can include High-Speed Downlink Pa cket Access: HSDPA and High-Speed Uplink Packet Access: HSUPA.

[0215] In one embodiment, base station 114a and WTRUs 102a, 102b, 102c, or RRHs 118a, 118b within RANs 103b / 104b / 105b, and TRPs 11 9a, 119b, and RSUs 120a, 120b and WTRUs 102c, 102d may implement wireless technologies such as evolved UMTS terrestrial radio access (E-UTRA), and by that technology, air interfaces 115 / 116 / 117 or 115c / 116c / 1 17c using Long-Term Evolution (LTE) or LTE-Advanced (LTE-A ) may be constructed respectively. In the future, air interfaces 115 / 116 / 11 7 may implement 3GPP NR technology. LTE and LTE-A technologies include interfaces with LTE Device-to-Device (D2D) and V2X technologies (such as sidelink communication). 3GPP NR technology includes interfaces with NR V2X technologies (such as sidelink communication).

[0216] In one embodiment, the base station 114a within RAN103 / 104 / 105 and the WTRU 102a, 102b, 102c, or the RRH within RAN103b / 104b / 105b 118a, 118b, TRP119a, 119b, RSU120a, 120b and the WTRU 102c, 102d, 102e, 102f may implement wireless technologies such as IEEE 802.16 (e.g., Worldwide Interoperability for Microwave Access: WiMAX), CDMA2000, C DMA2000 1X, CDMA2000 Evolution-Data Optimize d: EV-DO), Interim Standard: IS) 2000 (IS-2000), Interim Standard 95 (IS-95), Interim Standard 856 (IS-856), Global System for Mobile Communications: GSM (registered trademark)), GSM Enhanced Data Rates for GSM Evolution: ED GE, GSM EDGE (GSM EDGE Radio Access Network: GERAN), etc.

[0217] The base station 114c in FIG. 27A may be, for example, a wireless router, a home node B, a home e-node B, or an access point, and may utilize any suitable RAT for facilitating wireless connectivity in a local area such as an office, a home, a vehicle, a campus, etc. In one implementation ​In one configuration, the base station 114c and the WTRU 102e may implement a wireless technology such as IEEE 802.11 to establish a Wireless Local Area Network (WLAN). In one embodiment, the base station 114c and the WTRU 102d may implement a wireless technology such as IEEE 802.15 to establish a Wireless Personal Area Network (WPAN). In yet another embodiment, the base station 114c and the WTRU 102e may utilize a cellular-based RAT (e.g., WCDMA, CDMA2000, GSM, LTE, LTE-A, etc.) to establish a pico cell or a femto cell. As shown in FIG. 27A, the base station 114b may be directly connected to the Internet 110. Thus, the base station 114c does not need to access the Internet 110 via the core network 106 / 107 / 109. RANs 103 / 104 / 105 and RANs 103b / 104b / 105b are capable of communicating with the core network 106 / 107 / 109, which may be any type of network configured to provide services such as voice, data, applications, Voice Over Internet Protocol (VoIP), etc. to one or more of WTRU 102a, 102b, 102c, 102d. For example, the core network 106 / 107 / 109 may be configured to provide call control, billing services, mobile location information services, prepaid calling, Internet access, etc. In one configuration, the base station 114c and the WTRU 102e may implement a wireless technology such as IEEE 802.11 to establish a Wireless Local Area Network (WLAN). In one embodiment, the base station 114c and the WTRU 102d may implement a wireless technology such as IEEE 802.15 to establish a Wireless Personal Area Network (WPAN). In yet another embodiment, the base station 114c and the WTRU 102e may utilize a cellular-based RAT (e.g., WCDMA, CDMA2000, GSM, LTE, LTE-A, etc.) to establish a pico cell or a femto cell. As shown in FIG. 27A, the base station 114b may be directly connected to the Internet 110. Thus, the base station 114c does not need to access the Internet 110 via the core network 106 / 107 / 109. RANs 103 / 104 / 105 and RANs 103b / 104b / 105b are capable of communicating with the core network 106 / 107 / 109, which may be any type of network configured to provide services such as voice, data, applications, Voice Over Internet Protocol (VoIP), etc. to one or more of WTRU 102a, 102b, 102c, 102d. For example, the core network 106 / 107 / 109 may be configured to provide call control, billing services, mobile location information services, prepaid calling, Internet access, etc. In one configuration, the base station 114c and the WTRU 102e may implement a wireless technology such as IEEE 802.11 to establish a Wireless Local Area Network (WLAN). In one embodiment, the base station 114c and the WTRU 102d may implement a wireless technology such as IEEE 802.15 to establish a Wireless Personal Area Network (WPAN). In yet another embodiment, the base station 114c and the WTRU 102e may utilize a cellular-based RAT (e.g., WCDMA, CDMA2000, GSM, LTE, LTE-A, etc.) to establish a pico cell or a femto cell. As shown in FIG. 27A, the base station 114b may be directly connected to the Internet 110. Thus, the base station 114c does not need to access the Internet 110 via the core network 106 / 107 / 109. RANs 103 / 104 / 105 and RANs 103b / 104b / 105b are capable of communicating with the core network 106 / 107 / 109, which may be any type of network configured to provide services such as voice, data, applications, Voice Over Internet Protocol (VoIP), etc. to one or more of WTRU 102a, 102b, 102c, 102d. For example, the core network 106 / 107 / 109 may be configured to provide call control, billing services, mobile location information services, prepaid calling, Internet access, etc. In one configuration, the base station 114c and the WTRU 102e may implement a wireless technology such as IEEE 802.11 to establish a Wireless Local Area Network (WLAN). In one embodiment, the base station 114c and the WTRU 102d may implement a wireless technology such as IEEE 802.15 to establish a Wireless Personal Area Network (WPAN). In yet another embodiment, the base station 114c and the WTRU 102e may utilize a cellular-based RAT (e.g., WCDMA, CDMA2000, GSM, LTE, LTE-A, etc.) to establish a pico cell or a femto cell. As shown in FIG. 27A, the base station 114b may be directly connected to the Internet 110. Thus, the base station 114c does not need to access the Internet 110 via the core network 106 / 107 / 109. RANs 103 / 104 / 105 and RANs 103b / 104b / 105b are capable of communicating with the core network 106 / 107 / 109, which may be any type of network configured to provide services such as voice, data, applications, Voice Over Internet Protocol (VoIP), etc. to one or more of WTRU 102a, 102b, 102c, 102d. For example, the core network 106 / 107 / 109 may be configured to provide call control, billing services, mobile location information services, prepaid calling, Internet access, etc. In one configuration, the base station 114c and the WTRU 102e may implement a wireless technology such as IEEE 802.11 to establish a Wireless Local Area Network (WLAN). In one embodiment, the base station 114c and the WTRU 102d may implement a wireless technology such as IEEE 802.15 to establish a Wireless Personal Area Network (WPAN). In yet another embodiment, the base station 114c and the WTRU 102e may utilize a cellular-based RAT (e.g., WCDMA, CDMA2000, GSM, LTE, LTE-A, etc.) to establish a pico cell or a femto cell. As shown in FIG. 27A, the base station 114b may be directly connected to the Internet 110. Thus, the base station 114c does not need to access the Internet 110 via the core network 106 / 107 / 109. RANs 103 / 104 / 105 and RANs 103b / 104b / 105b are capable of communicating with the core network 106 / 107 / 109, which may be any type of network configured to provide services such as voice, data, applications, Voice Over Internet Protocol (VoIP), etc. to one or more of WTRU 102a, 102b, 102c, 102d. For example, the core network 106 / 107 / 109 may be configured to provide call control, billing services, mobile location information services, prepaid calling, Internet access, etc. In one configuration, the base station 114c and the WTRU 102e may implement a wireless technology such as IEEE 802.11 to establish a Wireless Local Area Network (WLAN). In one embodiment, the base station 114c and the WTRU 102d may implement a wireless technology such as IEEE 802.15 to establish a Wireless Personal Area Network (WPAN). In yet another embodiment, the base station 114c and the WTRU 102e may utilize a cellular-based RAT (e.g., WCDMA, CDMA2000, GSM, LTE, LTE-A, etc.) to establish a pico cell or a femto cell. As shown in FIG. 27A, the base station 114b may be directly connected to the Internet 110. Thus, the base station 114c does not need to access the Internet 110 via the core network 106 / 107 / 109.

[0218] RANs 103 / 104 / 105 and RANs 103b / 104b / 105b are capable of communicating with the core network 106 / 107 / 109, which may be any type of network configured to provide services such as voice, data, applications, Voice Over Internet Protocol (VoIP), etc. to one or more of WTRU 102a, 102b, 102c, 102d. For example, the core network 106 / 107 / 109 may be configured to provide call control, billing services, mobile location information services, prepaid calling, Internet access, etc. RANs 103 / 104 / 105 and RANs 103b / 104b / 105b are capable of communicating with the core network 106 / 107 / 109, which may be any type of network configured to provide services such as voice, data, applications, Voice Over Internet Protocol (VoIP), etc. to one or more of WTRU 102a, 102b, 102c, 102d. For example, the core network 106 / 107 / 109 may be configured to provide call control, billing services, mobile location information services, prepaid calling, Internet access, etc. RANs 103 / 104 / 105 and RANs 103b / 104b / 105b are capable of communicating with the core network 106 / 107 / 109, which may be any type of network configured to provide services such as voice, data, applications, Voice Over Internet Protocol (VoIP), etc. to one or more of WTRU 102a, 102b, 102c, 102d. For example, the core network 106 / 107 / 109 may be configured to provide call control, billing services, mobile location information services, prepaid calling, Internet access, etc. RANs 103 / 104 / 105 and RANs 103b / 104b / 105b are capable of communicating with the core network 106 / 107 / 109, which may be any type of network configured to provide services such as voice, data, applications, Voice Over Internet Protocol (VoIP), etc. to one or more of WTRU 102a, 102b, 102c, 102d. For example, the core network 106 / 107 / 109 may be configured to provide call control, billing services, mobile location information services, prepaid calling, Internet access, etc. RANs 103 / 104 / 105 and RANs 103b / 104b / 105b are capable of communicating with the core network 106 / 107 / 109, which may be any type of network configured to provide services such as voice, data, applications, Voice Over Internet Protocol (VoIP), etc. to one or more of WTRU 102a, 102b, 102c, 102d. For example, the core network 106 / 107 / 109 may be configured to provide call control, billing services, mobile location information services, prepaid calling, Internet access, etc. RANs 103 / 104 / 105 and RANs 103b / 104b / 105b are capable of communicating with the core network 106 / 107 / 109, which may be any type of network configured to provide services such as voice, data, applications, Voice Over Internet Protocol (VoIP), etc. to one or more of WTRU 102a, 102b, 102c, 102d. For example, the core network 106 / 107 / 109 may be configured to provide call control, billing services, mobile location information services, prepaid calling, Internet access, etc. RANs 103 / 104 / 105 and RANs 103b / 104b / 105b are capable of communicating with the core network 106 / 107 / 109, which may be any type of network configured to provide services such as voice, data, applications, Voice Over Internet Protocol (VoIP), etc. to one or more of WTRU 102a, 102b, 102c, 102d. For example, the core network 106 / 107 / 109 may be configured to provide call control, billing services, mobile location information services, prepaid calling, Internet access, etc. It can provide services such as continuity and video distribution, or execute advanced security functions such as user authentication. to do.

[0219] Although not shown in FIG. 27A, RAN103 / 104 / 105, RAN103b / 104 b / 105b, and core networks 106 / 107 / 109 can communicate directly or indirectly with other RANs using the same RAT or a different RAT as RAN103 / 104 / 1 05 or RAN103b / 104b / 105b. It will be understood that. For example, core networks 106 / 107 / 109 can be connected to RANs 103 / 104 / 105 and RAN103b / 104b / 105b that utilize E-UTRA radio technology only, and can also communicate with another RAN (not shown) that employs GSM radio technology. .

[0220] Core networks 106 / 107 / 109 can also function as gateways for WTRU102a, 102b, 102c , 102d, 102e to access PSTN108, Internet 110, or other networks 112. PSTN108 can include a circuit-switched telephone network that provides Plain Old Telephone Service (POTS). Internet 110 uses common communication protocols such as Transmission Control Protocol (TCP), User Datagram Protocol (UDP), and Internet Protocol (IP) within the TCP / IP Internet protocol suite for interconnected networks. to use. It may include a global system of computers networks and devices. The network 112 can include a wired or wireless communication network owned and operated by other service providers For example, network 112 can include another core network connected to one or more RANs that may use the same RAT or different RATs as RAN103 / 104 / 105 or RAN103b / 104b / 105b.

[0221] Some or all of the WTRUs 102a, 102b, 102c, 102d in the communication system 100 may have multi-mode capabilities. For example, WTRUs 102a, 102b, 10 2c, 102d, and 102e may have multiple transceivers for communicating with different wireless networks via different wireless links. For example, the WTRU10 shown in FIG. 27A may be configured to communicate with a base station 114a that can employ cellular-based wireless technology and a base station 114c that can employ IEEE 80 2 wireless technology. 2e

[0222] FIG. 27B is a block diagram of an example of a device or apparatus, such as a WTRU102, configured for wireless communication according to an embodiment shown herein. As shown in FIG. 27B, the exemplary WTRU102 can include a processor 118, a transceiver 120, a transmit / receive element 1 22, a speaker / microphone 124, a keypad 126, a display / touch pad / indicator 128, a non-removable memory 130, a removable memory 132, a power supply 134, a Global Positioning System (GPS) chipset 136, and other peripheral devices 138. . While maintaining consistency with one embodiment, the WTRU 102 can include any sub-combination of the above-described elements, which will be understood. Also, in each embodiment, it is understood that the base stations 114a, 114b and the nodes that the base stations 114a, 114b can represent (especially , for example, transceiver base stations (BTS), Node B, site controllers, access points (AP), home Node B, evolved home Node B (eNodeB), home evolved Node B (HeNB), home evolved Node B gateway, and proxy nodes, etc., but not limited to these) can be assumed to include some or all of the elements shown in FIG. 27B and described herein.

[0223] The processor 118 can be a general-purpose processor, a dedicated processor, a conventional processor, a digital signal processor (DSP), a plurality of microprocessors, one or more microprocessors associated with the DSP core, a controller, a microcontroller, an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) circuit, any other type of integrated circuit (IC), a state machine, etc. The processor 118 can perform signal encoding, data processing, power control, input / output processing, and any other functions that enable the operation of the WTRU 102 in a wireless environment. The processor 118 may be connected to the transceiver 120. ​ , the transceiver 120 may be connected to the transceiver element 122. FIG. 27B shows the processor 1 18 and the transceiver 120 as separate components, but it is understood that the processor 118 and the transceiver 120 may be integrated into one electronic package or chip will be.

[0224] The transceiver element 122 may be configured to transmit and receive signals with a base station ( e.g., base station 114a) via the air interface 115 / 116 / 117. For example, in one embodiment state, the transceiver element 122 may be an antenna configured to transmit and receive RF signals . In one embodiment, the transceiver element 122 may be, for example, an emitter / detector configured to transmit and receive IR, UV, or visible light signals . Further In one embodiment, the transceiver element 122 may be configured to transmit and receive both RF and optical signals . It will be understood that the transceiver element 122 may be configured to transmit and receive any combination of wireless signals .

[0225] Furthermore, in FIG. 27B, the transceiver element 122 is shown as a single element, but the WTR U102 may include any number of transceiver elements 122. More specifically, the WTRU10 2 may employ MIMO technology. Thus, in one embodiment, the WTRU10 2 may include two or more transceiver elements 122 (e.g., multiple antennas) for transmitting and receiving wireless signals via the air interface 115 / 116 / 117 .

[0226] The transceiver 120 modulates the signals transmitted by the transceiver element 122, and the transceiver element 122 It may be configured to demodulate the received signal. As described above, the WTRU 102 may have multi-mode capabilities. Thus, the transceiver 120 may include a plurality of transceivers so that the WTRU 102 can communicate via a plurality of RATs such as, for example, UTRA or IEEE 802.11. The processor 118 of the WTRU 102 is connected to and can receive user input data from a speaker / microphone 124, a keypad 126, and a display / touch pad / indicator 128 (e.g., a liquid crystal display (LCD) display unit or an organic light-emitting diode (OLED) display unit). The processor 118 can also output user data to the speaker / microphone 124, the keypad 126, and the display / touch pad / indicator 128. Further, the processor 118 can access information from and store data in any suitable type of memory, such as non-removable memory 130 and removable memory 132. The non-removable memory 130 may include random-access memory (RAM), read-only memory (ROM), a hard disk, or any other type of storage device. The removable memory 132 may include a subscriber identity module (SIM) card, a memory stick, a secure digital (SD) memory card, etc. In one embodiment, the processor 118 may be connected to, for example, a server or a home UTRA or IEEE 802.11 and other multiple RATs for communication, so it can include multiple transceivers.

[0227] The processor 118 of the WTRU 102 is connected to and can receive user input data from a speaker / microphone 124, a keypad 126, and a display / touch pad / indicator 128 (e.g., a liquid crystal display (LCD) display unit or an organic light-emitting diode (OLED) display unit). The processor 118 can also output user data to the speaker / microphone 124, the keypad 126, and the display / touch pad / indicator 128. Further, the processor 118 can access information from and store data in any suitable type of memory, such as non-removable memory 130 and removable memory 132. The non-removable memory 130 may include random-access memory (RAM), read-only memory (ROM), a hard disk, or any other type of storage device. The removable memory 132 may include a subscriber identity module (SIM) card, a memory stick, a secure digital (SD) memory card, etc. In one embodiment, the processor 118 may be connected to, for example, a server or a home The processor 118 of the WTRU 102 is connected to and can receive user input data from a speaker / microphone 124, a keypad 126, and a display / touch pad / indicator 128 (e.g., a liquid crystal display (LCD) display unit or an organic light-emitting diode (OLED) display unit). The processor 118 can also output user data to the speaker / microphone 124, the keypad 126, and the display / touch pad / indicator 128. Further, the processor 118 can access information from and store data in any suitable type of memory, such as non-removable memory 130 and removable memory 132. The non-removable memory 130 may include random-access memory (RAM), read-only memory (ROM), a hard disk, or any other type of storage device. The removable memory 132 may include a subscriber identity module (SIM) card, a memory stick, a secure digital (SD) memory card, etc. In one embodiment, the processor 118 may be connected to, for example, a server or a home (Liquid Crystal Display:LCD) display unit or an organic light-emitting diode (Organi c Light-Emitting Diode:OLED) display unit) and can receive user input data therefrom. The processor 118 can also output user data to the speaker / microphone 124, the keypad 126, and the display / touch pad / indicator 128. Further, the processor 118 can access information from and store data in any suitable type of memory, such as non-removable memory 130 and removable memory 132. The non-removable memory 130 may include random-access memory (RAM), read-only memory (ROM), a hard disk, or any other type of storage device. The removable memory 132 may include a subscriber identity module (SIM) card, a memory stick, a secure digital (SD) memory card, etc. In one embodiment, the processor 118 may be connected to, for example, a server or a home The processor 118 can receive user input data from a speaker / microphone 124, a keypad 126, and a display / touch pad / indicator 128 (e.g., a liquid crystal display (LCD) display unit or an organic light-emitting diode (OLED) display unit). The processor 118 can also output user data to the speaker / microphone 124, the keypad 126, and the display / touch pad / indicator 128. Further, the processor 118 can access information from and store data in any suitable type of memory, such as non-removable memory 130 and removable memory 132. The non-removable memory 130 may include random-access memory (RAM), read-only memory (ROM), a hard disk, or any other type of storage device. The removable memory 132 may include a subscriber identity module (SIM) card, a memory stick, a secure digital (SD) memory card, etc. In one embodiment, the processor 118 may be connected to, for example, a server or a home The processor 118 of the WTRU 102 is connected to and can receive user input data from a speaker / microphone 124, a keypad 126, and a display / touch pad / indicator 128 (e.g., a liquid crystal display (LCD) display unit or an organic light-emitting diode (OLED) display unit). The processor 118 can also output user data to the speaker / microphone 124, the keypad 126, and the display / touch pad / indicator 128. Further, the processor 118 can access information from and store data in any suitable type of memory, such as non-removable memory 130 and removable memory 132. The non-removable memory 130 may include random-access memory (RAM), read-only memory (ROM), a hard disk, or any other type of storage device. The removable memory 132 may include a subscriber identity module (SIM) card, a memory stick, a secure digital (SD) memory card, etc. In one embodiment, the processor 118 may be connected to, for example, a server or a home The processor 118 of the WTRU 102 is connected to and can receive user input data from a speaker / microphone 124, a keypad 126, and a display / touch pad / indicator 128 (e.g., a liquid crystal display (LCD) display unit or an organic light-emitting diode (OLED) display unit). The processor 118 can also output user data to the speaker / microphone 124, the keypad 126, and the display / touch pad / indicator 128. Further, the processor 118 can access information from and store data in any suitable type of memory, such as non-removable memory 130 and removable memory 132. The non-removable memory 130 may include random-access memory (RAM), read-only memory (ROM), a hard disk, or any other type of storage device. The removable memory 132 may include a subscriber identity module (SIM) card, a memory stick, a secure digital (SD) memory card, etc. In one embodiment, the processor 118 may be connected to, for example, a server or a home The processor 118 can access information from and store data in any suitable type of memory, such as non-removable memory 130 and removable memory 132. The non-removable memory 130 may include random-access memory (RAM), read-only memory (ROM), a hard disk, or any other type of storage device. The removable memory 132 may include a subscriber identity module (SIM) card, a memory stick, a secure digital (SD) memory card, etc. In one embodiment, the processor 118 may be connected to, for example, a server or a home The processor 118 can access information from and store data in any suitable type of memory, such as non-removable memory 130 and removable memory 132. The non-removable memory 130 may include random-access memory (RAM), read-only memory (ROM), a hard disk, or any other type of storage device. The removable memory 132 may include a subscriber identity module (SIM) card, a memory stick, a secure digital (SD) memory card, etc. In one embodiment, the processor 118 may be connected to, for example, a server or a home The non-removable memory 130 may include random-access memory (RAM), read-only memory (ROM), a hard disk, or any other type of storage device. The removable memory 132 may include a subscriber identity module (SIM) card, a memory stick, a secure digital (SD) memory card, etc. In one embodiment, the processor 118 may be connected to, for example, a server or a home :ROM), a hard disk, or any other type of storage device. The removable memory 132 may include a subscriber identity module (SIM) card, a memory stick, a secure digital (SD) memory card, etc. In one embodiment, the processor 118 may be connected to, for example, a server or a home The removable memory 132 may include a subscriber identity module (SIM) card, a memory stick, a secure digital (SD) memory card, etc. In one embodiment, the processor 118 may be connected to, for example, a server or a home The removable memory 132 may include a subscriber identity module (SIM) card, a memory stick, a secure digital (SD) memory card, etc. In one embodiment, the processor 118 may be connected to, for example, a server or a home In one embodiment, the processor 118 may be connected to, for example, a server or a home from a memory not physically located on the WTRU 102 but on a game computer (not shown). Information may be accessed and data may be stored therein.

[0228] The processor 118 may receive power from the power supply 134 and may be configured to distribute or control power to other components within the WTRU 102. The power supply 134 may be any suitable device for supplying power to the WTRU 102. For example, the power supply 134 may include one or more dry cells, solar cells, fuel cells, and the like.

[0229] The processor 118 may also be connected to a GPS chipset 136 configured to provide location information (e.g., longitude and latitude) regarding the current location of the WTRU 102. The WTRU 102 may receive location information from the GPS chipset 136 in addition to, or instead of, receiving location information from a base station (e.g., base stations 114a, 114b) via the air interface 115 / 116 / 117, or may determine its location based on the timing of signals received from two or more neighboring base stations. It will be understood that the WTRU 102 may obtain location information by any suitable positioning method while maintaining consistency with one embodiment.

[0230] The processor 118 may further be connected to other peripheral devices 138, which may include one or more software or hardware modules that provide additional features, functionality, and wired or wireless connectivity. For example, the peripheral devices 138 may include various sensors such as an accelerometer and a biometric (e.g., fingerprint) sensor, an electronic compass (e-Comp ​​​​​​​ ass), satellite transceiver, digital camera (for photos or videos), Universal Serial Albus (Universal Serial Bus: USB) port or other interconnection interface ace, vibration device, television transceiver, hands-free headset, blue Tooth (Bluetooth (registered trademark)) module, Frequency Modulated (FM) FM) radio unit, digital music player, media player, video game player module, Internet browser, etc. can be included.

[0231] WTRU102 can be embodied in other devices such as sensors, household appliances, wearable devices such as smart watches and smart closures, medical devices and eHealth devices, robots, industrial equipment, drones, transportation equipment such as passenger cars, trucks, trains, airplanes, etc. WTRU102 can be connected to such devices or other components, modules, or systems of the device via one or more interconnection interfaces such as an interconnection interface including one of the peripheral devices 138. equipment, drones, transportation equipment such as passenger cars, trucks, trains, airplanes, etc. It may also be embodied in the device. WTRU102 may include one of the peripheral devices 138 in such other components, modules, or systems of the device and be connected via one or more interconnection interfaces such as an interconnection interface. It may include one of the peripheral devices 138 in such other components, modules, or systems of the device and be connected via one or more interconnection interfaces such as an interconnection interface. It may be connected via one or more interconnection interfaces such as an interconnection interface including one of the peripheral devices 138. It may be connected.

[0232] Figure 27C is a system diagram of RAN103 and core network 106 according to one embodiment. As described above, RAN103 can communicate with WTRU102a, 102b, 102c via air interface 115 by adopting UTRA radio technology. It can communicate with WTRU102a, 102b, 102c via air interface 115 by adopting UTRA radio technology. RAN103 can also communicate with core network 106. As shown in Figure 27C, RAN103 can include Node B140a, 140b, 140c, and the node B140a, 140b, and 140c each include one or more transceivers for communicating with WTRU102a, 102b, and 102c via an air interface 115. Nodes B140a, 140b, and 140c may each be associated with a specific cell (not shown) within RAN103. RAN103 may further include RNCs 142a and 142 b. It will be understood that RAN103 may include any number of Node Bs and RNCs while maintaining consistency with one embodiment As shown in Figure 27C, nodes B140a and 140b are capable of communicating with RNC142a. Further, node B140c is capable of communicating with RNC142b. Nodes B140a, 140b, and 140c are each capable of communicating with RNCs 142a and 142b via an Iub interface. RNCs 142a and 142b are capable of communicating with each other via an Iur interface. Each of RNCs 142a and 142b may be configured to control each of the Node Bs 140a, 140b, and 140c to which it is connected. Further each of RNCs 142a and 142b may be configured to perform or support other functions such as outer loop power control, load control, admission control, packet scheduling, handover control, macro diversity, security functions

[0233] data encryption, etc The core network 106 shown in Figure 27C includes a Media Gateway (MGW) 144 and a Mobile Switching Center (MSC As shown in Figure 27C, nodes B140a and 140b are capable of communicating with RNC142a. Further, node B140c is capable of communicating with RNC142b. Nodes B140a, 140b, and 140c are each capable of communicating with RNCs 142a and 142b via an Iub interface. RNCs 142a and 142b are capable of communicating with each other via an Iur interface. Each of RNCs 142a and 142b may be configured to control each of the Node Bs 140a, 140b, and 140c to which it is connected. Further each of RNCs 142a and 142b may be configured to perform or support other functions such as outer loop power control, load control, admission control, packet scheduling, handover control, macro diversity, security functions data encryption, etc As shown in Figure 27C, nodes B140a and 140b are capable of communicating with RNC142a. Further, node B140c is capable of communicating with RNC142b. Nodes B140a, 140b, and 140c are each capable of communicating with RNCs 142a and 142b via an Iub interface. RNCs 142a and 142b are capable of communicating with each other via an Iur interface. Each of RNCs 142a and 142b may be configured to control each of the Node Bs 140a, 140b, and 140c to which it is connected. Further each of RNCs 142a and 142b may be configured to perform or support other functions such as outer loop power control, load control, admission control, packet scheduling, handover control, macro diversity, security functions

[0234] data encryption, etc MGW) 144 and a Mobile Switching Center (MSC ) 146, and at least one of a Serving General Packet Radio Service (GPRS) Support Node (SGSN) 148 and a Gateway GPRS Support Node (GGSN) 150 can be included. Each of the above elements is illustrated as part of the core network 106, but it will be understood that any of these elements may be owned and operated by entities other than the core network operator. : GPRS) Support Node (Serving GPRS Support Node: SGSN) 148 and the gateway GPRS support node (Gateway GPRS Support Node: GGSN) 150 can be included. Although each of the above elements is illustrated as part of the core network 106, it will be understood that any of these elements may be owned and operated by entities other than the core network operator. The RNC 142a in the RAN 103 may be connected to the MSC 146 in the core network 106 via the IuCS interface. The MSC 146 may be connected to the MGW 144. The MSC 146 and the MGW 144 can provide access to a circuit-switched network such as the PSTN 108 to the WTRUs 102a, 102b, 102c, and facilitate communication between the WTRUs 102a, 102b, 102c and conventional fixed wired communication devices. The RNC 142a in the RAN 103 may be further connected to the SGSN 148 in the core network 106 via the IuPS interface. The SGSN 148 may be connected to the GGSN 150. The SGSN 148 and the GGSN 150 can provide access to a packet-switched network such as the Internet 110 to the WTRUs 102a, 102b, 102c, and facilitate communication between the WTRUs 102a, 102b, 102c and IP-compatible devices.

[0235] The RNC 142a in the RAN 103 may be connected to the MSC 146 in the core network 106 via the IuCS interface. The MSC 146 may be connected to the MGW 144. The MSC 146 and the MGW 144 can provide access to a circuit-switched network such as the PSTN 108 to the WTRUs 102a, 102b, 102c, and facilitate communication between the WTRUs 102a, 102b, 102c and conventional fixed wired communication devices. The RNC 142a in the RAN 103 may be connected to the MSC 146 in the core network 106 via the IuCS interface. The MSC 146 may be connected to the MGW 144. The MSC 146 and the MGW 144 can provide access to a circuit-switched network such as the PSTN 108 to the WTRUs 102a, 102b, 102c, and facilitate communication between the WTRUs 102a, 102b, 102c and conventional fixed wired communication devices. The RNC 142a in the RAN 103 may be connected to the MSC 146 in the core network 106 via the IuCS interface. The MSC 146 may be connected to the MGW 144. The MSC 146 and the MGW 144 can provide access to a circuit-switched network such as the PSTN 108 to the WTRUs 102a, 102b, 102c, and facilitate communication between the WTRUs 102a, 102b, 102c and conventional fixed wired communication devices. The RNC 142a in the RAN 103 may be connected to the MSC 146 in the core network 106 via the IuCS interface. The MSC 146 may be connected to the MGW 144. The MSC 146 and the MGW 144 can provide access to a circuit-switched network such as the PSTN 108 to the WTRUs 102a, 102b, 102c, and facilitate communication between the WTRUs 102a, 102b, 102c and conventional fixed wired communication devices. The RNC 142a in the RAN 103 may be connected to the MSC 146 in the core network 106 via the IuCS interface. The MSC 146 may be connected to the MGW 144. The MSC 146 and the MGW 144 can provide access to a circuit-switched network such as the PSTN 108 to the WTRUs 102a, 102b, 102c, and facilitate communication between the WTRUs 102a, 102b, 102c and conventional fixed wired communication devices. The RNC 142a in the RAN 103 may be connected to the MSC 146 in the core network 106 via the IuCS interface. The MSC 146 may be connected to the MGW 144. The MSC 146 and the MGW 144 can provide access to a circuit-switched network such as the PSTN 108 to the WTRUs 102a, 102b, 102c, and facilitate communication between the WTRUs 102a, 102b, 102c and conventional fixed wired communication devices.

[0236] The RNC 142a in the RAN 103 may be further connected to the SGSN 148 in the core network 106 via the IuPS interface. The SGSN 148 may be connected to the GGSN 150. The SGSN 148 and the GGSN 150 can provide access to a packet-switched network such as the Internet 110 to the WTRUs 102a, 102b, 102c, and facilitate communication between the WTRUs 102a, 102b, 102c and IP-compatible devices. The RNC 142a in the RAN 103 may be further connected to the SGSN 148 in the core network 106 via the IuPS interface. The SGSN 148 may be connected to the GGSN 150. The SGSN 148 and the GGSN 150 can provide access to a packet-switched network such as the Internet 110 to the WTRUs 102a, 102b, 102c, and facilitate communication between the WTRUs 102a, 102b, 102c and IP-compatible devices. The RNC 142a in the RAN 103 may be further connected to the SGSN 148 in the core network 106 via the IuPS interface. The SGSN 148 may be connected to the GGSN 150. The SGSN 148 and the GGSN 150 can provide access to a packet-switched network such as the Internet 110 to the WTRUs 102a, 102b, 102c, and facilitate communication between the WTRUs 102a, 102b, 102c and IP-compatible devices. The RNC 142a in the RAN 103 may be further connected to the SGSN 148 in the core network 106 via the IuPS interface. The SGSN 148 may be connected to the GGSN 150. The SGSN 148 and the GGSN 150 can provide access to a packet-switched network such as the Internet 110 to the WTRUs 102a, 102b, 102c, and facilitate communication between the WTRUs 102a, 102b, 102c and IP-compatible devices. The RNC 142a in the RAN 103 may be further connected to the SGSN 148 in the core network 106 via the IuPS interface. The SGSN 148 may be connected to the GGSN 150. The SGSN 148 and the GGSN 150 can provide access to a packet-switched network such as the Internet 110 to the WTRUs 102a, 102b, 102c, and facilitate communication between the WTRUs 102a, 102b, 102c and IP-compatible devices. The RNC 142a in the RAN 103 may be further connected to the SGSN 148 in the core network 106 via the IuPS interface. The SGSN 148 may be connected to the GGSN 150. The SGSN 148 and the GGSN 150 can provide access to a packet-switched network such as the Internet 110 to the WTRUs 102a, 102b, 102c, and facilitate communication between the WTRUs 102a, 102b, 102c and IP-compatible devices.

[0237] As described above, the core network 106 may be further connected to a network 112 that may include a wired or wireless network owned and operated by another service provider.

[0238] FIG. 27D is a diagram of a system of the RAN 104 and the core network 107 according to one embodiment. As described above, the RAN 104 may employ E-UTRA radio technology and communicate with the WTRUs 102a, 102b, 102c via the air interface 116. The RAN 104 may also communicate with the core network 107.

[0239] The RAN 104 may include eNodeBs 160a, 160b, 160c, but it will be understood that the RAN 104 may include any number of eNodeBs while maintaining consistency with one embodiment. Each of the eNodeBs 160a, 160b, 160c may include one or more transceivers for communicating with the WTRUs 102a, 102b, 102c via the air interface 116. In one embodiment, the eNodeBs 160a, 160b, 160c may implement MIMO technology. In so doing, the eNodeB 160a, for example, may transmit wireless signals to the WTRU 102a using multiple antennas and receive wireless signals therefrom.

[0240] Each of the eNodeBs 160a, 160b, 160c may be associated with a particular cell (not shown) and may be configured to perform processes such as radio resource management decisions, handover decisions, and user scheduling in the uplink and downlink. FIG. 2 As shown in FIG. 7D, eNodeBs 160a, 160b, and 160c can communicate with each other via the X2 interface.

[0241] The core network 107 shown in FIG. 27D can include a Mobility Management Gateway (MME) 1 62, a Serving Gateway 164, and a Packet Data Network (PDN) Gateway 166. Although each of the above elements is shown as part of the core network 107, it will be understood that any of these elements may be owned and operated by entities other than the core network operator.

[0242] The MME 162 may be connected to each of the eNodeBs 160a, 160b, and 160c in the RAN 104 via the S1 interface and may function as a control node. For example, the MME 162 may be responsible for authenticating users of the WTRUs 102a, 102b, and 102c, activating / deactivating bearers, selecting a specific serving gateway during the initial attachment of the WTRUs 102a, 102b, and 102c, etc. The MME 162 may further provide control plane functions for switching between the RAN 104 and other RANs (not shown) using other radio technologies such as GSM and WCDMA.

[0243] The Serving Gateway 164 may be connected to each of the eNodeBs 160a, 160b, and 160c in the RAN 104 via the S1 interface. The Serving Gateway 164 generally forwards user data packets to the WTRUs 102a, 102b, and 102 It can be routed to or from c. Service Serving gateway 164 can further perform other functions such as anchoring of user planes during handover between eNodeBs, paging triggering when WTRU102a, 102b, 102c are capable of using downlink data, and management and storage of contexts of WTRU102a, 102b, 102c. It can be routed to or from c. Service Serving gateway 164 can further perform other functions such as anchoring of user planes during handover between eNodeBs, paging triggering when WTRU102a, 102b, 102c are capable of using downlink data, and management and storage of contexts of WTRU102a, 102b, 102c. Serving gateway 164 can further perform other functions such as anchoring of user planes during handover between eNodeBs, paging triggering when WTRU102a, 102b, 102c are capable of using downlink data, and management and storage of contexts of WTRU102a, 102b, 102c.

[0244] Serving gateway 164 can also be connected to PDN gateway 166. PDN gateway 166 provides access to a packet switched network such as the Internet 110 to WTRU102a, 102b, 102c, and can smooth the communication between WTRU102a, 102b, 102c and IP - enabled devices. Serving gateway 164 can also be connected to PDN gateway 166. PDN gateway 166 provides access to a packet switched network such as the Internet 110 to WTRU102a, 102b, 102c, and can smooth the communication between WTRU102a, 102b, 102c and IP - enabled devices. Serving gateway 164 can also be connected to PDN gateway 166. PDN gateway 166 provides access to a packet switched network such as the Internet 110 to WTRU102a, 102b, 102c, and can smooth the communication between WTRU102a, 102b, 102c and IP - enabled devices. Serving gateway 164 can also be connected to PDN gateway 166. PDN gateway 166 provides access to a packet switched network such as the Internet 110 to WTRU102a, 102b, 102c, and can smooth the communication between WTRU102a, 102b, 102c and IP - enabled devices.

[0245] Core network 107 can smooth the communication with other networks. For example, core network 107 provides access to a circuit - switched network such as PSTN108 to WTRU102a, 102b, 102c, and can smooth the communication between WTRU102a, 102b, 102c and traditional fixed - wired communication devices. For example, core network 107 can include or communicate with an IP gateway (e.g., an IP Multimedia Subsystem (IMS) server) that functions as an interface between core network 107 and PSTN108. Further, core network 107 provides access to network 112 that may include wired or wireless communication networks owned and operated by other service providers to WTRU102. Core network 107 can smooth the communication with other networks. For example, core network 107 provides access to a circuit - switched network such as PSTN108 to WTRU102a, 102b, 102c, and can smooth the communication between WTRU102a, 102b, 102c and traditional fixed - wired communication devices. For example, core network 107 can include or communicate with an IP gateway (e.g., an IP Multimedia Subsystem (IMS) server) that functions as an interface between core network 107 and PSTN108. Further, core network 107 provides access to network 112 that may include wired or wireless communication networks owned and operated by other service providers to WTRU102. Core network 107 can smooth the communication with other networks. For example, core network 107 provides access to a circuit - switched network such as PSTN108 to WTRU102a, 102b, 102c, and can smooth the communication between WTRU102a, 102b, 102c and traditional fixed - wired communication devices. For example, core network 107 can include or communicate with an IP gateway (e.g., an IP Multimedia Subsystem (IMS) server) that functions as an interface between core network 107 and PSTN108. Further, core network 107 provides access to network 112 that may include wired or wireless communication networks owned and operated by other service providers to WTRU102. Core network 107 can smooth the communication with other networks. For example, core network 107 provides access to a circuit - switched network such as PSTN108 to WTRU102a, 102b, 102c, and can smooth the communication between WTRU102a, 102b, 102c and traditional fixed - wired communication devices. For example, core network 107 can include or communicate with an IP gateway (e.g., an IP Multimedia Subsystem (IMS) server) that functions as an interface between core network 107 and PSTN108. Further, core network 107 provides access to network 112 that may include wired or wireless communication networks owned and operated by other service providers to WTRU102. Core network 107 can smooth the communication with other networks. For example, core network 107 provides access to a circuit - switched network such as PSTN108 to WTRU102a, 102b, 102c, and can smooth the communication between WTRU102a, 102b, 102c and traditional fixed - wired communication devices. For example, core network 107 can include or communicate with an IP gateway (e.g., an IP Multimedia Subsystem (IMS) server) that functions as an interface between core network 107 and PSTN108. Further, core network 107 provides access to network 112 that may include wired or wireless communication networks owned and operated by other service providers to WTRU102. Core network 107 can smooth the communication with other networks. For example, core network 107 provides access to a circuit - switched network such as PSTN108 to WTRU102a, 102b, 102c, and can smooth the communication between WTRU102a, 102b, 102c and traditional fixed - wired communication devices. For example, core network 107 can include or communicate with an IP gateway (e.g., an IP Multimedia Subsystem (IMS) server) that functions as an interface between core network 107 and PSTN108. Further, core network 107 provides access to network 112 that may include wired or wireless communication networks owned and operated by other service providers to WTRU102. Core network 107 can smooth the communication with other networks. For example, core network 107 provides access to a circuit - switched network such as PSTN108 to WTRU102a, 102b, 102c, and can smooth the communication between WTRU102a, 102b, 102c and traditional fixed - wired communication devices. For example, core network 107 can include or communicate with an IP gateway (e.g., an IP Multimedia Subsystem (IMS) server) that functions as an interface between core network 107 and PSTN108. Further, core network 107 provides access to network 112 that may include wired or wireless communication networks owned and operated by other service providers to WTRU102. Core network 107 can smooth the communication with other networks. For example, core network 107 provides access to a circuit - switched network such as PSTN108 to WTRU102a, 102b, 102c, and can smooth the communication between WTRU102a, 102b, 102c and traditional fixed - wired communication devices. For example, core network 107 can include or communicate with an IP gateway (e.g., an IP Multimedia Subsystem (IMS) server) that functions as an interface between core network 107 and PSTN108. Further, core network 107 provides access to network 112 that may include wired or wireless communication networks owned and operated by other service providers to WTRU102. Core network 107 can smooth the communication with other networks. For example, core network 107 provides access to a circuit - switched network such as PSTN108 to WTRU102a, 102b, 102c, and can smooth the communication between WTRU102a, 102b, 102c and traditional fixed - wired communication devices. For example, core network 107 can include or communicate with an IP gateway (e.g., an IP Multimedia Subsystem (IMS) server) that functions as an interface between core network 107 and PSTN108. Further, core network 107 provides access to network 112 that may include wired or wireless communication networks owned and operated by other service providers to WTRU102. a, 102b, and 102c.

[0246] FIG. 27E illustrates a system of the RAN 105 and the core network 109 according to an embodiment. The RAN 105 employs IEEE 802.16 wireless technology to provide wireless access to the air The access server communicates with the WTRUs 102a, 102b, and 102c via an interface 117. It may also be an Access Service Network (ASN). As discussed, the WTRUs 102a, 102b, and 102c, the RAN 105, and the core network Define the communication links between the different functional entities of the network 109 as reference points. can be done.

[0247] As shown in FIG. 27E, the RAN 105 includes base stations 180a, 180b, and 180c and an ASN The RAN 105 may include a gateway 182 while remaining consistent with an embodiment. It will be appreciated that the system may include any number of base stations and ASN gateways. Each of the stations 180a, 180b, 180c is associated with a particular cell within the RAN 105. The WTRUs 102a, 102b, 102c may be connected to each other via an air interface 117. 2c. In one embodiment, The base stations 180a, 180b, and 180c may implement MIMO technology. , the base station 180a may, for example, use multiple antennas to transmit wireless signals to the WTRU 102a. The base stations 180a, 180b, 18 0c also supports handoff triggering, tunnel establishment, radio resource management, traffic It can provide mobility management functions such as hook classification and implementation of service quality (QoS) policies. It can be done. The ASN gateway 182 can function as a traffic aggregation point and can be in charge of paging, caching of subscriber profiles, routing to the core network 109, etc.

[0248] The air interface 117 between the WTRUs 102a, 102b, 102c and the RAN 105 can be defined as an R1 reference point implementing the IEEE 802.16 specification. Furthermore, each of the WTRUs 102a, 102b, 102c can construct a logical interface (not shown) with the core network 109. The logical interface between the WTRUs 102a, 102b, 102c and the core network 109 can be defined as an R2 reference point that can be used for authentication, authorization, IP host configuration management, and mobility management.

[0249] The communication link between each of the base stations 180a, 180b, 180c can be defined as an R8 reference point including a protocol for facilitating WTRU handover and data transfer between base stations. The communication link between the base stations 180a, 180b, 180c and the ASN gateway 182 can be defined as an R6 reference point. The R6 reference point can include a protocol for facilitating mobility management based on mobility events associated with each of the WTRUs 102a, 102b, 102c.

[0250] As shown in Figure 27E, the RAN 105 can be connected to the core network 109. The communication link between the RAN 105 and the core network 109 can be, for example, for data transfer and mobility It can be defined as an R3 reference point including a protocol for promoting the RTI management ability The core network 109 can include a Mobile IP Home Agent (MIP-HA) 184, an Authentication, Authorization, Accounting (AAA) server 186, and a gateway 188. Each of the above elements is illustrated as part of the core network 109, but it should be understood that any of these elements may be owned and operated by entities other than the core network operator. Agent:MIP-HA) 184, an Authentication, Authorization, Accounting (AAA) server 186, and a gateway 188. The MIP-HA can be in charge of IP address management and enable the WTRUs 102a, 102b, 102c to roam between different ASNs and different core networks. The MIP-HA 184 can provide access to a packet-switched network such as the Internet 110 to the WTRUs 102a, 102b, 102c and facilitate communication between the WTRUs 102a, 102b, 102c and IP-enabled devices. The AAA server 186 can be in charge of user authentication and support of user services. The gateway 188 can facilitate interworking with other networks. For example, the gateway 188 can provide access to a circuit-switched network such as the PSTN 108 to the WTRUs 102a, 102b, 102c and facilitate communication between the WTRUs 102a, 102b, 102c and conventional fixed wired communication devices. Further, the gateway 188 can be a wired or wireless communication owned and operated by other service providers. Although each of the above elements is illustrated as part of the core network 109, it should be understood that any of these elements may be owned and operated by entities other than the core network operator. It should be understood that any of these elements may be owned and operated by entities other than the core network operator. operated by entities other than the core network operator.

[0251] The MIP-HA can be in charge of IP address management and enable the WTRUs 102a, 102b, 102c to roam between different ASNs and different core networks. The MIP-HA can be in charge of IP address management and enable the WTRUs 102a, 102b, 102c to roam between different ASNs and different core networks. The MIP-HA 184 can provide access to a packet-switched network such as the Internet 110 to the WTRUs 102a, 102b, 102c and facilitate communication between the WTRUs 102a, 102b, 102c and IP-enabled devices. The MIP-HA 184 can provide access to a packet-switched network such as the Internet 110 to the WTRUs 102a, 102b, 102c and facilitate communication between the WTRUs 102a, 102b, 102c and IP-enabled devices. The AAA server 186 can be in charge of user authentication and support of user services. The gateway 188 can facilitate interworking with other networks. The AAA server 186 can be in charge of user authentication and support of user services. The gateway 188 can facilitate interworking with other networks. For example, the gateway 188 can provide access to a circuit-switched network such as the PSTN 108 to the WTRUs 102a, 102b, 102c and facilit...

Claims

1. An apparatus comprising a processor, a memory, and a communication circuit, the apparatus comprising: The device is connected to a network via a path, and the device is stored in the memory and the processor When executed by the A base station transmits one or more sub-bands including one or more sub-band (SB) configurations. SB indication, or the base station's Listen Before Talk (LBT) indication. Receiving the results The apparatus further comprises computer-executable instructions to cause the apparatus to execute the steps of:

2. The instruction is to transmit a remapped control resource set (CO 2. The apparatus of claim 1, further comprising: a first command for receiving a first RESET from said apparatus;

3. The instruction specifies a physical resource block in a control resource set (CORESET). The PRBs in the group of PRBs overlap with the guard band at least partially. and further causing the device to determine that the PRB is invalid based on the objective.

2. The apparatus of claim 1.

4. The instructions are based at least in part on whether the PRB overlaps with the guard band. and further causing the device to determine that the PRB group is invalid.

4. The apparatus of claim 3.

5. The instructions may also be used to ensure that any invalid PRBs do not carry a Physical Downlink Control Channel (PDCCH). The device further performs blind detection of the PDCCH under the assumption that the PDCCH is not The apparatus of claim 3 .

6. The instructions are for transmitting MSG3 in a Random Access Channel (RACH) procedure. determining a plurality of transmission opportunities in the frequency domain of 2. The apparatus described in 1.

7. The plurality of transmission opportunities may include subbands or bandwidth parts (BWPs) for MSG3.

2. The method of claim 1, further comprising:

7. The apparatus described in 6.

8. The plurality of transmission opportunities may be based at least in part on one or more configured subbands.

7. The apparatus of claim 6, wherein the estimated value is determined by applying a shift based on the estimated value.

9. From multiple MSG3 transmission opportunities provided by one or more MSG2 messages 7. The method of claim 6, wherein the transmission opportunity is determined based at least in part on the random selection of The equipment.

10. A transmission opportunity is determined based at least in part on an identifier (ID) of the device. and multiple MSG3 transmission opportunities provided by one or more MSG2 messages. The device of claim 6 , wherein the

11. The instructions include a plurality of transmission opportunities in the time domain, the transmission opportunities being determined by a random access channel (RA determining a plurality of transmission opportunities for MSG3 transmission in the MSG3 (CH) procedure; The apparatus of claim 1 .

12. The plurality of transmission opportunities may include random access The apparatus of claim 11 , wherein the response is determined at least in part based on the response (RAR).

13. The instructions further include determining an LBT type that is MSG3 of a RACH procedure. The apparatus of claim 11 , wherein the apparatus executes

14. The instructions include downlink control information for scheduling a random access response (RAR) determining the LBT type from the DCI or from the RAR. The apparatus of claim 13 , wherein the apparatus executes

15. The command is transmitted to a Channel State Information Reference Signal (CSIRS). Signal: CSI-RS) Subbands are available LBT subbands and unavailable LBT The CSI-RS subband is at least partially determined based on whether the subband boundary is crossed. The subbands may be completely omitted, partially omitted, or may fit within the available subbands. The apparatus of claim 1 , further comprising: determining whether the first and second inputs are in a predetermined order.

16. The unavailable LBT sub-band may be a guard band or a sub-band of the LBT of the base station.

16. The apparatus of claim 15, wherein the LBT subbands are indicated as unavailable based on the results. Place.

17. The instructions may include a channel state that the base station belongs to prior to successfully acquiring a channel. Carries out Channel State Information Reference Signal (CSI-RS) By omitting one or more Orthogonal Frequency Division Multiplexing (OFDM) symbols, and further causing the device to adjust the assumption of the CSI-RS in the device.

13. The apparatus of claim 1 .

18. The instructions are based at least in part on when the base station successfully acquires a channel. In this case, the Channel State Information Reference Signal (CSIR) is used. One or more orthogonal frequency division multiplexing (OFDM) symbols carrying CSI-RS By shifting the CSI-RS, the assumption of the CSI-RS in the device can be adjusted. The apparatus of claim 1 further comprising:

19. The instruction: providing support information to the base station related to an LBT result of the device; receiving an adjusted SB indication from the base station; The apparatus of claim 1 , further comprising:

20. The one or more SB indications and the assistance information are during a first portion of a time period (MCOT), exchanged between the device and the base station; The adjusted SB indication is received during a second portion of the MCOT.

20. The apparatus of claim 19.

21. The assistance information includes one or more preferred downlink (DL) subbands.

20. The device described in item 19.

22. 2. The method of claim 1, wherein the one or more SB indications include a group identifier. Equipment.

23. The instructions adjust a search space based at least in part on available subbands. The apparatus of claim 1 , further comprising:

Images