Method and device for cell aggregation in communication system

Abstract

A method and a device for cell aggregation in a communication system are disclosed. The method for a terminal comprises the steps of: receiving, from a base station, system information including subband full duplex (SBFD) configuration information, uplink (UL)-downlink (DL) configuration information, and random-access channel (RACH) configuration information; identifying an SD (SBFD) resource indicated by the SDFD configuration information; identifying a non-SD (ND) resource indicated by the UL-DL configuration information; and determining a valid RO set among an additional RACH occasion (RO) set configured in the SD resource or a legacy RO set configured in the ND resource, on the basis of the RACH configuration information.

Description

Method and device for cell combining in a communication system

[0001] The present disclosure relates to communication technology, and more particularly, to cell search technology and random access technology.

[0002] With the advancement of information and communication technology, various wireless communication technologies are being developed. Representative wireless communication technologies include LTE (long term evolution) and NR (new radio), both of which are defined by the 3rd generation partnership project (3GPP) standards. LTE can be one of the 4th generation (4G) wireless communication technologies, and NR can be one of the 5th generation (5G) wireless communication technologies.

[0003] To handle the rapidly increasing volume of wireless data following the commercialization of 4G communication systems (e.g., communication systems supporting LTE), 5G communication systems (e.g., communication systems supporting NR) that utilize higher frequency bands (e.g., frequency bands higher than 6 GHz) than the frequency bands of 4G communication systems (e.g., frequency bands below 6 GHz) are being considered. 5G communication systems can support enhanced Mobile Broadband (eMBB), Ultra-Reliable and Low Latency Communication (URLLC), and massive Machine Type Communication (mMTC). Discussions are ongoing regarding 6G communication systems that will follow 5G communication systems.

[0004] Meanwhile, if a terminal is located at the edge of a base station's coverage area, communication quality between the terminal and the base station may deteriorate. In this case, the terminal may not be able to communicate with the base station. Methods to address the above-mentioned issues are needed.

[0005] The purpose of the present disclosure to solve the above problems is to provide a method and device for cell search and random access in a communication system.

[0006] According to embodiments of the present disclosure for achieving the above object, a method of a terminal includes the steps of: receiving system information including subband full duplex (SBFD) configuration information, uplink (UL)-downlink (DL) configuration information, and random access channel (RACH) configuration information from a base station; identifying an SD (SBFD) resource indicated by the SBFD configuration information; identifying an ND (non-SD) resource indicated by the UL-DL configuration information; determining a valid RO set from among an additional RO (RACH occasion) set configured in the SD resource or a legacy RO set configured in the ND resource based on the RACH configuration information; and transmitting an RA (random access) preamble from the valid RO set to the base station.

[0007] The above SD resource may be a resource capable of UL communication and DL communication, the ND resource may include at least one of a UL resource, a DL resource, or a FL (flexible) resource, the UL resource may be a resource capable of the UL communication, the DL resource may be a resource capable of the DL communication, the FL resource may be a resource capable of the UL communication or the UL communication, and each of the additional RO set and the legacy RO set may include one or more ROs.

[0008] The method of the terminal may further include a step of receiving a synchronization signal block (SSB) from the base station, and an RO set located after a preset time from the reception time of the SSB among the additional RO set or the legacy RO set may be determined as the valid RO set.

[0009] The method of the terminal may further include a step of performing an SSB-RO mapping operation on the valid RO set, wherein the SSB-RO mapping operation may not be performed on an invalid RO set among the additional RO set or the legacy RO set.

[0010] The additional RO set set in the above SD resource can be determined as the valid RO set, and the additional RO set can be an RO set set in an SD-DL resource or an SD-FL resource among the SD resources, and the SD-DL resource can be a DL resource having a UL subband, and the SD-FL resource can be an FL resource having the UL subband or an FL resource not having the UL subband.

[0011] The step of determining the valid RO set may include the step of performing a validity determination procedure on the additional RO set including at least one SD resource; and the step of determining the legacy RO set set in the ND resource as the valid RO set without performing the validity determination procedure.

[0012] The legacy RO set set in the ND resource may be considered invalid in the SD resource, and the additional RO set set in the SD resource may be considered invalid in the ND resource.

[0013] The above RACH configuration information may include one or more RACH general configurations associated with one or more PRACH (physical random access channel) configuration indices, and each of the one or more RACH general configurations may include at least one of time resource information or frequency resource information of the RO set.

[0014] If the above RACH configuration information includes one RACH general configuration associated with one PRACH configuration index, at least one of the additional RO set or the legacy RO set can be configured based on the one RACH general configuration.

[0015] When the above RACH configuration information includes a first RACH general configuration and a second RACH general configuration, the legacy RO set may be configured based on the first RACH general configuration associated with the first PRACH configuration index, and the additional RO set may be configured based on the second RACH general configuration associated with the second PRACH configuration index.

[0016] The above system information may further include information indicating that one PRACH configuration index or two PRACH configuration indices are configured in the terminal.

[0017] According to embodiments of the present disclosure for achieving the above object, a terminal includes at least one processor, wherein the at least one processor causes the terminal to receive system information including subband full duplex (SBFD) configuration information, uplink (UL)-downlink (DL) configuration information, and random access channel (RACH) configuration information from a base station; identify an SD (SBFD) resource indicated by the SBFD configuration information; identify an ND (non-SD) resource indicated by the UL-DL configuration information; determine a valid RO set from among an additional RO (RACH occasion) set configured in the SD resource or a legacy RO set configured in the ND resource based on the RACH configuration information; and transmit an RA (random access) preamble from the valid RO set to the base station.

[0018] The above SD resource may be a resource capable of UL communication and DL communication, the ND resource may include at least one of a UL resource, a DL resource, or a FL (flexible) resource, the UL resource may be a resource capable of the UL communication, the DL resource may be a resource capable of the DL communication, the FL resource may be a resource capable of the UL communication or the UL communication, and each of the additional RO set and the legacy RO set may include one or more ROs.

[0019] The at least one processor may further cause the terminal to receive a synchronization signal block (SSB) from the base station, and an RO set located after a preset time from the reception time of the SSB among the additional RO set or the legacy RO set may be determined as the valid RO set.

[0020] The at least one processor may further cause the terminal to perform an SSB-RO mapping operation for the valid RO set, wherein the SSB-RO mapping operation may not be performed for an invalid RO set among the additional RO set or the legacy RO set.

[0021] The additional RO set set in the above SD resource can be determined as the valid RO set, and the additional RO set can be an RO set set in an SD-DL resource or an SD-FL resource among the SD resources, and the SD-DL resource can be a DL resource having a UL subband, and the SD-FL resource can be an FL resource having the UL subband or an FL resource not having the UL subband.

[0022] When determining the valid RO set, the at least one processor may cause the terminal to perform a validity determination procedure for the additional RO set including at least one SD resource; and, without performing the validity determination procedure, determine the legacy RO set set in the ND resource as the valid RO set.

[0023] The above RACH configuration information may include one or more RACH general configurations associated with one or more PRACH (physical random access channel) configuration indices, and each of the one or more RACH general configurations may include at least one of time resource information or frequency resource information of the RO set.

[0024] If the above RACH configuration information includes one RACH general configuration associated with one PRACH configuration index, at least one of the additional RO set or the legacy RO set can be configured based on the one RACH general configuration.

[0025] When the above RACH configuration information includes a first RACH general configuration and a second RACH general configuration, the legacy RO set may be configured based on the first RACH general configuration associated with the first PRACH configuration index, and the additional RO set may be configured based on the second RACH general configuration associated with the second PRACH configuration index.

[0026] According to the present disclosure, a terminal can identify SD (SBFD (subband full duplex)) resources and ND (non-SD) resources based on information included in system information received from a base station, identify RO (RACH (random access channel) occasion) set(s) configured in the SD resources and / or ND resources, identify a valid RO set among the RO set(s), and transmit an RA (random access) preamble to the base station from the valid RO set. Based on the above-described operations, an RA procedure can be efficiently performed in a communication system supporting an SBFD operation, and the performance of the communication system can be improved.

[0027] Figure 1 is a conceptual diagram illustrating a first embodiment of a communication system.

[0028] Figure 2 is a block diagram illustrating a first embodiment of a communication node constituting a communication system.

[0029] FIG. 3 is a conceptual diagram illustrating a first embodiment of a subband filtering mask for a DL subband and an UL subband in an SD symbol.

[0030] FIG. 4 is a conceptual diagram illustrating a first embodiment of a slot pattern (e.g., a TDD slot pattern) including SD symbols.

[0031] Figure 5 illustrates a first embodiment of a base station implementing a TDD system.

[0032] Figure 6 illustrates a first embodiment of a base station implementing SBFD operation.

[0033] Figure 7 illustrates a second embodiment of a base station implementing SBFD operation.

[0034] Figure 8 illustrates a third embodiment of a base station implementing SBFD operation.

[0035] Figure 9 is a flowchart illustrating a communication method between a base station and a terminal.

[0036] Figure 10 is a flowchart illustrating a communication method between a base station and a terminal.

[0037] Figure 11 is a conceptual diagram illustrating the setting of the PRACH combining cycle.

[0038] Figure 12 is a conceptual diagram illustrating the setting of the PRACH combining cycle.

[0039] Fig. 13 is a conceptual diagram illustrating a first embodiment of interpreting the setting of a RO set mapped to an SD symbol and a UL symbol.

[0040] Fig. 14 is a conceptual diagram illustrating a second embodiment of interpreting the setting of a RO set mapped to SD symbols and UL symbols.

[0041] Fig. 15 is a conceptual diagram illustrating a third embodiment of interpreting the setting of a RO set mapped to SD symbols and UL symbols.

[0042] Fig. 16 is a conceptual diagram illustrating a fourth embodiment of interpreting the setting of a RO set mapped to SD symbols and UL symbols.

[0043] Figure 17 is a conceptual diagram illustrating a first embodiment in which one RO is mapped across SD symbols and non-SD symbols.

[0044] Figure 18 is a conceptual diagram illustrating a second embodiment in which one RO is mapped across SD symbols and non-SD symbols.

[0045] Figure 19 is a conceptual diagram illustrating a third embodiment in which one RO is mapped across SD symbols and non-SD symbols.

[0046] Figure 20 is a conceptual diagram illustrating a first embodiment in which one RO is mapped to a non-SD symbol.

[0047] Figure 21 is a conceptual diagram illustrating a fourth embodiment in which one RO is mapped across SD symbols and non-SD symbols.

[0048] FIG. 22 is a conceptual diagram illustrating an embodiment of an RO composed of SD-FL symbol(s) and / or ND-UL symbol(s).

[0049] Figure 23 is a conceptual diagram illustrating a first embodiment in which ROs are mapped to different frequency resources in SD resources and non-SD resources, respectively.

[0050] Figure 24 is a conceptual diagram illustrating a second embodiment in which ROs are mapped to different frequency resources in SD resources and non-SD resources, respectively.

[0051] Figure 25 is a conceptual diagram illustrating embodiments in which one RO is scheduled across two or more slots.

[0052] Figure 26 is a conceptual diagram illustrating a third embodiment in which ROs are mapped to different frequency resources in SD resources and non-SD resources, respectively.

[0053] Figure 27 is a conceptual diagram illustrating a fourth embodiment in which ROs are mapped to different frequency resources in SD resources and non-SD resources, respectively.

[0054] Figure 28 is a conceptual diagram illustrating a first embodiment in which one Msg3 instance is mapped across SD symbols and non-SD symbols.

[0055] Figure 29 is a conceptual diagram illustrating a second embodiment in which one Msg3 instance is mapped across SD symbols and non-SD symbols.

[0056] FIG. 30 is a conceptual diagram illustrating a third embodiment in which one Msg3 instance is mapped across SD symbols and non-SD symbols.

[0057] Figure 31 is a conceptual diagram illustrating a first embodiment in which one Msg3 instance is mapped to a non-SD symbol.

[0058] This disclosure may be subject to various modifications and various embodiments. Specific embodiments are illustrated and described in detail in the drawings. However, this is not intended to limit the disclosure to specific embodiments, but rather to encompass all modifications, equivalents, and alternatives falling within the spirit and technical scope of the disclosure.

[0059] While terms such as "first" and "second" may be used to describe various components, these components should not be limited by these terms. These terms are used solely to distinguish one component from another. For example, without departing from the scope of the present disclosure, a first component could be referred to as a "second component," and similarly, a second component could also be referred to as a "first component." The term "and / or" encompasses any combination of multiple related items or any one of multiple related items.

[0060] In embodiments of the present disclosure, “at least one of A and B” may mean “at least one of A or B” or “at least one of combinations of one or more of A and B.” Furthermore, in embodiments of the present disclosure, “at least one of A and B” may mean “at least one of A or B” or “at least one of combinations of one or more of A and B.”

[0061] When a component is referred to as being "connected" or "connected" to another component, it should be understood that it may be directly connected or connected to that other component, but that there may be other components intervening. Conversely, when a component is referred to as being "directly connected" or "connected" to another component, it should be understood that there are no other components intervening.

[0062] The terminology used in this disclosure is only used to describe specific embodiments and is not intended to limit the present disclosure. The singular expression includes the plural expression unless the context clearly indicates otherwise. In this disclosure, it should be understood that the terms "comprises" or "has" indicate the presence of a feature, number, step, operation, component, part, or combination thereof described in the specification, but do not preclude the presence or addition of one or more other features, numbers, steps, operations, components, parts, or combinations thereof.

[0063] Unless otherwise defined, all terms used herein, including technical or scientific terms, have the same meaning as commonly understood by a person of ordinary skill in the art to which this disclosure pertains. Terms defined in commonly used dictionaries should be interpreted as having a meaning consistent with their meaning in the context of the relevant technology, and shall not be interpreted in an idealized or overly formal sense unless explicitly defined herein.

[0064] Hereinafter, preferred embodiments of the present disclosure will be described in more detail with reference to the attached drawings. In order to facilitate an overall understanding in describing the present disclosure, identical reference numerals will be used for identical components in the drawings, and redundant descriptions of identical components will be omitted.

[0065] A communication system to which embodiments according to the present disclosure are applied will be described. The communication system to which embodiments according to the present disclosure are applied is not limited to the scope described below, and embodiments according to the present disclosure can be applied to various communication systems. Here, the term "communication system" may be used interchangeably with "communication network."

[0066] In an embodiment, "an operation (e.g., a transmission operation) is set" may mean that "setting information for the operation (e.g., information, information elements, parameters)" and / or "information instructing performance of the operation" are signaled. "Information (e.g., information elements, parameters) is set" may mean that the information is signaled. The signaling may be at least one of SI (system information) signaling (e.g., transmission of a SIB (system information block) and / or MIB (master information block)), RRC signaling (e.g., transmission of an RRC message, an RRC parameter, and / or an upper layer parameter), MAC signaling (e.g., transmission of a MAC message and / or a MAC CE (control element)), or PHY signaling (e.g., transmission of a PHY message, DCI (downlink control information), UCI (uplink control information), and / or SCI (sidelink control information)).

[0067] Figure 1 is a conceptual diagram illustrating a first embodiment of a communication system.

[0068] Referring to FIG. 1, the communication system (100) may include a plurality of communication nodes (110-1, 110-2, 110-3, 120-1, 120-2, 130-1, 130-2, 130-3, 130-4, 130-5, 130-6). In addition, the communication system (100) may further include a core network (e.g., a serving-gateway (S-GW), a packet data network (PDN)-gateway (P-GW), a mobility management entity (MME)). If the communication system (100) is a 5G communication system (e.g., a new radio (NR) system), the core network may include an access and mobility management function (AMF), a user plane function (UPF), a session management function (SMF), etc.

[0069] A plurality of communication nodes (110 to 130) can support a communication protocol (e.g., LTE communication protocol, LTE-A communication protocol, NR communication protocol, etc.) specified in the 3GPP (3rd generation partnership project) standard. The plurality of communication nodes (110 to 130) may support CDMA (code division multiple access) technology, WCDMA (wideband CDMA) technology, TDMA (time division multiple access) technology, FDMA (frequency division multiple access) technology, OFDM (orthogonal frequency division multiplexing) technology, Filtered OFDM technology, CP (cyclic prefix)-OFDM technology, DFT-s-OFDM (discrete Fourier transform-spread-OFDM) technology, OFDMA (orthogonal frequency division multiple access) technology, SC (single carrier)-FDMA technology, NOMA (non-orthogonal multiple access) technology, GFDM (generalized frequency division multiplexing) technology, FBMC (filter bank multi-carrier) technology, UFMC (universal filtered multi-carrier) technology, SDMA (space division multiple access) technology, etc. Each of the plurality of communication nodes may have the following structure.

[0070] Figure 2 is a block diagram illustrating a first embodiment of a communication node constituting a communication system.

[0071] Referring to FIG. 2, a communication node (200) may include at least one processor (210), a memory (220), and a transmission / reception device (230) that is connected to a network and performs communication. In addition, the communication node (200) may further include an input interface device (240), an output interface device (250), a storage device (260), etc. Each component included in the communication node (200) may be connected by a bus (270) and communicate with each other.

[0072] However, each component included in the communication node (200) may be connected through an individual interface or individual bus centered around the processor (210), rather than a common bus (270). For example, the processor (210) may be connected to at least one of a memory (220), a transmission / reception device (230), an input interface device (240), an output interface device (250), and a storage device (260) through a dedicated interface.

[0073] The processor (210) can execute program commands stored in at least one of the memory (220) and the storage device (260). The processor (210) may refer to a central processing unit (CPU), a graphics processing unit (GPU), or a dedicated processor in which the methods according to embodiments of the present disclosure are performed. Each of the memory (220) and the storage device (260) may be configured with at least one of a volatile storage medium and a non-volatile storage medium. For example, the memory (220) may be configured with at least one of a read-only memory (ROM) and a random access memory (RAM).

[0074] Referring again to FIG. 1, the communication system (100) may include a plurality of base stations (110-1, 110-2, 110-3, 120-1, 120-2) and a plurality of terminals (130-1, 130-2, 130-3, 130-4, 130-5, 130-6). Each of the first base station (110-1), the second base station (110-2), and the third base station (110-3) may form a macro cell. Each of the fourth base station (120-1) and the fifth base station (120-2) may form a small cell. The fourth base station (120-1), the third terminal (130-3), and the fourth terminal (130-4) may be within the cell coverage of the first base station (110-1). The second terminal (130-2), the fourth terminal (130-4), and the fifth terminal (130-5) may be within the cell coverage of the second base station (110-2). The fifth base station (120-2), the fourth terminal (130-4), the fifth terminal (130-5), and the sixth terminal (130-6) may be within the cell coverage of the third base station (110-3). The first terminal (130-1) may be within the cell coverage of the fourth base station (120-1). The sixth terminal (130-6) may be within the cell coverage of the fifth base station (120-2).

[0075] Here, each of the plurality of base stations (110-1, 110-2, 110-3, 120-1, 120-2) may be referred to as a NodeB (NB), an evolved NodeB (eNB), a gNB, an advanced base station (ABS), a high reliability-base station (HR-BS), a base transceiver station (BTS), a radio base station, a radio transceiver, an access point, an access node, a radio access station (RAS), a mobile multihop relay-base station (MMR-BS), a relay station (RS), an advanced relay station (ARS), a high reliability-relay station (HR-RS), a home NodeB (HNB), a home eNodeB (HeNB), a road side unit (RSU), a radio remote head (RRH), a transmission point (TP), a transmission and reception point (TRP), etc.

[0076] Each of the plurality of terminals (130-1, 130-2, 130-3, 130-4, 130-5, 130-6) may be referred to as a user equipment (UE), terminal equipment (TE), advanced mobile station (AMS), high reliability-mobile station (HR-MS), terminal, access terminal, mobile terminal, station, subscriber station, mobile station, portable subscriber station, node, device, on board unit (OBU), etc.

[0077] Meanwhile, each of the plurality of base stations (110-1, 110-2, 110-3, 120-1, 120-2) may operate in a different frequency band or may operate in the same frequency band. Each of the plurality of base stations (110-1, 110-2, 110-3, 120-1, 120-2) may be connected to each other via an ideal backhaul link or a non-ideal backhaul link, and may exchange information with each other via the ideal backhaul link or the non-ideal backhaul link. Each of the plurality of base stations (110-1, 110-2, 110-3, 120-1, 120-2) may be connected to the core network via the ideal backhaul link or the non-ideal backhaul link. Each of the plurality of base stations (110-1, 110-2, 110-3, 120-1, 120-2) can transmit a signal received from the core network to the corresponding terminal (130-1, 130-2, 130-3, 130-4, 130-5, 130-6), and can transmit a signal received from the corresponding terminal (130-1, 130-2, 130-3, 130-4, 130-5, 130-6) to the core network.

[0078] Additionally, each of the plurality of base stations (110-1, 110-2, 110-3, 120-1, 120-2) may support multi-input multi-output (MIMO) transmission (e.g., single user (SU)-MIMO, multi user (MU)-MIMO, massive MIMO, etc.), coordinated multipoint (CoMP) transmission, carrier aggregation (CA) transmission, transmission in an unlicensed band, device to device communication (D2D) (or, proximity services (ProSe)), Internet of Things (IoT) communication, dual connectivity (DC), etc. Here, each of the plurality of terminals (130-1, 130-2, 130-3, 130-4, 130-5, 130-6) can perform an operation corresponding to the base station (110-1, 110-2, 110-3, 120-1, 120-2) and an operation supported by the base station (110-1, 110-2, 110-3, 120-1, 120-2). For example, the second base station (110-2) can transmit a signal to the fourth terminal (130-4) based on the SU-MIMO scheme, and the fourth terminal (130-4) can receive a signal from the second base station (110-2) by the SU-MIMO scheme. Alternatively, the second base station (110-2) can transmit signals to the fourth terminal (130-4) and the fifth terminal (130-5) based on the MU-MIMO method, and each of the fourth terminal (130-4) and the fifth terminal (130-5) can receive signals from the second base station (110-2) based on the MU-MIMO method.

[0079] Each of the first base station (110-1), the second base station (110-2), and the third base station (110-3) can transmit a signal to the fourth terminal (130-4) based on the CoMP scheme, and the fourth terminal (130-4) can receive a signal from the first base station (110-1), the second base station (110-2), and the third base station (110-3) based on the CoMP scheme. Each of the plurality of base stations (110-1, 110-2, 110-3, 120-1, 120-2) can transmit and receive a signal with terminals (130-1, 130-2, 130-3, 130-4, 130-5, 130-6) within its cell coverage based on the CA scheme. Each of the first base station (110-1), the second base station (110-2), and the third base station (110-3) can control D2D between the fourth terminal (130-4) and the fifth terminal (130-5), and each of the fourth terminal (130-4) and the fifth terminal (130-5) can perform D2D under the control of the second base station (110-2) and the third base station (110-3).

[0080] Next, the operating methods of communication nodes in a communication system will be described. Even if a method (e.g., signal transmission or reception) performed by a first communication node among communication nodes is described, a corresponding second communication node can perform a method (e.g., signal reception or transmission) corresponding to the method performed by the first communication node. In other words, if the operation of a terminal is described, the corresponding base station can perform an operation corresponding to the operation of the terminal. Conversely, if the operation of a base station is described, the corresponding terminal can perform an operation corresponding to the operation of the base station.

[0081] To reduce data error rates, a lower modulation and coding scheme (MCS) level (e.g., a lower MCS index) can be applied. To prevent the size of the field indicated by the downlink control information (DCI) from increasing, the most frequently used MCS(s) can be selected. Subsequently, to apply a lower MCS, a repetitive transmission operation can be supported. Since quadrature phase shift keying (QPSK) has the lowest modulation rate, this can further reduce the code rate. In particular, since the transmit power in uplink (UL) transmission is limited, the repetitive transmission operation can be performed in the time domain rather than the frequency domain.

[0082] eMBB (enhanced Mobile Broadband) traffic and URLLC (Ultra-Reliable and Low Latency Communication) traffic can use low MCS for different purposes. eMBB traffic can use low MCS to extend the reach. On the other hand, URLLC traffic can use low MCS to reduce latency and achieve low error rates. Because of their different requirements, eMBB traffic can be transmitted repeatedly even if latency occurs, while URLLC traffic can be transmitted using a new MCS (e.g., a lower MCS) rather than repeated transmissions. The new MCS can be set by an RRC message and / or DCI.

[0083] To support repetitive transmissions for eMBB traffic in the time domain, physical uplink shared channel (PUSCH) repetition (e.g., PUSCH repetition type A) may be introduced. In the present disclosure, PUSCH repetition may mean a PUSCH instance. In other words, depending on the context, PUSCH repetition may be interpreted as having the same meaning as a PUSCH instance. Repeated transmission of a PUSCH may be performed in units of PUSCH instances. When repeated transmission of a PUSCH is performed, a PUSCH allocated in units of slots may be repeatedly transmitted. To extend the reach, time resources may be allocated to multiple slots. When PUSCH repetition type A is used, the time resources may be configured by an RRC message and / or DCI. The number of repetitions of PUSCH can be indicated by an RRC message, and the time resource in which PUSCH is transmitted in the first slot can be indicated by a DCI (e.g., a type 2 CG (configured grant) or a dynamic grant) or an RRC message (e.g., a type 1 CG). In the present disclosure, the number of repetitions can mean the number of repeated transmissions or the number of transmissions.

[0084] Repeated transmission of URLLC traffic may not be appropriate because it incurs delay when the traffic is repeatedly transmitted. However, if a sufficiently low MCS is used, the delay for decoding URLLC traffic can be reduced. In other words, if a sufficiently low MCS is used, the number of REs (resource elements) to which URLLC traffic is mapped can increase, and the base station (e.g., the base station decoder) can wait until all REs are received. In this case, the delay for decoding URLLC traffic can be reduced.

[0085] When a PUSCH with a relatively high MCS is repeatedly transmitted, the base station can perform a decoding operation using only some REs. The time to first successful decoding in a PUSCH repeated transmission (e.g., a PUSCH repeated transmission with a relatively high MCS) may be faster than the time to first successful decoding in a PUSCH transmission without repetition (e.g., a PUSCH transmission with a low MCS). When PUSCH repetition type A is used, unnecessary delay may occur, and PUSCH repetition type B may be introduced to reduce the delay time for PUSCH repeated transmission. When PUSCH repetition type B is used, a PUSCH allocated in units of mini-slots may be repeatedly transmitted. When PUSCH repetition type B is used, the time resource may be set by an RRC message and / or DCI. The combination of the reference time resource and the number of repeated transmissions of a PUSCH instance can be indicated by a DCI (e.g., Type 2 CG and / or dynamic grant) or an RRC message (e.g., Type 1 CG).

[0086] In order to control the transmit power of SRS resources indicated by SRI (SRS (sounding reference signal) resource indicator), the base station can estimate the path attenuation for each SRS resource. The base station can control the transmit power for the SRS resource(s) using DCI. The transmit power of the SRS resource(s) can be controlled based on the estimated path attenuation. The DCI can be scheduling DCI (e.g., DCI format 0_0, DCI format 0_1, DCI format 0_2, DCI format 1_0, DCI format 1_1, or DCI format 1_2) or group common (GC)-DCI (e.g., DCI format 2_2 or DCI format 2_3). The DCI can include a field indicating a transmit power control (TPC) command, and the TPC command can be used to control the transmit power of a terminal. For example, the transmission power of a terminal may be increased or decreased based on a TPC command included in the DCI. To determine the transmission power of a PUSCH, the terminal may consider a value obtained based on path attenuation, a value according to a TPC command included in the DCI, and / or a PUSCH bandwidth indicated by the DCI.

[0087] A base station can configure two or more sets for a terminal using higher layer signaling. The terminal can receive configuration information for the two or more sets from the base station. Each element constituting the two or more sets can be a transmit power parameter(s), which can be designated to suit different scenarios (e.g., a URLLC scenario, an eMBB scenario). The terminal can receive a scheduling DCI or an activating DCI from the base station that allocates PUSCH resources, and the scheduling DCI or the activating DCI can indicate a set for interpreting the transmit power parameter(s). If the sets of transmit power parameter(s) are different, the magnitude of the increase or decrease in transmit power designated by the same TPC command can be different.

[0088] When Type 1 CG or Type 2 CG is used, the transmit power may be determined based on DCI format 2_3 for the SRI associated with the PUSCH instance. When Type 2 CG is used, the activation DCI may indicate a set of transmit power parameter(s) applicable to a PUSCH occasion. A PUSCH occasion may mean a PUSCH instance. The UE may obtain a TPC command for the SRI by receiving a GC (group common)-DCI, interpret the TPC command to be suitable for the set of transmit power parameter(s) indicated by the base station, and derive the transmit power applicable to the PUSCH instance based on the interpretation result.

[0089] In a dynamically scheduled PUSCH transmission, the UE can derive the transmit power applied to the PUSCH instance based on a combination of GC-DCI and scheduling DCI. The UE can identify the TPC command of the SRI by receiving the GC-DCI and store the identified TPC command. In a dynamically scheduled PUSCH transmission, a set of transmit power parameter(s) and / or TPC command applied to the PUSCH occasion can be indicated by scheduling DCI. The UE can derive the transmit power applied to the PUSCH instance based on the transmit power of the SRI associated with the PUSCH instance.

[0090] Repeated HARQ-ACK transmissions can be indicated (or configured) by higher-layer signaling for each physical uplink control channel (PUCCH) format. The number of repeated transmissions for PUCCH format i can be independently configured. i can be 1, 3, or 4. A terminal can repeatedly transmit a PUCCH format in slots. In this case, the PUCCH format can be transmitted using the same time resource in each slot.

[0091] Uplink control information (UCI) types can be classified according to the type of information included in the UCI. UCI can include at least one of scheduling request (SR), L1-RSRP (reference signal received power), HARQ-ACK, or channel state information (CSI). In embodiments, UCI and UCI type can be used interchangeably. In a repeated transmission operation of UCI, only one UCI type can be transmitted. To support this operation, the priority of UCI types can be defined in a technical specification. One UCI type can be selected, and a PUCCH including one UCI type can be repeatedly transmitted. In this case, the terminal can assume that no other UCI types are transmitted before the transmission of the corresponding UCI type is completed. To support this operation, the base station can instruct the terminal to transmit UCI (e.g., SR or HARQ-ACK) after the PUCCH transmission is completed. The latency for such UCI transmissions can be long, and this latency can act as a scheduling constraint for the base station.

[0092] When "transmission of HARQ-ACKs in the same slot (or the same sub-slot)" or "PUCCH time resources indicated by DCI and / or RRC message allocating PDSCH (physical downlink shared channel) overlap each other," the terminal may generate the HARQ codebook so that the HARQ codebook is transmitted in one PUCCH (e.g., one PUCCH time resource). HARQ-ACK bits in the HARQ codebook may be arranged according to an order defined in the technical specification. Information bits may be generated by the above-described operation. The terminal may generate coded bits by performing an coding operation.

[0093] Reed-Muller codes or polar codes can be used in encoding operations. The code rate applied in encoding operations can be indicated by higher-layer signaling. For example, in the PUCCH format, a single value can be the code rate and can be indicated to the terminal.

[0094] One codeword can be mapped to one PUCCH. In a PUCCH repeated transmission operation, one UCI type can be generated as a codeword. When a PUCCH is transmitted once, information bits of one UCI type or two or more UCI types can be concatenated, and the terminal can generate one codeword by performing the same encoding operation on the information bits. When a Reed-Muller code or a polar code is used, performing a soft combining operation may be difficult in implementation. Therefore, even when a PUCCH is repeatedly transmitted, the same codeword can be transmitted, and the base station can perform a chase combining operation on the same codeword. The encoded bits or codeword can mean a bit string in which multiple code blocks are concatenated. A modulation operation can be performed on the codeword, and the result of the modulation operation can be mapped to an RE.

[0095] Meanwhile, identical UCI types may be considered different information. Identical UCI types that are considered different information can be mapped. For example, UCIs may be created to support traffic with different priorities. UCIs supporting eMBB traffic (e.g., SR or HARQ-ACK) may be considered distinct information from UCIs supporting URLLC traffic (e.g., SR or HARQ-ACK). In this case, even if the UCI types are identical, UCIs with the same UCI type may be distinguished as different information.

[0096] Encoded UCI can be mapped to PUCCH. The same preprocessing scheme (e.g., spatial information, spatial relations) can be maintained during PUCCH transmission. Alternatively, the use of different preprocessing schemes for each PUCCH can be permitted through RRC signaling from the base station.

[0097] To support URLLC traffic, it may be desirable for a terminal to perform frequent reception operations on downlink (DL) resources and / or frequent transmission operations on uplink (UL) resources. In a time division duplex (TDD) system, a terminal may operate based on a half-duplex scheme. Therefore, the support time for DL ​​traffic and / or UL traffic may increase depending on the slot pattern. On the other hand, in a frequency division duplex (FDD) system, a terminal can utilize DL resources and UL resources. Therefore, the above-described problem in a TDD system may not occur in an FDD system. An FDD system can use two or more carriers. If two or more serving cells are configured for a terminal in a TDD system, the terminal can utilize DL resources and UL resources.

[0098] In a communication system including at least one carrier to which FDD is applied (hereinafter referred to as an "FDD carrier"), there may be no problem with the delay time of the terminal. In a communication system including only carrier(s) to which TDD is applied (hereinafter referred to as "TDD carrier(s)"), there may be a problem with the delay time of the terminal. To solve the above problem, slots in TDD carriers may be configured according to different patterns.

[0099] Carrier aggregation (CA) can be configured in the UE, and PCell and SCell(s) can be activated. Depending on whether a common search space (CSS) set is configured in the cell, the cell can be classified as a PCell or SCell. For example, a CSS set can be configured in the PCell, and a CSS set can be unconfigured in the SCell. To reduce latency in a communication system supporting URLLC traffic, slots with different patterns can be configured and / or indicated to the UE.

[0100] Transmission of eMBB or URLLC traffic can be supported in licensed and / or unlicensed bands. Carrier(s) in the licensed band or carrier(s) in the unlicensed band can be utilized independently. Alternatively, depending on the base station configuration, carrier(s) in the licensed band and carrier(s) in the unlicensed band can be utilized together through frequency aggregation.

[0101] In an embodiment, two or more terminals may receive data from one or more TRPs and transmit data to one or more TRPs. It may be assumed that one base station or one server performs management operations and / or scheduling operations for one or more TRPs among the plurality of TRPs. The TRPs may be directly connected. Alternatively, the TRPs may be connected via a base station. The above-described connection may be a connection according to an Xn interface or a wireless interface (e.g., an interface of 3GPP NR).

[0102] Shadow regions may exist between the areas supported by TRPs. TRPs can resolve shadow regions through cooperative transmission. Cooperative transmission can be performed on terminals located between TRPs. Even in the absence of shadow regions, numerous TRPs (e.g., base stations) can be installed to transmit and receive large amounts of data, and the quality of the wireless link can be improved by having multiple TRPs.

[0103] Depending on the cooperative transmission and reception of TRPs, communication methods can be classified into dynamic point selection (DPS) and joint transmission (JT). For a specific set of physical resource blocks (PRBs), DPS may be a method in which a terminal receives data through a single TRP, and JT may be a method in which a terminal receives data through two or more TRPs. Dynamic point blanking (DPB) may be a type of JT. When DPB is used, a terminal may not receive data from some TRPs and may receive data from the remaining TRPs. JT can be classified into coherent JP and noncoherent JP. Depending on whether a coherent combining operation is performed on signals received from TRPs, either coherent JP or noncoherent JP may be used.

[0104] Depending on the latency and traffic capacity of the backhaul network to which base stations or TRPs are connected, TRPs may or may not participate in real-time cooperative transmission and reception. A terminal may support JT based on a single DCI (e.g., single DCI (sDCI)). Alternatively, a terminal may support JT based on multiple DCIs (e.g., multi-DCI (mDCI)).

[0105] When using sDCI, a terminal can transmit and receive data with TRPs. When using sDCI, it may be desirable for TRPs to cooperate without delay through a backhaul network. When using mDCI, a terminal can transmit and receive data with some TRPs. If a terminal transmits and receives data with other TRPs, it may be difficult for the other TRPs to cooperate in real time through the backhaul network. It may be desirable for other TRPs to be allocated semi-fixed resources.

[0106] A CORESET (control resource set) pool index can be used to identify a TRP. A CORESET pool can be a collection of CORESETs, and the transmission configuration indication (TCI) state applied to each CORESET can be independently indicated to the UE through RRC signaling and / or MAC control element (CE) signaling. A CORESET pool index may not necessarily correspond to a TRP. Specifically, a TRP can be divided into a transmission point (TxP) and a reception point (RxP). A CORESET pool index can correspond to an RxP. For example, an Rx beam for a TxP can be derived from a TCI state, and uplink signals / channels scheduled from DCIs discovered in CORESETs belonging to a CORESET pool indicated by a single CORESET pool index can be interpreted as being received by the same RxP.

[0107] For a terminal to benefit from coherent combining, the TRPs for that terminal must be synchronized to a certain degree, and CSI reports for those TRPs must be shared. If this is not the case, performing noncoherent combining may provide performance advantages.

[0108] If the terminal is mounted on a vehicle, constraints on its size and weight can be relaxed. If the terminal is carried by a person, portability can be considered.

[0109] To expand the signal coverage area, small cells or Integrated Access Backhaul (IAB) nodes can be deployed. The transmission capacity of small cells or IAB nodes may vary depending on the quality of the backhaul link. Securing a backhaul network can be costly. As an alternative to the above embodiment, a wireless relay device can be deployed, which can transmit high-quality signals to terminals. Wireless relay devices can be categorized into several types depending on the method of signal transmission. A wireless relay device supporting multiple functions can exhibit performance similar to that of a base station. A wireless relay device supporting fewer functions can be deployed at a lower cost. In the present disclosure, a wireless relay device can perform the function of forming a beam to terminals and the minimum function of transmitting data. A base station can transmit wireless signals to control the wireless relay device. Appropriate parameters can be set for the wireless relay device based on the wireless signals.

[0110] In this embodiment, transmission of a channel may mean transmission of a message, data, signal, and / or information on the channel, and reception of a channel may mean transmission of a message, data, signal, and / or information on the channel. The channel may be a physical downlink control channel (PDCCH), a physical downlink shared channel (PDSCH), a physical uplink control channel (PUCCH), a physical uplink shared channel (PUSCH), a physical random access channel (PRACH), a physical sidelink broadcast channel (PSBCH), a physical sidelink control channel (PSCCH), a physical sidelink shared channel (PSSCH), and / or a physical sidelink feedback channel (PSFCH).

[0111] In a communication system supporting TDD, downlink (DL) communication and uplink (UL) communication can be performed in different time resources. The ratio between the DL time, in which DL communication is performed, and the UL time, in which UL communication is performed, can be determined based on the ratio of traffic (e.g., DL traffic and / or UL traffic). For example, in an NR system, since the amount of DL traffic is greater than the amount of UL traffic, more DL slots can be allocated than UL slots. For example, slots (e.g., slot patterns) can be configured to repeat a DDDSU pattern. D can denote a DL slot, S can denote a special slot including DL symbol(s), FL (flexible) symbol(s), and UL symbol(s), and U can denote a UL slot. The arrangement order of symbols in an S slot can be DL symbol(s)-FL symbol(s)-UL symbol(s). The base station can instruct or set the slot pattern to the terminal(s) through signaling (e.g., RRC signaling). The base station can indicate some FL symbol(s) among the FL symbols set by the RRC signaling as DL symbol(s) or UL symbol(s). The some FL symbol(s) can be indicated as DL symbol(s) or UL symbol(s) through DCI.

[0112] A terminal located at the edge of a cell may repeatedly transmit a UL signal / channel to transmit UL traffic to a base station. In this case, the signal to interference plus noise ratio (SINR) may be improved and the block error rate (BLER) may be reduced at the base station. In the present disclosure, a UL signal / channel may refer to a UL signal and / or a UL channel, and a DL signal / channel may refer to a DL signal and / or a DL channel. The base station may instruct a terminal to repeatedly transmit a UL signal / channel, and the terminal may repeatedly transmit the UL signal / channel based on the instruction of the base station. The base station may instruct a terminal to repeatedly transmit a DL signal / channel, and the terminal may repeatedly receive the DL signal / channel based on the instruction of the base station. If UL slots do not occur frequently, a significant delay may occur for the terminal to obtain sufficient UL slots for repeated transmission. For example, if "the DDDSU pattern is set in the terminal and the SCS (subcarrier spacing) is 30 kHz," UL slots may occur every 2.5 ms (milliseconds). In this case, the time required for four repetitions of the UL signal / channel may be 10 ms.

[0113] To reduce the above time delay, a method of improving the frequency shape of the slot may be considered. The base station may perform full duplex communication. The frequency domain for the DL symbol (or FL symbol) of the DL slot (or DL ​​slot and S slot) may be divided into subbands. The base station may perform a transmission operation of a DL signal / channel or a reception operation of an UL signal / channel in some subbands of the DL slot (e.g., a DL symbol or an FL symbol). Although the terminal performs half-duplex communication, the terminal may perform a transmission operation of an UL signal / channel in the DL slot (e.g., a DL symbol or an FL symbol). A symbol capable of DL communication and UL communication may be referred to as an SBFD (subband full duplex) symbol. The SBFD symbol may be referred to as an SD symbol for convenience. In other words, in the present disclosure, the SD symbol may mean an SBFD symbol. SD may be an abbreviation for SBFD. An SD symbol can be interpreted as an SD resource, and an SBFD symbol can be interpreted as an SBFD resource. A base station can configure an SD symbol and / or a non-SD symbol to a terminal through signaling. The terminal can receive configuration information of the SD symbol and / or the non-SD symbol from the base station. The configuration information of the SD symbol can be SBFD configuration information. The configuration information of the non-SD symbol can be UL-DL configuration information. A non-SD symbol can include a UL symbol, a DL symbol, and / or an FL symbol. The UL symbol, the DL symbol, and / or the FL symbol can be indicated (e.g., configured) based on the UL-DL configuration information. DL communication or UL communication can be performed in a non-SD symbol. A non-SD symbol can be interpreted as a non-SD resource or an ND (non-SD) resource. The SBFD configuration information and the UL-DL configuration information can be included in system information (e.g., SIB1).

[0114] Since DL and UL communications are performed within a single SD symbol (e.g., within the same time resource), a guard band may be introduced. The bandwidth of the guard band may vary depending on the level of interference at the base station. When different antenna arrays are used, coupling between DL and UL communications may be reduced. If there is little coupling between DL and UL communications, a guard band may be unnecessary or a small amount of bandwidth may be required for the guard band. In this case, a guard band may not be allocated separately. Alternatively, a small number of PRBs may be allocated for the guard band.

[0115] When there is little coupling between DL communication and UL communication, a separate Rx filtering operation or Rx processing operation may be performed at the base station, but a separate Tx filtering operation or Tx processing operation may not be necessary at the terminal. The filtering operation may be an RF (radio frequency) filtering operation. When an RF filtering operation is performed, spectral emission (e.g., out-of-band emission (OOB) or adjacent channel leakage ratio (ACLR)) affecting adjacent PRB(s) can be reduced, and saturation of RF components can be prevented.

[0116] The DL and UL subbands can have different frequencies. If leakage occurs, the analog-to-digital converter (ADC) can saturate, causing small signals to be ignored. Base stations can appropriately arrange shielding between antenna arrays or apply signal processing methods. Base stations can also allocate guard bands with smaller bandwidths.

[0117] FIG. 3 is a conceptual diagram illustrating a first embodiment of a subband filtering mask for a DL subband and an UL subband in an SD symbol.

[0118] Referring to FIG. 3, a power spectral density or spectrum mask for DL-related filtering and / or UL-related filtering may be illustrated. DL-related filtering may be performed at a base station, and UL-related filtering may be performed at a terminal. A UL subband may be located at the center of a carrier, and two DL subbands may exist. A DL frequency band may be divided into two DL subbands by the UL subband. In another example, two or more UL subbands may exist, and DL subbands may exist in the remaining frequency band.

[0119] The base station may not perform DL-related filtering by additionally considering the locations of the DL subbands and / or UL subbands. The terminal may perform UL-related filtering by considering the locations of the UL subbands.

[0120] In order to add (e.g., transmit) a UL signal / channel while minimizing the number of UL slots in a slot pattern, an SD symbol may be introduced. A base station may instruct or configure repeated transmission of a UL signal / channel to a terminal located at a cell edge. The terminal may determine that repeated transmission of the UL signal / channel is required based on the instruction or configuration of the base station. Scheduling information for allocating a PUSCH / PUCCH may include a repetition factor for time resources. The terminal may determine the repetition factor included in the scheduling information. The repetition factor may indicate n repeated transmissions of the PUSCH / PUCCH. n may be a natural number. One repeated transmission may mean one transmission of the PUSCH / PUCCH. If the repetition factor is not instructed to the terminal (e.g., if the scheduling information does not include a repetition factor), the terminal may transmit the PUSCH / PUCCH once. In the present disclosure, PUSCH / PUCCH may refer to PUSCH and / or PUCCH. Scheduling information may include resource allocation information, resource activation information, and / or resource deactivation information. Scheduling information may be included in an RRC message, a MAC message (e.g., MAC CE), and / or a PHY message (e.g., DCI).

[0121] To extend the reach of UL signals / channels, a base station can instruct a terminal to perform demodulation-reference signal (DM-RS) bundling via signaling (e.g., RRC signaling). The terminal can determine that DM-RS bundling is required based on the signaling from the base station. Performing DM-RS bundling can mean "maintaining power consistency / phase continuity in repeated PUSCH / PUCCH transmissions." While power consistency / phase continuity is maintained, the base station can perform channel estimation operations simultaneously. Therefore, the reception performance of PUSCH / PUCCH at the base station can be improved. Power consistency / phase continuity can mean power consistency and / or phase continuity. Power consistency / phase continuity can mean coherence (e.g., time coherence).

[0122] The base station can allocate SD symbols. The order of symbols in a slot can be DL symbol-SD symbol-UL symbol. An FL symbol can be placed between a DL symbol and an SD symbol. Alternatively, an FL symbol can be omitted between a DL symbol and an SD symbol. An FL symbol can be placed between an SD symbol and an UL symbol. Alternatively, an FL symbol can be omitted between an SD symbol and an UL symbol.

[0123] FIG. 4 is a conceptual diagram illustrating a first embodiment of a slot pattern (e.g., a TDD slot pattern) including SD symbols.

[0124] Referring to FIG. 4, SD symbol(s) may be positioned after DL symbol(s), and UL symbol(s) may be positioned after SD symbol(s). The frequency band for SD symbol(s) may be divided into DL subbands and UL subbands.

[0125] The UL bandwidth for SD symbols may differ from the UL bandwidth for UL symbols. The base station may apply different filtering operations to SD and UL symbols. Optionally, the terminal may apply different filtering operations to SD and UL symbols (or DL ​​symbols). The application of different filtering operations may mean that different filtering operations are applied based on the boundary between SD and UL symbols. In this case, power consistency / phase continuity may not be maintained during the transmission and reception of UL signals / channels.

[0126] The shape of the base station for implementing the SBFD operation can be given in various ways, and FIGS. 5 to 8 can show embodiments of the base station.

[0127] Figure 5 illustrates a first embodiment of a base station implementing a TDD system.

[0128] Referring to FIG. 5, a base station can have K Tx chains and K Rx chains. The Tx chains and the Rx chains can be connected to an array having L element antennas (e.g., a shared-Tx / Rx antenna array). Each of K and L can be a natural number. In a DL resource, the shared-Tx / Rx antenna array can be connected to a Tx chain, and in a UL resource, the shared-Tx / Rx antenna array can be connected to an Rx chain. In other words, the shared-Tx / Rx antenna array can be switched according to time resources and can be utilized in both DL and UL.

[0129] Figure 6 illustrates a first embodiment of a base station implementing SBFD operation.

[0130] Referring to Fig. 6, a base station may have K Tx chains and K Rx chains, and a panel group may be formed by L element antennas. Each of K and L may be a natural number. Panel group #1 utilized in DL resources and panel group #2 utilized in UL resources may be distinguished from each other. In SD resources, both panel group #1 and panel group #2 may be utilized.

[0131] From the perspective of base station transmit power, the transmit power in a DL symbol may be the same as the transmit power in an SD symbol. Since the DL bandwidth of an SD symbol is narrower than that of a DL symbol, the power density (e.g., energy per resource element (EPRE)) in an SD symbol may be greater than the power density (e.g., EPRE) in a DL symbol.

[0132] Figure 7 illustrates a second embodiment of a base station implementing SBFD operation.

[0133] Referring to FIG. 7, a base station can have K / 2 Tx chains and K / 2 Rx chains, and a panel group can be formed with L / 2 element antennas. Each of K and L can be a natural number. Panel group #1 and panel group #2 can be utilized in DL resources and / or UL resources. In DL resources, both panel group #1 and panel group #2 can be connected to a Tx chain, and in UL resources, both panel group #1 and panel group #2 can be connected to an Rx chain. In SD resources, panel group #1 can be connected to a Tx chain, and panel group #2 can be connected to an Rx chain.

[0134] From the perspective of base station transmit power, the transmit power in a DL symbol may differ from that in an SD symbol. Since the DL bandwidth of an SD symbol is narrower than that of a DL symbol, the power density (e.g., EPRE) in an SD symbol may be the same as the power density (e.g., EPRE) in a DL symbol.

[0135] Figure 8 illustrates a third embodiment of a base station implementing SBFD operation.

[0136] Referring to FIG. 8, a base station can have K / 2 Tx chains and K / 2 Rx chains, and a panel group can be formed by L / 2 element antennas. Each of K and L can be a natural number. Panel group #1 can be utilized in DL resources, and panel group #2 can be utilized in UL resources. In DL resources and SD resources, panel group #1 can be connected to a Tx chain, and in SD resources and UL resources, panel group #2 can be connected to an Rx chain.

[0137] From the perspective of base station transmit power, the transmit power in a DL symbol may differ from that in an SD symbol. Since the DL bandwidth of an SD symbol is narrower than that of a DL symbol, the power density (e.g., EPRE) in an SD symbol may be the same as the power density (e.g., EPRE) in a DL symbol.

[0138] To handle the traffic demand of a terminal, a base station can establish an RRC connection with the terminal. An unspecified number of terminals can select or reselect a base station using a cell search procedure. The base station (or cell) can periodically transmit a synchronization signal and / or system information. System information can be divided into a master information block (MIB) and a system information block (SIB). SIBs can be classified as SIB1, SIB2, etc. A terminal can camp on a specific base station (or cell) using the MIB and SIB. The synchronization signal and MIB can be combined, and a synchronization signal block (SSB) including the synchronization signal and MIB can be transmitted. In the examples below, SIB may mainly refer to SIB1, but SIB may not necessarily be interpreted as SIB1. Depending on the context, SIB may be interpreted as SIBx (x=1, 2, 3, etc.).

[0139] When DL traffic to be transmitted to a terminal occurs in a network or base station, the network or base station can transmit a paging message to an unspecified number of terminals to search for the terminal and establish an RRC connection with the terminal. The terminal can receive the paging message and perform a random access procedure for the network or base station, and can establish an RRC connection with the network or base station through the random access procedure.

[0140] When UL traffic to be transmitted from a terminal to a network or base station occurs, the terminal can perform a random access procedure to establish an RRC connection with the base station (or network) on which the terminal is camping.

[0141] After the RRC connection between the terminal and the base station is established, the terminal can operate based on the control of the base station (e.g., serving cell). For example, the terminal can transmit and receive data with the base station.

[0142] Because the base station cannot monitor the status of the camping terminals, its power may be wasted by the SSB and / or SIB that it periodically transmits. For example, a base station operating in normal mode may transmit SIBs at a predetermined interval. A base station operating in low-power mode may transmit SIBs at a longer interval. Alternatively, a base station operating in low-power mode may not transmit SIBs at all.

[0143] NES (network energy saving)

[0144] On demand SIB1

[0145] In the embodiments below, SSB may be transmitted periodically, but SIB may not be transmitted.

[0146] To conserve power, a base station can transmit a SIB at the request of a terminal(s). The SSB can be transmitted periodically, and the MIB included in the SSB can include separate information indicating that the SIB (e.g., SIB1) is not being transmitted. Alternatively, the MIB included in the SSB can implicitly indicate that the SIB is not being transmitted.

[0147] Alternatively, the control channel scheduling the SIB may not be transmitted in the CORESET and / or Type0-PDCCH CSS set. The CORESET and / or Type0-PDCCH CSS set may not be configured in the terminal.

[0148] In an embodiment of the present disclosure, the MIB may include information indicating whether the SSB is a cell-defining (CD)-SSB or a non-cell-defining (NCD)-SSB. The terminal may identify a CS-SSB or a NCD-SSB based on the information included in the MIB. The information included in the MIB may be ssb-SubcarrierOffset. The MIB may include information for setting CORESET 0 and search space 0. An index may be indicated by the MIB, and the index (e.g., one index) may mean (e.g., indicate) a multiplexing pattern of the SSB and the CORESET, a bandwidth of the CORESET, a number of symbols of the CORESET, and / or an RB offset. If the SSB and the CORESET are not multiplexed, a cell may not be defined. An SSB that is not multiplexed with the CORESET (e.g., an SSB for an undefined cell) may be referred to as an NCD-SSB. k SSB If the value of is less than a certain value, the terminal k SSB The SSB associated with can be classified as CD-SSB and the Type0-PDCCH CSS set can be searched. k SSB If the value of falls within the remaining range, the terminal is k SSB The SSB associated with can be classified as NCD-SSB and the Type0-PDCCH CSS set may not be searched. In this case, the terminal may perform the cell reselection procedure again. k SSB may mean the frequency offset between the SSB and the CORESET (e.g., the CORESET for scheduling SIB1, the CORESET associated with the Type 0-PDCCH CSS set). Or k SSB may indicate that reception of another SSB is required to acquire SIB1.

[0149] The base station can transmit NCD-SSB in a mode that does not transmit SIB1 (hereinafter referred to as “SIB non-transmission mode”). The base station can transmit CD-SSB in a mode that transmits SIB1 (hereinafter referred to as “SIB transmission mode”). In SIB non-transmission mode, SIBx may not be transmitted. In SIB transmission mode, SIBx may be transmitted. x may be a natural number.

[0150] In an embodiment of the present disclosure, a terminal can recognize the presence or absence of a CORESET DM-RS. If a CORESET DM-RS is present, the terminal can assume that SIB1 is transmitted. If a CORESET DM-RS is absent, the terminal can assume that SIB1 is not transmitted. In this case, the terminal can perform a cell reselection procedure again. The CORESET DM-RS may be a DM-RS used for demodulation of DCI transmitted in the CORESET.

[0151] In an embodiment of the present disclosure, k SSB The value of can be used as a counter. When the counter expires, k with a range meaning NCD-SSB SSB can be changed to a value in the range that means CD-SSB. The terminal can use the value of the counter to predict the time at which the base station transmits SIB1.

[0152] According to the above methods, the base station may or may not transmit SIB as needed. It may be desirable to measure the conditions for changing from SIB non-transmission mode to SIB transmission mode. The terminal can request a change in SIB transmission mode by transmitting a UL DRS (discovery signal or discovery reference signal) or PRACH (e.g., RA preamble) to the base station.

[0153] To transmit UL DRS, it may be necessary to establish an RRC connection between the terminal and the base station or use PRACH (e.g., PRACH transmission, PRACH configuration). The base station may transmit UL DRS configuration information (e.g., resource configuration, other configuration) to the terminal. The terminal may receive UL DRS configuration information from the base station. To transmit PRACH, it may be necessary to indicate RO (RA (random access) occasion) configuration information to the terminal. A method using PRACH will be described below.

[0154] To transmit a PRACH, a terminal may generate a preamble (e.g., an RA preamble) based on a sequence defined in a technical specification and / or an information element (IE) (e.g., configuration information) included in SIB1, and may allocate appropriate transmission power for transmission of the preamble. The terminal may derive information of an RO set from another IE included in SIB1, select a specific RO from the RO set, and transmit a PRACH (e.g., a preamble, an RA preamble, a PRACH preamble) in the selected RO. The base station may transmit RACH configuration information for deriving a PRACH and / or an RO to an unspecified number of terminals. An RO set may include one or more ROs. In the present disclosure, an RO set and an RO may be used interchangeably. An RO set may be interpreted as an RO set or an RO depending on the context. An RO may be interpreted as an RO or an RO set depending on the context. In the present disclosure, the RO set may mean a set of ROs. In other words, the RO set and the set of ROs may have the same meaning.

[0155] In an embodiment of the present disclosure, a base station may transmit SIB1 at a long period (e.g., a very long period), and among the terminals camped on the base station, some terminals may receive SIB1, and some terminals may obtain RACH configuration information based on SIB1. The RACH configuration information may be included in system information (e.g., SIB1). If some terminals transmit PRACH, the base station may transmit SIB1 at a short period. If PRACH is received from a terminal, the base station may adjust the transmission period of the SIB (e.g., SIB1). The above operation may refer to a method for changing the transmission mode of the SIB.

[0156] To request (e.g., trigger) SIB1 transmission, a SIB1 transmitted at a long period may contain simplified information. In other words, sufficient information for performing random access may not be included in a SIB1 with a long period, and information for deriving RACH configuration information for requesting SIB1 and / or a set of ROs associated with a PRACH may be included in a SIB1 with a long period. A SIB1 with a long period may be a simplified SIB1. Alternatively, a SIB1 with a long period may be separately defined information. A UE may transmit a PRACH at a specific RO. After receiving a PRACH from a UE, the base station may transmit a SIB1 at a short period.

[0157] In an embodiment of the present disclosure, a base station may transmit to unspecified terminals a separate DCI format containing sufficient information to derive a PRACH sequence and RO set derived from RACH configuration information. The proposed DCI format may or may not schedule a PDSCH.

[0158] The proposed DCI format can be scrambled by a SI (system information)-RNTI (radio network temporary identifier) ​​or a separate RNTI. For example, the RNTI (e.g., SI-RNTI, separate RNTI) can be a value derived based on the time resources (e.g., slots, symbols) of the CORESET / search space set in which the DCI format is transmitted.

[0159] The resource receiving the proposed DCI format may be a Type 0-PDCCH CSS set. The transmission period of the DCI format may be two radio frames. Alternatively, a separate transmission period for the DCI format may be configured in the terminal.

[0160] The proposed DCI format may include at least one of preamble information, UL symbol location information, RO set information, or SSB index. Since each PRACH and RO set represents a PRACH and RO set for triggering SIB1 transmission, the DCI format may include simplified information compared to SIB1. Since SIB1 transmission is triggered using the OOK (on / off shift keying) method, the base station does not need to resolve collisions between unspecified UEs. Therefore, the preamble index may be indicated by the DCI (e.g., the DCI format).

[0161] A PRACH configuration index may indicate an UL resource on which an RO may be transmitted. The PRACH configuration index may be included in a RACH generic configuration (e.g., RACH-ConfigGeneric). In other words, a PRACH configuration index may be associated with a RACH generic configuration. The presence of one or more PRACH configuration indices may mean that one or more RACH generic configurations are configured (e.g., indicated) to the UE. For example, if two PRACH configuration indices are configured (e.g., indicated) to the UE, one RACH generic configuration associated with one PRACH configuration index may include information (e.g., time and / or frequency resource information) of a set of ROs (RACH occasions) configured in an ND resource (e.g., UL resource and / or FL resource), and another RACH generic configuration associated with another PRACH configuration index may include information (e.g., time and / or frequency resource information) of a set of ROs configured in an SD resource.

[0162] The RO set configured in the ND resource may be referred to as a legacy RO set. The RO set configured in the SD resource may be referred to as an additional RO set. The RO set may be configured across the ND resource and the SD resource. The RO set configured in the ND resource and the SD resource may be referred to as a special RO set. The special RO set may be configured based on the two RACH general configurations described above. The special RO set may be a type of the additional RO set. In other words, the special RO set may belong to the additional RO set. The RACH configuration information may include one RACH general configuration associated with one PRACH configuration index and an additional RACH general configuration associated with the additional PRACH configuration index. In other words, the RACH configuration information may include one or more RACH general configurations associated with one or more RACH configuration indices.

[0163] The base station and / or the terminal can derive a valid RO (e.g., a valid RO set) by deriving the position of the UL symbol using the pattern information of the slot. The base station can instruct (e.g., configure) the frequency resources of the ROs to the terminal. The base station and / or the terminal can check the number of FDM-capable ROs in the same time resource based on the frequency resources of the ROs. Based on the above operations, the terminal can derive the RO set and select an RO corresponding to the SSB within the RO set. The information required for the above operations can be derived from the RACH configuration information. The information required for the above operations can be acquired based on the information included in SIB1. For PRACH / RO configuration for changing the transmission mode of SIB1, only simplified information may be required.

[0164] The proposed DCI (e.g., DCI format) may include information indicating that SIB1 is to be transmitted or that SIB1 is being transmitted. The above-described information may be derived based on the values ​​of a separate information field in the DCI or existing information field(s). For example, the information indicating that SIB1 is to be transmitted may be expressed as a counter. When the counter expires, the UE may expect SIB1 to be transmitted. A time window in which SIB1 is transmitted may be configured. The time window configuration information may include information on the length of the time window (e.g., 160 ms (milliseconds)), a radio frame offset, and / or a subframe offset. The subframe offset may indicate the starting point of the time window. For example, the starting point of the time window may be after the subframe offset from the subframe boundary. If one information field in the DCI has the first value, the terminal can expect that "SIB1 will not be transmitted in the time window to which the DCI was received, but SIB1 will be transmitted in the time window following the time window." Based on the above information, the terminal may not transmit PRACH even if SIB1 is not received, and may wait for the next time window for SIB1.

[0165] synchronization signal (SS)-reference signal received power (RSRP) and reference signal received quality (SS-RSRQ)

[0166] The concept of SS-RSRP and SS-RSRQ

[0167] SS-RSRP can refer to the value of RSRP measured using SSB. The terminal can measure SS-RSRP in RRC idle mode or RRC inactive mode.

[0168] SS-RSRP may be the average received power of the secondary synchronization signal (SSS) in the RE (resource element)(s). SS-RSRP may be measured in a specific time interval. The specific time interval may be indicated to the UE by the SSB measurement timing configuration (SMTC). In other words, the base station may transmit the SMTC to the UE. The UE may receive the SMTC from the base station and identify the specific time interval based on the SMTC. When SS-RSRP is used as L1-RSRP, L1-RSRP may be measured not only in the time interval indicated by the SMTC but also in other time intervals. The time interval indicated by the SMTC may be referred to as the SMTC interval.

[0169] SS-RSRP may refer to the measurement results of SSS, PBCH DM-RS, and / or CSI-RS. To use CSI-RS for SS-RSRP measurements, separate upper-layer signaling may be required for the terminal. When multiple signals are used, the measured power may be the average of the measurements of the multiple signals.

[0170] If SS-RSRP is not used as L1-RSRP, CSI-RS may not be additionally considered. SS-RSRP may be a measurement result for signals corresponding to the SSB index and the physical cell identifier (PCI). If SS-RSRP is not used as L1-RSRP, if a specific SS / PBCH block is designated by upper layer signaling, SS-RSRP may be measured using the specific SS / PBCH block.

[0171] When SS-RSRP is used as L1-RSRP, the UE must operate in RRC connected mode to measure SS-RSRP (e.g., L1-RSRP). When SS-RSRP is not used as L1-RSRP, a UE in RRC disconnected mode (e.g., RRC idle mode or RRC inactive mode) can measure SS-RSRP.

[0172] SS-RSRQ may refer to a value measured using SSB for RSRQ. SS-RSRQ may be defined as a ratio of SS-RSRP and NR carrier RSSI (received signal strength indicator). For example, SS-RSRQ may be N × SS-RSRP / NR carrier RSSI. SS-RSRP may be obtained based on the above-described method. The value of N may represent the number of RBs (resource blocks) included in the bandwidth for measuring NR carrier RSSI. Measurements of SS-RSRP and NR carrier RSSI may be performed in the same RBs. N may be a natural number.

[0173] NR carrier RSSI may be an average of power measured across N RBs in a specific OFDM symbol. OFDM symbol(s) belonging to the measurement time resource may be utilized for measuring NR carrier RSSI. The OFDM symbol may be referred to as a symbol for convenience. If SS-RSRQ is used for cell selection, the time resource for measuring SS-RSRQ may not be limited. If SS-RSRQ is not used for cell selection, the time resource for measuring NR carrier RSSI may be limited to the SMTC period (e.g., the time period indicated by SMTC).

[0174] The terminal can use higher layer signaling to indicate (e.g., set) separate parameters (e.g., measurementSlots) to the terminal. If the measurement gap (MG) is not used, the NR carrier RSSI can be measured using the slot(s) indicated by measurementSlots among the slots belonging to the SMTC period and the OFDM symbols defined in Table 1. Table 1 can indicate the NR carrier RSSI measurement symbol(s). If the MG is used, the NR carrier RSSI can be measured using the slot(s) indicated by measurementSlot and / or the overlapping time resources (e.g., slots and / or OFDM symbols) between the SMTC period and the MG.

[0175] MeasurementSlots may indicate slot(s) in which a terminal can measure NR carrier RSSI. The value of MeasurementSlots set by upper layer signaling may have the form of a bit string. Each slot belonging to an SMTC section may be associated with one bit of MeasurementSlots. A bit set to a first value (e.g., 1) among the bits of MeasurementSlots may indicate that measurement of NR carrier RSSI is possible in the slot associated with the bit. The length of a slot may vary depending on the subcarrier spacing (SCS). A slot that completely belongs to the SMTC section may be used for measurement of NR carrier RSSI. In other words, if a part of a slot belongs to the SMTC section, the slot may not be used for measurement of NR carrier RSSI. If the SCS of the PCell (primary cell) and SCell (secondary cell) set in a terminal supporting CA (carrier aggregation) are different, slots across the boundary of the SMTC section may exist.

[0176] The endSymbol may indicate the range of OFDM symbols within a slot in which NR carrier RSSI can be measured. The slot may be a slot in which NR carrier RSSI can be measured. The terminal may measure NR carrier RSSI in the range from OFDM symbol 0 within the slot to OFDM symbol k indicated by the endSymbol. Referring to Table 1 below, multiple OFDM symbols may be used for measuring NR carrier RSSI. The same OFDM symbols may be used for measuring NR carrier RSSI in all slots in which NR carrier RSSI measurement is performed.

[0177]

[0178] In intra-frequency SS-RSRQ measurements, NR carrier RSSI may be measured using a timing reference at the same frequency (e.g., frequency layer) as the serving cell. In inter-frequency SS-RSRQ measurements, NR carrier RSSI may be measured using a timing reference relative to any cell at the target frequency (e.g., target frequency layer). "Unless indicated by higher layer signaling (e.g., SSB is not indicated by higher layer signaling) and MG is not used", NR carrier RSSI may be measured in OFDM symbol(s) belonging to the SMTC interval. "Unless indicated by higher layer signaling (e.g., SSB is not indicated by higher layer signaling) and MG is used", NR carrier RSSI may be measured in OFDM symbol(s) belonging to the overlapping time between the SMTC interval and the MG.

[0179] When a specific SSB is indicated by upper layer signaling, SS-RSRP based on the specific SSB can be measured for SS-RSRQ measurement. A terminal in either RRC connected mode or RRC non-connected mode can measure SS-RSRQ. In other words, SS-RSRQ can be measured not only by a terminal in RRC connected mode but also by a terminal in RRC non-connected mode.

[0180] How to distinguish cell states separately

[0181] According to the proposed method, SS-RSRQ can be measured by considering the ON / OFF state of a cell. For example, SS-RSRQ can be measured in a cell that is ON, and SS-RSRQ can be measured in a cell that is OFF. The UE can measure SS-RSRQ in a cell that is ON and SS-RSRQ in a cell that is OFF by considering SMTC, measurementSlots, endSymbol, and / or NR carrier RSSI. The cell can distinguish and derive SS-RSRQ in the ON state and SS-RSRQ in the OFF state.

[0182] Since there are few DL signals / channels transmitted periodically in cells that are off, the amount of interference or NR carrier RSSI may be small. Due to the DL signals / channels transmitted periodically in cells that are on, the amount of interference or NR carrier RSSI may be relatively large.

[0183] By applying the measurementSlots and endSymbol indicated to the terminal, it may be desirable for the terminal to measure SS-RSRQ on resources belonging to the same state (e.g., on state or off state). Measurement time set 1 may include slot(s) and / or symbol(s) in the on state of the cell. Measurement time set 2 may include slot(s) and / or symbol(s) in the off state of the cell. The transmission period (e.g., reception period) of SSB and the pattern of the on / off state of the cell may not always be aligned. The slot offset for the transmission period of SSB may be different from the slot offset for the pattern of the on / off state of the cell.

[0184] Measurement time sets 1 and 2 can be defined in various ways. For example, measurement time sets 1 and 2 can be defined as time resources for measuring SS-RSRQ in the SMTC interval. For another example, measurement time sets 1 and 2 can be time resources distinguished according to cell status, or can be time resources that do not consider SMTC. SS-RSRQ can be measured in time resources that belong to both measurement time sets 1 and 2 and the SMTC interval.

[0185] According to the proposed method, SS-RSRQ (hereinafter referred to as SS-RSRQ 1) can be measured in a measurement time set 1 associated with an ON state of a cell. SS-RSRQ (hereinafter referred to as SS-RSRQ 2) can be measured in a measurement time set 2 associated with an OFF state of a cell. The terminal can perform a cell selection procedure or a cell reselection procedure based on the size of SS-RSRQ 1 and / or SS-RSRQ 2. The terminal can perform a cell selection procedure or a cell reselection procedure using SS-RSRQ.

[0186] SSB selection

[0187] Below, the methods by which a terminal selects SSB to perform random access will be described.

[0188] A terminal can perform a four-step procedure to perform random access. The terminal can receive SIB1 from a base station and acquire RACH configuration information (e.g., RACH-config) included in SIB1. Based on SIB1, the terminal can derive information related to an initial bandwidth part (BWP) and information related to a slot pattern. For example, based on UL-DL configuration information (e.g., tdd-UL-DL-ConfigurationCommon) included in SIB1, a slot can include DL (downlink) symbols, FL (flexible) symbols, and / or UL (uplink) symbols. A slot configuration based on UL-DL configuration information (e.g., tdd-UL-DL-ConfigurationCommon) can be a semi-static configuration. To measure RSRP for SSB, the UE can assume that the SSB is received in a DL symbol (or FL resource, DL / FL resource, or non-SD symbol). The UE can use the SSB pattern information included in SIB1 to determine the indices of the SSB actually transmitted by the base station (e.g., SSB indices). The SSB pattern information can be used to derive an RO set and / or an SSB-RO mapping. When an SSB-RO mapping operation is performed, one or more SSB indices can be mapped to one RO (e.g., one RO set). Alternatively, one SSB index can be mapped to one or more ROs (e.g., one or more RO sets).

[0189] A base station performing SBFD operation can transmit SSBs on DL resources, FL resources, and / or SD resources. RSRP, which is a measurement result for SSBs with the same SSB index on DL / FL resources, and RSRP, which is a measurement result for SSBs with the same SSB index on SD resources, can be distinguished.

[0190] According to the implementation of the base station (e.g., the embodiments of FIGS. 5, 6, and / or 8), the connection states of the Tx chains and panel groups applied to the DL / FL resources and the SD resources may be the same. It may be assumed that the same Tx beam is applied for RSRP measurement of an SSB with the same SSB index in the DL / FL resources and for RSRP measurement of an SSB with the same SSB index in the SD resources. Since the EPRE is the same in the resources where the SSB is transmitted, there is no need for the terminal to distinguish between the RSRP measurement of an SSB in the DL / FL resources and the RSRP measurement of an SSB in the SD resources.

[0191] Depending on the implementation of the base station (e.g., the embodiment of FIG. 7), the connection states of the Tx chains and panel groups applied to DL / FL resources and SD resources may be different. It may not be assumed that the same Tx beam is applied for RSRP measurement of an SSB with the same SSB index in a DL / FL resource and for RSRP measurement of an SSB with the same SSB index in an SD resource. The EPRE of a resource on which an SSB is transmitted in a DL / FL resource may be the same as the EPRE of a resource on which an SSB is transmitted in an SD resource. If the Tx beams applied for SSB transmission in the DL / FL resource and the SD resource are different, the RSRP of the SSB in the DL / FL resource may be measured differently from the RSRP of the SSB in the SD resource. Depending on the implementation of the base station, if the Tx beam used for SSB transmission remains the same, the terminal can assume the same EPRE in the DL / FL resource and the SD resource, and can measure RSRP without distinguishing between the DL / FL resource and the SD resource.

[0192] To solve the problem caused by the implementation of the base station, the terminal can manage RSRP measured in DL / FL resources and RSRP measured in SD resources differently for SSBs with the same SSB index. The physical layer of the terminal can transmit one or two values ​​to the upper layer of the terminal by performing L3 filtering. When the physical layer of the terminal transmits one value to the upper layer of the terminal, the terminal can derive one value by normalizing the RSRP measured in DL / FL resources and the RSRP measured in SD resources, and can perform L3 filtering on the one value. Alternatively, the terminal can perform L3 filtering first and then derive one value. When the physical layer of the terminal transmits two values ​​to the upper layer of the terminal, one value can be the result of L3 filtering on the RSRP measured in DL / FL resources, and the other value can be the result of L3 filtering on the RSRP measured in SD resources. The base station can transmit an SIB including information on the measurement method performed by the terminal to the terminal. The terminal can receive a SIB from a base station and determine a measurement method indicated by the base station based on information included in the SIB.

[0193] The terminal can select one of the SSBs by comparing RSRPs for the SSBs, check the SSB index of the selected SSB, determine an RO (e.g., a set of ROs) corresponding to the selected SSB index, and transmit an RA preamble in the determined RO. The above-described operation can be utilized for the terminal's RO selection and PRACH transmission in the RA procedure.

[0194] PRACH time resource transition

[0195] The base station can instruct the terminals that the RACH configuration has changed. The RACH configuration can be changed from the first configuration to the second configuration using RRC signaling. The base station can broadcast a paging channel to the terminals camping on the base station. The terminals camping on the base station can be notified of the RACH configuration change by re-receiving the SIB. The base station can re-establish the RRC connection for the terminals being served. The above-described operation can be derived based on information included in the RRC message for configuring the serving cell.

[0196] The RO sets derived from the first configuration and the RO sets derived from the second configuration may differ from each other. For example, the RO sets derived from the first configuration and the RO sets derived from the second configuration may have different association periods.

[0197] According to the proposed method, a base station can change RACH settings to a UE through L1 signaling. The L1 signaling message can be in a UE-specific DCI format or a group-common DCI format. The UE can use a separate RNTI, other than the C-RNTI, to receive the DCI format.

[0198] According to the proposed method, the base station can change the RACH settings through RRC signaling. The terminal can receive a PDSCH containing an RRC signaling message and transmit a HARQ-ACK for the PDSCH. The time elapsed after a preset time from the transmission time of the HARQ-ACK can be regarded as the reference time.

[0199] When the RACH configuration changes from the first configuration to the second configuration, the terminal may perform demodulation and / or decoding operations for the DCI format during a preset time () from the reception time (t) of the DCI format. The terminal may apply SSB-RO mapping for the first configuration before the reference time (t+), and may apply SSB-RO mapping for the second configuration after the reference time (t+). The terminal may assume that the SSB-RO mapping is applied based on the above-described method. t+ may denote a boundary of the reference time.

[0200] According to the proposed method, after the end of the PRACH combining period for the SSB-RO mapping of the first configuration, the PRACH combining period for the SSB-RO mapping of the second configuration may start. The criterion for the transition boundary between the first configuration and the second configuration may be the PRACH combining period.

[0201] The terminal may assume that after receiving the DCI format, the operation (or setting) related to the SSB-RO mapping of the first setting is terminated and then the operation (or setting) related to the SSB-RO mapping of the second setting is started.

[0202] The terminal may assume that the operation (or setting) related to the SSB-RO mapping of the second setting starts after the operation (or setting) related to the SSB-RO mapping of the first setting ends after the demodulation and / or decoding time for the DCI format from the reception time of the DCI format.

[0203] Figure 9 is a flowchart illustrating a communication method between a base station and a terminal.

[0204] Referring to FIG. 9, at S901, the base station may transmit an SSB to the terminal and transmit DCI to the terminal. At S901, the terminal may receive an SSB from the base station and may receive DCI from the base station. At S902, the terminal may perform a parameter recognition / initialization operation based on the SSB and / or DCI received from the base station. At S903, the terminal may select a set of RA resources. At S904, the terminal may transmit Msg1 to the base station based on the selected set. Msg1 may be repeatedly transmitted. Msg1 may be transmitted based on a sweeping scheme (e.g., beam sweeping scheme). At S904, the base station may receive Msg1 from the terminal. If Msg1 is received, the base station may determine that SI (e.g., SIB1) transmission is requested. In S905, the base station may transmit SSB and / or SIB1 to the terminal. In S905, the terminal may receive SSB and / or SIB1 from the base station. In the present disclosure, Msg1 may be interpreted as Msg1 or MsgA depending on the context, and Msg2 may be interpreted as Msg2 or MsgB depending on the context.

[0205] Figure 10 is a flowchart illustrating a communication method between a base station and a terminal.

[0206] Referring to FIG. 10, in S1001, the base station may transmit an SSB to the terminal and transmit SIB1 to the terminal. In S1001, the terminal may receive an SSB from the base station and receive SIB1 from the base station. In S1002, the terminal may perform a parameter recognition / initialization operation based on the SSB and / or SIB1 received from the base station. In S1003, the terminal may select a set of RA resources. In S1004, the terminal may transmit Msg1 to the base station based on the selected set. Msg1 may be repeatedly transmitted. Msg1 may be transmitted based on a sweeping scheme (e.g., beam sweeping scheme). In S1004, the base station may receive Msg1 from the terminal. In S1005, the base station may transmit Msg2 to the terminal in response to Msg1. In S1005, the terminal can receive Msg2 from the base station.

[0207] Figure 11 is a conceptual diagram illustrating the setting of a PRACH association period.

[0208] Referring to FIG. 11, the terminal may receive a DCI format at t0 or t0+. Alternatively, a decoding operation for the DCI format may be completed at t0 or t0+. Alternatively, RRC signaling (e.g., a configuration according to the RRC signaling) may be reflected at t0 or t0+. The configuration of the SSB-RO mapping may not be reflected immediately. In other words, the configuration of the SSB-RO mapping may not be reflected at t0 or t0+. After the end of the PRACH combining period according to the SSB-RO mapping for the first configuration, the PRACH combining period according to the SSB-RO mapping for the second configuration may start. The PRACH combining period according to the SSB-RO mapping for the second configuration may start from the beginning or the middle. Some ROs according to the SSB-RO mapping for the second configuration may not be used. PRACH combining period can mean PRACH combining pattern or PRACH combining pattern period.

[0209] According to another proposed method, the PRACH combining period according to the SSB-RO mapping for the first configuration can be stopped, and the PRACH combining period according to the SSB-RO mapping for the second configuration can be started. For example, the PRACH combining period according to the SSB-RO mapping for the first configuration can be stopped at t0 or t0+, and the PRACH combining period according to the SSB-RO mapping for the second configuration can be started at t0 or t0+. In this case, the number of unused ROs among all ROs according to the SSB-RO mapping for the second configuration can be reduced.

[0210] Figure 12 is a conceptual diagram illustrating the setting of the PRACH combining cycle.

[0211] Referring to FIG. 12, some ROs according to the SSB-RO mapping for the first setting may not be used, and some ROs according to the SSB-RO mapping for the second setting may not be used. The SSB-RO mapping may be changed at t0 or t0+. For example, the SSB-RO mapping according to the first setting may be changed to the SSB-RO mapping according to the second setting at t0 or t0+.

[0212] According to another proposed method, after the PRACH combining period according to the SSB-RO mapping for the first configuration is completed, the PRACH combining period according to the SSB-RO mapping for the second configuration can be started.

[0213] The reference time for a change (e.g., switching) of the PRACH combining period may be t0 or t0+. t0 may be the reception time of the DCI, and t0+ may be the time at which the decoding operation for the DCI is completed. After the PRACH combining period to which the reference time belongs ends, the PRACH combining period for the second configuration may start.

[0214] According to another proposed method, the transition time between the first configuration and the second configuration can be any time before the completion of the PRACH combining cycle. In other words, any time within the PRACH combining cycle can be the transition time between configurations (e.g., the reference time). The SSB-RO mapping for the first configuration can be applied before the reception time of the DCI (e.g., t0) or the time considering the decoding operation for the DCI (e.g., t0+). The SSB-RO mapping for the second configuration can be applied after the reception time of the DCI (e.g., t0) or the time considering the decoding operation for the DCI (e.g., t0+).

[0215] Additional settings for priorities

[0216] The terminal may consider capabilities (or features) to derive a set of ROs for the first and second configurations. The set of ROs for the first configuration may be considered the terminal's basic features. The set of ROs for the second configuration may be considered the terminal's additional features. For the set of ROs for the second configuration, separate priority values ​​may be assigned to the preamble set for the additional features.

[0217] contention free random access (CFRA)

[0218] During a SI request procedure (e.g., a SIB1 request procedure), a situation may arise where a UE requests other system information (OSI). OSI may refer to other system information block (OSIB). After the signaling for a state change of a camping cell has been sufficiently instructed to the UE, the first SSB-RO mapping among the SSB-RO mappings (e.g., the earliest SSB-RO mapping) may be considered. A camping cell may refer to a cell on which the UE has camped.

[0219] The terminal can receive a PDCCH order from the base station and transmit Msg1 to the base station based on the PDCCH order. The terminal can receive DCI, which is a PDCCH order, perform a decoding operation for the DCI, and transmit Msg1 in an RO according to the initial SSB-RO mapping.

[0220] If the UE is instructed to signal a change in the status of the serving TRP (e.g., serving cell), the UE may cancel the CFRA. In other words, the UE may not perform the CFRA. The CFRA cancellation operation may be indicated (e.g., signaled) from the physical layer of the UE to the upper layer of the UE. The CFRA cancellation operation may mean the cancellation of a pending PRACH operation. The counter associated with the PRACH transmission may be reset.

[0221] SBFD-Msg1

[0222] In the embodiments below, methods for a terminal camping on a base station performing SBFD operation to select an RO will be described.

[0223] The concept of SD resources

[0224] The UE can obtain parameter(s) (e.g., configuration(s)) for performing the RA procedure from SIB1. For example, the UE can obtain RACH configuration information (e.g., RACH-ConfigCommon, RACH-ConfigDedicated, RACH-ConfigGeneric, and / or prach-ConfigurationIndex). The RACH configuration information can be included in system information (e.g., SIB1). Based on the obtained parameter(s), the UE can check configuration information for PRACH, time resource information of the RO set, and / or frequency resource information of the RO set.

[0225] The terminal can identify the time location of UL resources (or FL resources, UL / FL resources, non-SD resources) to which a valid RO can be mapped among the RO set based on the UL-DL configuration information (tdd-UL-DL-ConfigurationCommon). The UL-DL configuration information can be included in system information (e.g., SIB1). The terminal can identify the frequency location of UL / FL resources to which a valid RO can be mapped among the RO set based on BWP-uplinkCommon.

[0226] The terminal can perform PRACH transmission or drop PRACH transmission based on separately defined drop conditions. If PRACH transmission is dropped in an RO, the terminal can select another RO within the RO set. If the terminal transmits a PRACH, the terminal can receive Msg2 PDSCH (or MsgB PDSCH) according to the RA procedure. Alternatively, if the terminal transmits a PRACH, the terminal can receive SI.

[0227] A RO set can be mapped in non-DL resources (e.g., FL resources, UL resources). According to the proposed method, it may be desirable for the RO set to also be mapped in SD resources. In order to allow UL transmission in SD resources, the SD resources can be composed of SD symbols and UL subbands, and ROs belonging to the SD resources can be determined as valid ROs. A RO set (e.g., a valid RO set) configured in an SD resource can be considered an invalid RO set in an ND resource. A RO set (e.g., a valid RO set) configured in an ND resource can be considered an invalid RO set in an SD resource.

[0228] An SD resource may be composed of consecutive symbols in the time domain and consecutive REs (resource elements) in the frequency domain. SD resources may not overlap each other. One SD resource or multiple SD resources may exist within a BWP (or a pair of BWPs). An SD resource may include not only SD symbols but also FL symbols. In the methods proposed below, the time resource of an SD resource may be interpreted as an SD symbol or as "SD symbol + FL symbol." Alternatively, in the methods proposed below, the time resource of an SD resource may be interpreted as a DL symbol or as "DL symbol + FL symbol." In an FL symbol, a DL subband and / or an UL subband may not be indicated (e.g., configured), and an FL symbol may be classified as a non-SD symbol.

[0229] In an SD resource, an SD symbol may be a DL symbol. In a DL symbol, a UL subband may be indicated (e.g., configured). The above-described DL symbol may be referred to as an SD-DL symbol. An SD-DL symbol may mean a DL symbol in which a UL subband is configured in an SD resource. In other words, an SD-DL resource may mean a DL resource having a UL subband. An SD resource may be divided into an SD-DL symbol and an SD-FL symbol. An SD-FL symbol may mean an FL symbol in an SD resource. In an FL symbol, a UL subband may or may not be configured. An SD-FL resource may mean an FL resource having a UL subband or an FL resource not having a UL subband. An SD-DL symbol and an SD-FL symbol may have a common SSB-RO mapping. An SD-DL symbol and an SD-FL symbol may have different SSB-RO mappings. The RO validity determination based on the SSB-RO mapping for SD-DL symbols may differ from the RO validity determination based on the SSB-RO mapping for SD-FL symbols. The RO set configured in SD-DL resources may be determined as a valid RO set or an invalid RO set, and the RO set configured in SD-FL resources may be determined as a valid RO set or an invalid RO set.

[0230] From the perspective of RO validity judgment, SD symbols may be limited to DL symbols among DL symbols and FL symbols indicated by RRC signaling (e.g., tdd-UL-DL-ConfigurationCommon). In this case, in the methods proposed below, SD resources (e.g., SD symbols) may mean DL symbols indicated by RRC signaling.

[0231] An SD resource may mean both a DL symbol (e.g., an SD-DL symbol) for which a UL subband is indicated (e.g., configured) and an FL symbol (e.g., an SD-FL symbol) for which a UL subband is indicated (e.g., configured). An RO may include both SD resources and non-SD resources, and SD-DL symbols, SD-FL symbols, and / or non-SD symbols (e.g., FL symbols, UL symbols) may be distinguished. In the proposed methods, distinct SSB-RO mappings may be applied to SD-DL symbols and SD-FL symbols.

[0232] SIB

[0233] The base station can inform the terminal(s) of the location of SD resource(s) using signaling (e.g., RRC signaling). The location information of the SD resource(s) can be included in the SIB. The terminal can identify the location of the SD resource(s) through the signaling of the base station (e.g., RRC signaling, SIB). For example, the terminal can identify the location of the SD resource(s) based on the SBFD configuration information received from the base station. The terminal can determine whether the RO is a valid RO or an invalid RO by applying the pattern of the SD resource(s) to the RO set derived based on RACH-ConfigCommon. The terminal can recognize the shape of the SD resource. The terminal can derive information indicating that the RO set is mapped to the SD resource from the SIB. The terminal can determine the validity of the RO in the SD resource based on the prach-ConfigurationIndex. If the RO set is mapped to the SD resource, another RO set can be mapped to the ND resource (e.g., UL / FL resource).

[0234] The base station can transmit existing SIBs to support legacy terminals. The base station can transmit SIBs containing new information to support terminals capable of communicating on SD resources (e.g., terminals supporting SBFD operation).

[0235] A SIB may include a prach-ConfigurationIndex for deriving a set of ROs mapped from UL resources and / or FL resources (e.g., a legacy RO set) and a prach-ConfigurationIndex for deriving a set of ROs mapped from SD resources (e.g., an additional RO set). The prach-ConfigurationIndex for deriving a set of ROs mapped from SD resources may be referred to as prach-ConfigurationIndex-SD. The SIB may explicitly include prach-ConfigurationIndex-SD, or prach-ConfigurationIndex-SD may be derived based on parameter(s) included in the SIB. The feature for deriving a set of ROs from SD resources may be considered a separate feature combination. The UE may select a preamble belonging to a preamble set assigned to each feature combination.

[0236] The RA trigger event may be the same, and the purpose of the early indication of the terminal may be the same. According to the proposed method, Msg1 transmission considering the RO set mapped in the SD resource and the ND resource (e.g., non-SD resource) may correspond to the same priority value. For example, even if the RA configuration (e.g., RA configuration information) indicating the RO set mapped to the SD resource and the RA configuration indicating the RO set mapped to the ND resource are different, the above-described RA configurations may correspond to the same priority value. The ND resource may mean a non-SD resource. The ND resource may mean a resource other than an SD resource. The SD resource may mean a resource including SD symbols. The ND resource may include FL symbols, DL symbols, and / or UL symbols. The UL subband and / or DL ​​subband for SBFD operation in the ND resource may not be indicated (e.g., configured). A terminal may be considered to perform one duplex operation on symbol(s) belonging to an ND resource.

[0237] According to another proposed method, additionally indicated RA configurations (e.g., RA configuration information) to the UE may have separate priority values ​​and separate preamble sets. The UE may perform an RA procedure (e.g., a contention-based random access (CBRA) procedure or a CFRA procedure) based on an RA trigger event. Based on a rule defined in the technical specification or a measurement result of the UE (e.g., SS-RSRQ, SS-RSRP), the UE may select one RO set from among the RO set mapped from the ND resource, the RO set mapped from the SD resource, or the RO set mapped from the ND resource and the SD resource (e.g., a special RO set). The UE's selection of an RO set may imply that the UE selects one RA configuration. It may be desirable that the priority value and / or the preamble set be indicated for each RA configuration, because the additionally indicated RA configurations may be shared with UEs having different features. In other words, additionally indicated RA settings (e.g., RO) can be shared across terminals with different capabilities.

[0238] According to the proposed method, for one RA configuration, the set of ROs mapped to SD resources can be distinguished from the set of ROs mapped to ND resources, and an RA procedure (e.g., a CBRA procedure or a CFRA procedure) can be performed. In this case, a separate priority value or a separate set of preambles can be indicated (e.g., configured) for the same RA trigger event. This is because the additionally indicated RA configuration can be shared with terminals having different features. In other words, the additionally indicated RA configuration (e.g., RO) can be shared with terminals having different features.

[0239] Option 2 Overview

[0240] Fig. 13 is a conceptual diagram illustrating a first embodiment of interpreting the setting of a RO set mapped to an SD symbol and a UL symbol.

[0241] Referring to FIG. 13, a terminal can derive two PRACH configuration indices (e.g., two prach-ConfigurationIndexes) from an SIB. Each PRACH configuration index can be independently indicated (e.g., configured). According to the two PRACH configuration indices, different preamble formats, different SSB-RO mapping ratios, and / or different numbers of FDM ROs can be indicated. The number of FDM ROs can be the number of ROs being FDMed.

[0242] The order of the two PRACH configuration indices can be indicated to the UE. The UE can distinguish between one PRACH configuration index (e.g., an existing PRACH configuration index or a legacy PRACH configuration index) and an additional PRACH configuration index. One PRACH configuration index can be associated with one RACH generic configuration (e.g., one RACH-ConfigGeneric), and the additional PRACH configuration index can be associated with an additional RCAH generic configuration (e.g., additional RACH-ConfigGeneric).

[0243] The terminal may consider the two PRACH configuration indices to correspond to different symbol types (e.g., SD symbol, ND symbol). For example, one PRACH configuration index may correspond to an ND symbol (e.g., ND resource), and an additional PRACH configuration index may correspond to an SD symbol (e.g., SD resource). In other words, one RACH general configuration associated with one PRACH configuration index may include at least one of time resource information or frequency resource information of an RO set configured in an ND resource (e.g., a legacy RO set), and an additional RACH general configuration associated with an additional PRACH configuration index may include at least one of time resource information or frequency resource information of an RO set configured in an SD resource (e.g., an additional RO set). The special RO sets configured in the ND resource and the SD resource may be configured based on one RACH general configuration and the additional RACH general configuration.

[0244] Each PRACH configuration index can indicate a set of ROs, and among these sets, some ROs (e.g., some ROs) may be determined to be valid. The rules defined in the technical specifications may be applied in the RO validity determination procedure. SSBs may be mapped to valid ROs. The UE may transmit the PRACH preamble in a valid RO. In certain cases, the PRACH preamble may be dropped.

[0245] A legacy terminal can transmit a PRACH preamble from a set of ROs (e.g., RO) that are determined to be valid in an ND symbol. Valid ROs in an ND symbol may be referred to as legacy ROs. A legacy terminal may not be able to identify a set of ROs (e.g., RO, a set of valid ROs, a valid RO) in an SD symbol. Furthermore, a legacy terminal may determine an RO set (e.g., RO) in an SD symbol to be invalid. In other words, a set of valid ROs in an SD symbol may be determined to be an invalid RO set in an ND symbol. Valid ROs in an SD symbol may be referred to as additional ROs.

[0246] Legacy ROs and additional ROs can be derived using different PRACH configuration indices. Legacy ROs and additional ROs may or may not overlap in the time domain. Since legacy ROs are used by legacy terminals, legacy ROs can be configured in FL symbols and / or UL symbols. Additional ROs may include at least one SD symbol. In this case, a priority may not necessarily be required for a terminal to select the two ROs. An RO including at least one SD symbol and at least one ND symbol may be referred to as a special RO.

[0247] Option 1 Overview

[0248] To enable legacy UEs to interpret a single PRACH configuration index and SSB-RO mapping, SSB-RO mapping for a single PRACH configuration index can be performed. The UE can derive a set of ROs from UL resources. One SSB can be mapped to three ROs, and four ROs can be FDM'd in the same symbol. For four SSBs (e.g., four SSB indices), four ROs can be indexed in the first RACH slot. The first to third ROs can be associated with SSB index a. The fourth RO can be associated with SSB index b. Four ROs can be indexed in the second RACH slot. Four ROs can be indexed in the second RACH slot. In the second RACH slot, four ROs can be associated with SSB index b, SSB index b, SSB index c, and SSB index c, in that order. Based on the above-described method, SSB can be mapped to RO.

[0249] SSB-RO mapping for different PRACH configuration indices can be performed so that new terminals can interpret different PRACH configuration indices (e.g., additional PRACH configuration indices) and SSB-RO mapping. The terminal can derive a set of ROs from SD resources (e.g., resources indicated by DL symbols through signaling, SD-DL resources, and / or resources indicated by DL symbols or FL symbols through signaling). One SSB can be mapped to four ROs, and two ROs can be FDM'd in the same symbol. The number of SSB indices can be four. In the first slot, two ROs can be indexed for SSB index a. In the second slot, two ROs can be indexed for SSB index a. Based on the above-described method, an SSB can be mapped to an RO.

[0250] In the embodiment of FIG. 13, since there is one PRACH configuration index (e.g., the existing prach-ConfigurationIndex) and an additional PRACH configuration index, the amount of information for configuring the RO set can be doubled. Since the shape of the SD resource and the shape of the UL resource can have any form, it may be desirable for the existing PRACH configuration index and the additional PRACH configuration index to have independent values ​​in order to efficiently configure the PRACH and / or the RO. For example, a base station performing SBFD operation can indicate to the terminal a preamble having a long format for the RO set mapped in the SD resource (e.g., a resource indicated by a DL symbol by signaling, an SD-DL resource, and / or a resource indicated by a DL symbol or an FL symbol by signaling) in order to extend the UL coverage. Since legacy terminals can only use UL resources (e.g., FL symbols or UL symbols) for transmitting PRACH preambles, a preamble with a short format can be indicated to the terminal from a set of ROs mapped to UL resources (e.g., a set of ROs mapped to ND resources). According to the above-described embodiment, multiplexing performance with other UL signals / channels can be improved.

[0251] According to the proposed method, the amount of information indicated to the UE may be reduced. Alternatively, the base station and / or the UE may have many degrees of freedom. Therefore, the RO set may not be maintained as a union. For some RRC parameter(s), configurations (e.g., indications) of existing RACH-config and additional RACH-config with the same values ​​may be expected. For example, preambleTransMax, ra-ResponseWindow, ra-ContentionResolutionTimer, rsrp-ThresholdSSB, msg1-SubcarrierSpacing, and / or msg3-transformPrecoder may be considered.

[0252] A PRACH configuration index (e.g., an existing PRACH configuration index) can indicate an RO set, and the RO set can be divided into an RO set defined in an ND symbol (e.g., a legacy RO set), an RO set defined in an SD symbol (e.g., an additional RO set), and / or an RO set defined in both an ND symbol and an SD symbol (e.g., a special RO set). The RO set defined in an ND symbol, the RO set defined in an SD symbol, and / or the RO sets defined in both an ND symbol and an SD symbol can be regarded as separate RO sets. Alternatively, the RO set defined in an ND symbol, the RO set defined in an SD symbol, and / or the RO sets defined in both an ND symbol and an SD symbol can be regarded as one RO set. The rule(s) defined in the technical specification can be applied in determining RO validity. An SSB can be mapped to a valid RO. A terminal can transmit a PRACH preamble in a valid RO. Transmission of the PRACH preamble can be dropped in certain cases.

[0253] Since legacy terminals can transmit PRACH preambles in ROs belonging to the valid RO set in an ND symbol, ROs belonging to the valid RO set in an ND symbol may be referred to as legacy ROs. Legacy terminals may not recognize the valid RO set in an SD symbol. Alternatively, legacy terminals may determine the valid RO set in an SD symbol as invalid. In other words, the valid RO set in an SD symbol may be regarded as an invalid RO set in an ND symbol. ROs belonging to the valid RO set in an SD symbol may be referred to as additional ROs.

[0254] Legacy ROs and additional ROs can be derived based on a single PRACH configuration index (e.g., an existing PRACH configuration index). In the time domain, legacy ROs and additional ROs can be interpreted as non-overlapping. To enable legacy terminals to utilize legacy ROs, legacy ROs can be configured in FL symbols and / or UL symbols. Additional ROs can include at least one SD symbol.

[0255] Simultaneous support of two options

[0256] A UE can derive a set of ROs for legacy ROs, special ROs, and / or additional ROs based on one PRACH configuration index or two PRACH configuration indices. A UE can operate according to one option (e.g., option-1 or option-2). If option-1 is supported, the UE can identify at least one of the legacy RO set, the additional RO set, or the special RO set based on one RACH general configuration associated with one PRACH configuration index (e.g., prach-ConfigurationIndex). If option-2 is supported, the UE can identify at least one of the legacy RO set, the additional RO set, or the special RO set based on two RACH general configurations associated with two PRACH configuration indices. For example, the terminal can identify a legacy RO set based on a first RACH general configuration associated with a first PRACH configuration index among two PRACH configuration indices, the terminal can identify an additional RO set based on a second RACH general configuration associated with a second PRACH configuration index among two PRACH configuration indices, and the terminal can identify a special RO set based on the first RACH general configuration and the second RACH general configuration.

[0257] Some terminals may not support operations according to both options (e.g., option 1 and option 2). The base station may not know which terminal supports which option. It may be desirable for the base station to transmit SIB1 to support both options. If the base station supports operation according to one option, the coverage expansion effect may not occur because terminals that support SBFD operation but support other operations of the RA procedure will perform the existing RA procedure. The base station can transmit information about which option is supported among option 1 and option 2 to the terminal through signaling (e.g., SIB1). The terminal can determine which option (e.g., option 1 or option 2) the base station supports through the signaling of the base station. In other words, the terminal can determine that one PRACH configuration index (e.g., one RACH general configuration) or two or more PRACH configuration indices (e.g., two or more RACH general configurations) is indicated (e.g., configured) to the terminal based on the signaling of the base station.

[0258] If the PRACH configuration index for the legacy RO and the PRACH configuration index for the additional RO are distinguished in SIB1, the IE included in SIB1 may indicate the PRACH configuration index for the legacy RO and the PRACH configuration index for the additional RO. The IE included in SIB1 may indicate that the PRACH configuration index for the legacy RO is distinguished from the PRACH configuration index for the additional RO.

[0259] SIB1 may include time resource information (e.g., time shape information, time pattern information) of SBFD resources and / or frequency resource information (e.g., frequency shape information, frequency pattern information) of SBFD resources. The time resource information of SBFD resources and the frequency resource information of SBFD resources may be indicated by different IEs in SIB1. For example, the time pattern of SBFD resources may be indicated by pattern information of TDD symbols / slots for legacy terminals, and the frequency pattern of SBFD resources may be indicated by BWP configuration information. BWP-UplinkCommon may include frequency pattern information of SBFD resources. tdd-UL-DL-ConfigurationCommon may include time pattern information of SBFD resources.

[0260] RA resources can be indicated by BWP configuration information. Methods for deriving legacy ROs / additional ROs can be divided into a method in which both legacy ROs and additional ROs are derived based on a single RA configuration information (e.g., method 1) and a method in which each legacy RO and additional RO are derived based on two pieces of RA configuration information (e.g., method 2).

[0261] In method 1, the terminal can select one symbol (e.g., one symbol type) for transmitting msg1 from among ND symbols (e.g., legacy RO) and SD symbols (e.g., additional RO), and select a valid RO for the determined symbol type. The terminal can transmit msg1 in the valid RO. The base station can set parameter(s) belonging to SIB1 so that the terminal transmits msg1 in one symbol type (e.g., a valid RO for one symbol type). Alternatively, the terminal can select one symbol type based on a specific metric.

[0262] According to the proposed method, in the above-described method 1, the base station can explicitly indicate to the terminal through signaling whether transmission of msg1 is allowed in the SD symbol or in the ND symbol. The terminal can determine the symbol type (e.g., SD symbol or ND symbol) in which transmission of msg1 is allowed based on the signaling of the base station. To support the above-described operation, separate RRC parameter(s) can be introduced. The separate RRC parameter(s) can indicate that the use of the SD symbol (e.g., RO in the SD symbol) is activated.

[0263] According to another proposed method, in method 1, if the parameter(s) required for transmitting msg1 in an SD symbol are derived by the terminal, the terminal can determine (e.g., interpret) that msg1 can be transmitted in an SD symbol. In this case, the terminal can transmit msg1 in an SD symbol or an ND symbol. The terminal can select an SD symbol or an ND symbol based on a specific metric. The terminal can select an RO for the determined (e.g., selected) symbol type.

[0264] In Method 2, the terminal may consider the symbol type and RO mapped to the RO in the RO set derived based on two PRACH configuration indices. Even in a single RA trigger event, two PRACH configuration indices may be used. An RA trigger event may refer to an event that triggers an RA procedure.

[0265] A UE can select a PRACH configuration index based on an RA trigger event. When the UE performs an RA procedure for initial access, the UE can use a set of ROs and a set of preambles derived from a specific PRACH configuration index. When the UE performs a CFRA procedure, the UE can specify (e.g., select) an RO from a set of ROs derived from different PRACH configuration indices. The former PRACH configuration index (e.g., a specific PRACH configuration index) can be commonly applied to UEs camping at the base station. The latter PRACH configuration index (e.g., a different PRACH configuration index) can be information indicated by the base station to each UE.

[0266] To signal Method 2, rach-ConfigCommon can include two pieces of configuration information. A terminal supporting SBFD operation can interpret (e.g., understand) both pieces of configuration information included in rach-ConfigCommon. A terminal supporting SBFD operation can derive a set of ROs mapped to each SD resource and ND resource based on each PRACH configuration index. A legacy terminal (e.g., a terminal that does not support SBFD operation) can derive a set of ROs mapped to ND resources. In other words, a legacy terminal (e.g., a terminal that does not support SBFD operation) cannot derive a set of ROs mapped to SD resources. Alternatively, even if a legacy terminal derives a set of ROs mapped to SD resources, the legacy terminal may determine the derived set of ROs as an invalid set of ROs.

[0267] A base station can signal to a terminal that the terminal uses a function-specific preamble set. Ambiguity may arise regarding which preamble set of the RO set the signaling indicates. For example, it may be ambiguous whether the signaling indicates a preamble set from an RO set mapped to SD resources or a preamble set from an RO set mapped to ND resources.

[0268] According to the proposed method, the terminal can assume that the preamble set applies to the RO set mapped in the ND resource. For example, the preamble set for the RO set mapped in the SD resource can be used without restriction. If the base station additionally indicates the preamble set, the preamble set for the RO set mapped in the SD resource can be considered as explicitly indicated. For another example, if only one preamble set is indicated (e.g., configured) to the terminal, the terminal may not determine that the RO set mapped in the SD resource is valid. It may be necessary for the base station to indicate to the terminal the preamble set for the RO set mapped in the SD resource.

[0269] According to the proposed method, a terminal can receive information (e.g., an indication) of an additional preamble set from a base station. The terminal can regard the preamble set indicated by the base station (e.g., an additional preamble set) as a preamble set applicable to a RO set mapped to SD resources. The terminal can assume that the preamble set is indicated (e.g., configured) to the terminal together with configuration information of a RO set mapped to SD resources.

[0270] According to another proposed method, the terminal can assume that the preamble set applies to all RO sets mapped to ND resources and / or SD resources. Based on the above method, some preambles in the RO set mapped to SD resources can be utilized. In the SBFD operation, if the RA trigger event is restricted to some circumstances (e.g., PDCCH order, reconfiguration with uplink synchronization, etc.), the RO set mapped to the SD resource (e.g., ROs belonging to the RO set) may not be used as shared ROs. Therefore, the method of restricting the preamble set to be the same as the preamble set for the RO set mapped to the ND resource may limit the configuration freedom. In the SBFD operation, if the RA trigger event is not restricted, the preamble (e.g., the preamble set) may be restricted. If shared ROs are likely to be used, separately indicating the preamble sets for each of the RO sets mapped from SD resources and the RO sets mapped from ND resources may increase the signaling burden, but may not significantly increase the degree of freedom (e.g., the degree of configuration freedom).

[0271] To signal method 2, rach-ConfingCommon and additionalRACH-ConfigList can be used. rach-ConfingCommon can be used to indicate the set of ROs that are mapped on the ND resource. One configuration belonging to additionalRACH-ConfigList can be used to indicate the set of ROs that are mapped on the SD resource.

[0272] RA trigger events (e.g., RACH trigger events) for configurations (e.g., RO configuration in ND resources and RO configuration in SD resources) can be distinguished. The behavior of redCap terminals and RAN (radio access network) slicing terminals may differ from that of legacy terminals starting from the BWP indication phase. A redCap terminal may be a terminal with reduced capability. A RAN slicing terminal may refer to a terminal that supports the RAN slicing function. Even when a UE capability report is not delivered to the base station, a separate preamble set, a separate configuration index, and / or one or more configurations belonging to additionalRACH-ConfigList may be indicated (e.g., configured) to the terminal. In normal operation, RA configuration 1 may be applied. In other words, RA configuration 1 may be applied for legacy terminals. RA configuration 2 may be applied for redCap terminals. RA setting 3 can be applied for RAN slicing terminals.

[0273] In a terminal supporting SBFD operation, an RA trigger event may not be indicated from the upper layer of the terminal to the physical layer of the terminal, and SD resources or ND resources may be selected according to the pattern of SBFD resources. The terminal may have the same RA trigger event and may select one RO set from among the RO sets derived based on different PRACH configuration indices. It may be assumed that the terminal performs the above-described operation.

[0274] Method 1 and Method 2 can be supported simultaneously. According to the proposed method, one PRACH configuration index (e.g., PRACH configuration index 1) and an additional PRACH configuration index (e.g., PRACH configuration index 2) can be included in the BWP configuration information. PRACH configuration index 1 can be associated with RA configuration 1, and PRACH configuration index 2 can be associated with RA configuration 2. RA configuration 1 can be used to configure RO sets mapped to ND resources and / or SD resources.

[0275] A terminal performing method 1 can regard a set of ROs mapped to ND resources or SD resources based on RA configuration 1 as a valid set of ROs. The terminal can select ND resources or SD resources based on a method described below. Alternatively, the terminal can select ND resources or SD resources based on an explicit configuration of a base station. A terminal performing method 2 can regard a set of ROs mapped to ND resources based on RA configuration 1 as a valid set of ROs, and a set of ROs mapped to SD resources based on RA configuration 2 as a valid set of ROs. Based on the configuration of the base station, the preamble set can be commonly applied to SD resources and ND resources. Alternatively, based on the configuration of the base station, the preamble set can be independently applied to SD resources and ND resources.

[0276] For example, a base station may instruct (e.g., configure) a BWP supporting method 1 to a terminal, and the terminal may support method 2. In this situation, the terminal may determine a set of ROs mapped in ND resources as a valid set of ROs based on the RA configuration that configures method 1. For another example, a base station may instruct (e.g., configure) a BWP supporting method 2 to a terminal, and the terminal may support method 1. In this situation, the terminal may determine a set of ROs mapped to SD resources as a valid set of ROs based on a configuration corresponding to an additional configuration among the RA configurations that configure method 2. For another example, a base station may instruct (e.g., configure) a BWP supporting both methods 1 and 2 to a terminal, and the terminal may support both methods 1 and 2. In this situation, the terminal may select one resource from among the ND resources and the SD resources. The terminal may apply the following method(s) to select one resource.

[0277] With respect to the feature combination, RO resources mapped to ND resources and RO resources mapped to SD resources can have the same priority. Even if Method 1 and Method 2 are supported and three RO sets are distinguished (e.g., RO set 1 mapped to ND resources based on RA configuration 1, RO set 2 mapped to SD resources based on RA configuration 1, and RO set 3 mapped to SD resources based on an additional RO configuration (e.g., RO configuration 2)), one priority can be applied.

[0278] SS-RSRP and SS-RSRQ

[0279] SS-RSRP and SS-RSRQ can be measured in relation to SBFD operation. In addition to considering SBFD operation, a method utilizing SS-RSRP and / or SS-RSRQ can be applied.

[0280] Selection of SD and ND resources

[0281] Both Method 1 and Method 2 described above can be considered. Based on Method 1, the terminal can derive a set of ROs mapped to ND resources using one PRACH configuration index, and a set of ROs mapped to SD resources. Based on Method 2, the terminal can derive a set of ROs mapped to ND resources based on one PRACH configuration index, and a set of ROs mapped to SD resources based on another PRACH configuration index.

[0282] The RA procedure performed by a terminal supporting SBFD operation may be considered. An RA trigger (e.g., an RA trigger event) may be transmitted from the upper layer of the terminal to the physical layer of the terminal. Thereafter, the terminal may select an SSB based on SS-RSRP, and may select one RO set associated with the selected SSB from among the RO set mapped to SD resources and the RO set mapped to ND resources. The following method(s) may be applied to the initial transmission operation and / or retransmission operation of msg1.

[0283] A terminal can select a set of ROs mapped to SD resources and transmit msg1 in the selected RO set. In this case, cross-link interference (CLI) may occur. Even if the RB in which msg1 is transmitted belongs to a UL usable PRB and is different from the DL usable PRB of a neighboring terminal, CLI may still occur in the neighboring terminal due to leakage. To minimize CLI, it may be desirable for msg1 to be transmitted in a set of ROs that have frequency resources that are far from the DL usable PRBs. In this case, spectrum leakage for msg1 transmission may be reduced. To minimize CLI, a terminal can select a set of ROs mapped to SD resources for transmitting msg1 with low transmit power. In other words, a terminal may not select a set of ROs mapped to SD resources for transmitting msg1 with high transmit power.

[0284] In the proposed method, to select a set of ROs mapped to SD resources, the terminal may select a set of ROs (e.g., ROs) that have frequency resources spaced apart from DL-available PRBs by a preset distance. If there is no set of ROs mapped to SD resources by a frequency resource spaced apart from DL-available PRBs by a preset distance, the terminal may select a set of ROs mapped to ND resources.

[0285] In another proposed method, if the transmit power of msg1 is below a preset value, the terminal can select a set of ROs mapped from SD resources. If the transmit power of msg1 is not maintained below a preset value, the terminal can select a set of ROs mapped from ND resources.

[0286] Alternatively, the terminal can utilize SS-RSRQ. Comparing SS-RSRQ and SS-RSRP, the NR carrier RSSI can be additionally measured for SS-RSRQ. Considering an aggressor and a victim in an interference scenario, the NR carrier RSSI can be interpreted as the amount of interference at the victim. The aggressor can be a neighboring base station or a neighboring terminal. The terminal transmitting msg1 can be the aggressor, and the transmission of msg1 can cause interference to the victim. The NR carrier RSSI measured at the victim can be closely related to the amount of interference the aggressor causes to the neighboring base station or neighboring terminal. If the NR carrier RSSI is large, it may be desirable for the terminal measuring SS-RSRQ not to use the RO set mapped in the SD resource.

[0287] In the proposed method, the terminal can select an SD resource (e.g., a set of ROs mapped to SD resources) or an ND resource (e.g., a set of ROs mapped to ND resources) based on SS-RSRQ. By comparing SS-RSRP and SS-RSRQ, the NR carrier RSSI can be derived. If the NR carrier RSSI is greater than or equal to a threshold, the CLI affected by msg1 transmission can be predicted to be large. In this case, the terminal can select an RO set mapped to ND resources. If the NR carrier RSSI is less than or equal to a threshold, the CLI affected by msg1 transmission can be predicted to be small. In this case, the terminal can select an RO set mapped to SD resources.

[0288] If SS-RSRQ is greater than or equal to the threshold, the terminal may select a set of ROs mapped from SD resources. If SS-RSRQ is less than the threshold, the terminal may select a set of ROs mapped from ND resources.

[0289] Comparison of SS-RSRP and SS-RSRQ

[0290] In the proposed method, SD resources and ND resources can be distinguished for measuring SS-RSRQ. The SD resources for measuring SS-RSRQ can refer to resources belonging to the DL available PRB of the SD symbol. The ND resources for measuring SS-RSRQ can refer to resources belonging to the DL available PRB of the ND symbol. The time resources for measuring SS-RSRQ can be indicated to the terminal through higher layer signaling.

[0291] For SS-RSRQ measurements, SMTC, measurementSlots, endSymbol, and / or MG (measurement gap) can be considered. Since SS-RSRP relies on coherence demodulation of sequences using SSB, SS-RSRP measured on SD resources and SS-RSRP measured on ND resources can have the same value.

[0292] The UE can select SSB using SS-RSRP. After that, the UE can measure SS-RSRQ and determine an RO set mapped to ND resources or SD resources based on the comparison result of SS-RSRP and SS-RSRQ. The UE can select one RO set (e.g., RO, RO group) from among the RO sets mapped to ND resources and the RO sets mapped to SD resources, and transmit msg1 to the base station using the selected RO set. Alternatively, the UE can select one RO set from among the legacy RO set, the additional RO set, or the special RO set, and transmit msg1 to the base station using the selected RO set.

[0293] Comparison of SS-RSRQs

[0294] According to the proposed method, SS-RSRQ can be measured in two or more separate ways, considering the time resources of SBFD. The terminal can derive SS-RSRQ from SD resources and SS-RSRQ from ND resources by considering SMTC, measurementSlots, endSymbol, and / or NR carrier RSSI.

[0295] It may be desirable to measure SS-RSRQ for resources belonging to the same symbol type by applying measurementSlots and / or endSymbol indicated to the terminal. Measurement time set 1 may be slot(s) and / or symbol(s) belonging to ND resources. Measurement time set 2 may be slot(s) and / or symbol(s) belonging to SD resources. The SSB reception period may not always be aligned with the period of the SBFD resource pattern. The slot offset of the SSB reception period may be different from the slot offset of the SBFD resource pattern.

[0296] Various methods for defining measurement time sets 1 and 2 may be considered. For example, measurement time sets 1 and 2 may be defined as time resources for measuring SS-RSRQ in SMTC (e.g., SMTC interval). For another example, measurement time sets 1 and 2 may be resources temporally distinguished by the SBFD resource pattern, and measurement time sets 1 and 2 may be time resources that do not consider SMTC. SS-RSRQ may be measured in time resources belonging to measurement time sets (e.g., measurement time sets 1 and / or 2) and SMTC (e.g., SMTC interval).

[0297] According to the proposed method, SS-RSRQ (e.g., SS-RSRQ 1) can be measured in measurement time set 1 associated with ND resources, and SS-RSRQ (e.g., SS-RSRQ 2) can be measured in measurement time set 2 associated with SD resources. The UE can select an RO set based on the sizes of SS-RSRQ 1 and SS-RSRQ 2. If SS-RSRQ 1 is larger than SS-RSRQ 2, the UE can determine that NR carrier RSSI 1 is smaller than NR carrier RSSI 2 because SS-RSRPs are the same. The size of NR carrier RSSI can be related to the size of CLI affected by msg1 transmission. Since it is desirable that the size of NR carrier RSSI is small, the UE can select an RO set mapped in the ND resource associated with SS-RSRQ 1. If SS-RSRQ 1 is less than or equal to SS-RSRQ 2, the terminal can select a RO set mapped from the SD resources associated with SS-RSRQ 2.

[0298] The UE can select SSB using SS-RSRP. After that, the UE can measure SS-RSRQ on each ND resource and SD resource for each measurement time set, and compare the SS-RSRQ measured on the ND resource with the SS-RSRQ measured on the SD resource to determine (e.g., select) the RO set mapped on the ND resource or SD resource. The UE can select one RO (or one RO group) within the RO set, and transmit msg1 to the base station using one RO (or one RO group).

[0299] Option-1 Settings

[0300] A UE can select a PRACH configuration index based on the cause (e.g., trigger condition, trigger event) for performing a RACH procedure (e.g., RA procedure). An RO set can be derived based on the selected PRACH configuration index. The UE can select an RO (or RO group) belonging to the RO set. While performing the RA procedure, the UE can maintain the RO set (e.g., the derived RO set). For example, the UE can select an RO (or RO group) from the same RO set for PRACH retransmission.

[0301] A SIB can use a single PRACH configuration index to indicate both a set of ROs mapped to UL resources (e.g., a set of ROs mapped to ND resources) and a set of ROs mapped to SD resources. Since the same PRACH configuration index is shared, a separate function combination for deriving a set of ROs from SD resources may not be allocated. Since SD resources and UL resources are temporally distinct, the set of ROs mapped to SD resources and the set of ROs mapped to UL resources can be temporally distinct. An SD resource can be indicated by a DL symbol through signaling, and an UL resource can be indicated by an FL symbol or an UL symbol through signaling. Alternatively, an SD resource can be indicated by a DL symbol or an FL symbol through signaling, and an UL resource can be indicated by a UL symbol through signaling.

[0302] SSB mapping may be performed to derive two or more RO sets (e.g., a legacy RO set, an additional RO set, and / or a special RO set) based on a single PRACH configuration index. The order of the SSB indices may be fixed to a, b, c, and d so that legacy terminals can interpret the RO sets mapped to UL resources.

[0303] Fig. 14 is a conceptual diagram illustrating a second embodiment of interpreting the setting of a RO set mapped to SD symbols and UL symbols, and Fig. 15 is a conceptual diagram illustrating a third embodiment of interpreting the setting of a RO set mapped to SD symbols and UL symbols.

[0304] Referring to FIGS. 14 and 15, a set of ROs can be derived based on a single PRACH configuration index. Based on conventional rules, ROs in UL resources, UL symbols, and / or FL symbols can be considered as valid ROs, and SSB-RO mapping for valid ROs can be performed. According to the proposed method, ROs in SD resources as well as ND resources can be considered as valid ROs, and SSB-RO mapping for valid ROs in ND resources and SSB-RO mapping for valid ROs in SD resources can be performed independently.

[0305] Since the RO set is derived based on a single PRACH configuration index, the SSB-RO mapping can be performed so that legacy terminals can interpret the SSB-RO mapping. The RO set can be derived from UL resources (e.g., UL symbols and / or FL symbols indicated by signaling), and the four ROs can be FDM'd. Since the legacy terminal determines the RO validity in time resources, all four ROs (e.g., four ROs located in the same time resource) can be considered valid ROs.

[0306] A set of ROs can be derived from SD resources. Valid ROs can be derived from SD resources. The SD resources can be composed of SD symbols and UL subbands. ROs can be valid in both time resources and frequency resources. In the embodiments of FIGS. 14 and 15, only two of the four ROs can be assumed to be valid ROs. Since SSB-RO mapping is performed on the valid ROs, SSB index a and SSB index a can correspond to the first RACH slot, and SSB index a and SSB index b can correspond to the second RACH slot. According to the proposed method, four ROs can always be assumed to be valid ROs. In other words, the number of valid ROs in the UL resource can be interpreted as being equal to the number of valid ROs in the SD resource. In this case, SSB index a, SSB index a, SSB index a, and SSB index b may correspond to the first RACH slot, and SSB index b, SSB index b, SSB index c, and SSB index c may correspond to the second RACH slot.

[0307] Since the terminal derives the RO set using a single PRACH configuration index, it can distinguish between the RO set mapped to UL resources and the RO set mapped to SD resources. Alternatively, the terminal can regard the derived RO set as an RO set in a single resource.

[0308] In the embodiment of FIG. 14, the terminal may select a set of ROs mapped to ND resources or a set of ROs mapped to SD resources. Alternatively, the terminal may select a set of ROs mapped to UL resources (e.g., UL symbols and / or FL symbols), a set of ROs mapped to SD-FL symbols, or a set of ROs mapped to SD-DL symbols.

[0309] In the embodiment of FIG. 15, the terminal may consider both the RO set mapped to the ND resource and the RO set mapped to the SD resource, and select an RO from all the RO sets. Alternatively, the terminal may consider all the RO set mapped to the UL resource (e.g., UL symbol and / or FL symbol), the RO set mapped to the SD-FL symbol, and the RO set mapped to the SD-DL symbol, and select an RO from all the RO sets.

[0310] union set

[0311] A set of ROs mapped from UL resources (e.g., a set of ROs mapped from ND resources) may mean ROs mapped from SD-FL symbols as well as UL symbols (e.g., UL-RO). A set of ROs mapped from SD resources may mean ROs mapped from SD-DL symbols (e.g., SD-RO). UL-RO may mean a set of ROs mapped from ND symbols (e.g., FL symbols and / or UL symbols). SD-RO may mean a set of ROs mapped from SD-DL symbols or SD-FL symbols.

[0312] According to the proposed method, a terminal can perform SSB-RO mapping for each of the RO sets mapped to ND resources and the RO sets mapped to SD resources based on independent rules. In the RO selection procedure, the terminal can select an RO from the union of the aforementioned RO sets. The above-described operation may not affect legacy terminals, and terminals supporting SBFD operation can select multiple ROs.

[0313] If the order of SSB indices in the SSB-RO mapping for the RO set mapped in the SD resource remains the same as the conventional order, certain SSB indices may occur frequently in the early slots of the PRACH combining period (e.g., the PRAHC combining pattern period).

[0314] When assigning different indices to SSB indices, the SSB indices in SD resources may be different from the SSB indices in UL resources. According to the proposed method, the order of SSB indices in SSB-RO mapping for a set of ROs mapped to SD resources may be assigned differently.

[0315] For example, the SSB indices may be mapped to the ROs in reverse order. The SSB indices for the set of ROs mapped to SD resources in the early slots (e.g., the first slots) of the PRACH combining period (e.g., the PRACH combining pattern period) may have the order d, c, b, a. The SSB indices for the set of ROs mapped to ND resources in the early slots (e.g., the first slots) of the PRACH combining period (e.g., the PRACH combining pattern period) may have the order a, b, c, d.

[0316] For another example, SSB indices may be mapped to ROs in the existing order. A set of ROs mapped in ND resources (e.g., UL symbols and / or FL symbols) may be first mapped to SSBs (e.g., SSB indices) based on the existing method, and thereafter, a set of ROs mapped in SD resources (e.g., SD-DL symbols and / or SD-FL symbols) may be mapped to SSBs (e.g., SSB indices) based on the existing method. In other words, a terminal may first perform SSB mapping for a set of ROs by considering RACH slots belonging to ND resources based on the existing method, and thereafter, perform SSB mapping for a set of ROs by considering RACH slots belonging to SD resources based on the existing method. A RACH slot belonging to an ND resource may be a RACH slot following a PRACH combining period. RACH slots belonging to SD resources within the same PRACH combining period may be mapped in time order.

[0317] Fig. 16 is a conceptual diagram illustrating a fourth embodiment of interpreting the setting of a RO set mapped to SD symbols and UL symbols.

[0318] Referring to FIG. 16, SSB-RO mapping can be performed in reverse order. A combining period (e.g., a PRACH combining period) can be derived based on a set of ROs mapped in ND resources (e.g., UL symbols and / or FL symbols). A terminal can map SSB indices based on a conventional method. A set of ROs mapped in SD resources can be composed of the first RACH slot and the last RACH slot belonging to the same combining period. Alternatively, a set of ROs mapped in SD resources can be composed of RACH slot(s) belonging between reference RACH slots (e.g., the first RACH slots or the last RACH slots) within an arbitrary combining period.

[0319] The SSB indices for the RO set mapped in the SD resource can be mapped in reverse order, and other rules can follow the technical specifications. In the embodiment of FIG. 16, the SSB indices can have the order of d, c, b, a. The SSB mapping for the RO belonging to the ND resource and the SSB mapping for the RO belonging to the SD resource can be performed independently. For the RO set belonging to the ND resource within the PRACH combining period, all SSB indices can be mapped to integer multiples. For the RO set belonging to the SD resource within the PRACH combining period, some SSB indices may not be mapped to integer multiples. Or, some SSB indices may not be mapped.

[0320] SSB-RO mapping can be performed on concatenated resources. SSB-RO mapping can be performed first on ND resources, and SSB-RO mapping can be performed on SD resources concatenated with the ND resources. The embodiment of FIG. 16 can illustrate the order of RACH slots. A set of ROs belonging to ND resources (e.g., UL symbols and / or FL symbols) can consist of three slots, and a set of ROs belonging to SD resources (e.g., SD-DL symbols and / or SD-FL symbols) can be considered thereafter. The fourth slot can correspond to the first RO within the combining period. The fifth slot and the slot(s) after the fifth slot can have a temporal order. A slot can include one or more RACH slots. In the embodiment of FIG. 16, a slot in an ND resource can include four RACH slots, and a slot in an SD resource can include two RACH slots.

[0321] When one PRACH configuration index is indicated, the combining period can be derived based on an SSB-RO mapping cycle. According to the conventional technical specification, one SSB-RO mapping cycle can be derived. According to the proposed method, two or more SSB-RO mapping cycles can be derived. There can be an SSB-RO mapping cycle derived from an SD resource and an SSB-RO mapping cycle derived from an UL resource. According to the proposed method, the combining period can be derived based on an SSB-RO mapping cycle derived from an UL resource (e.g., an UL symbol and / or an FL symbol).

[0322] bonding cycle

[0323] To determine a combining period (e.g., a PRACH combining period), n SSB-RO mapping cycles may be considered. n may be an integer. If there is a RO set or a PRACH preamble index that does not belong to the combining period, the SSB index may not be additionally mapped. All SSB indices in one combining period may be equally assigned. Considering a RO set that is mapped to an SD symbol (e.g., an SD-DL symbol and / or an SD-FL symbol), an SSB index may be additionally mapped to one or more ROs within the same combining period.

[0324] According to the proposed method, among the RO sets mapped in ND resources (e.g., UL symbols and / or FL symbols) within one combining period, the base station and / or the terminal can expect that the SSB index is not mapped to the RO sets after the last RO set, based on the last RO set to which the SSB is mapped. The above-described method can be applied to the RO sets mapped in SD resources (e.g., SD-DL symbols and / or SD-FL symbols).

[0325] According to another proposed method, SSB may not be mapped to RO(s) after the last RO described above among ROs mapped in ND resources (e.g., UL symbols and / or FL symbols), and SSB may be mapped to RO(s) after the last RO described above among ROs mapped in SD resources (e.g., SD-DL symbols and / or SD-FL symbols).

[0326] A single combined pattern period can be composed of n combined periods, where n can be an integer. A combined pattern period can be introduced so that the same SSB-RO mapping can be repeated with a maximum period of 160 ms in terms of radio frame numbers. The combined pattern period may not be exactly aligned with the n combined periods. Some ROs may not belong to a combined period. SSBs may not be mapped to some ROs that do not belong to a combined period. The above-described method can be applied to ROs mapped in SD resources. In other words, among the ROs mapped in SD resources, RO(s) belonging to a combined period mapped in ND resources can be considered as valid RO(s). The combined period for a valid RO mapped in SD resources may not be derived separately, and the combined period mapped in ND resources can be applied to SD resources.

[0327] RO Validity (Ngap)

[0328] Ngap may denote a minimum gap between an SSB and an RO. The SSB may be received in a DL symbol or an FL symbol. According to the proposed method, a base station performing SBFD operation may transmit an SSB in an SD symbol. The SSB may be transmitted in a non-UL subband (e.g., a DL subband) of the SD symbol. A terminal may monitor an SSB in an SD resource. To support the above-described operation, a set of ROs may be defined in the SD resource, and the set of ROs defined in the SD resource may be indicated to the terminal. A terminal supporting a half-duplex mode may select (e.g., perform) one operation between an SSB monitoring operation in an SD symbol and a PRACH preamble transmission operation in an RO (or a group of ROs).

[0329] According to the proposed method, a terminal can consider an RO that has been in operation for a preset time period since the last symbol in which an SSB was received as a valid RO. A valid RO may refer to an RO that is the target of SSB-RO mapping. The preset time period may include the processing time required for switching (e.g., changing) the RF chain for SSB reception and PRACH preamble transmission.

[0330] According to the proposed method, the terminal can transmit the PRACH preamble in an RO that has been set to a preset time after the last symbol in which the SSB was received. The above-described embodiment may mean that SSB-RO mapping is performed regardless of the SSB timing pattern. The RO actually selected by the terminal may be an RO that has been set to a preset time after the SSB reception time.

[0331] Preamble repetition

[0332] When a terminal performs repeated PRACH transmission, the terminal can transmit a PRACH preamble in a valid RO. In repeated PRACH transmission, the terminal can transmit the PRACH preamble more than twice. According to the proposed method, a valid RO can change according to an SSB pattern (e.g., an SSB time pattern). Alternatively, a valid RO can be determined independently of the SSB pattern. The RO actually selected by the terminal can be adjusted. If a valid RO is determined independently of the SSB pattern, the SSB pattern may not be considered to derive an RO group. The terminal can consider the SSB pattern to determine whether to transmit a preamble (e.g., a PRACH preamble). The terminal can perform a preamble transmission or drop the preamble transmission considering the SSB pattern. Since dropping of the preamble transmission may occur, the number of RO(s) on which the preamble is actually transmitted may be smaller than the size of the RO group (e.g., the number of RO(s) belonging to the RO group). The size of the RO group may correspond to the number of ROs corresponding to the number of times the preamble is intended to be transmitted. The terminal may select an RO group such that at least one RO is used for preamble transmission.

[0333] The above-described methods can be applied to Type 1 RACH procedures and / or Type 2 RACH procedures. The above-described methods can be applied to CBRA procedures and / or CFRA procedures.

[0334] CFRA procedures

[0335] The PRACH mask index for the CFRA procedure can be indicated to the UE. The CFRA procedure can be triggered by a higher layer or by a PDCCH order. In this case, the UE can derive an RO (or a group of ROs) by considering the PRACH mask index.

[0336] A PRACH mask index may be set in the terminal, and a method for interpreting the RO index will be proposed. In a set of ROs mapped to ND resources (e.g., UL symbols and / or FL symbols), one RO index (e.g., one RO indexing) may be considered. In a set of ROs mapped to SD resources (e.g., SD-DL symbols and / or SD-FL symbols), it may be desirable to introduce a new RO index (e.g., a new RO indexing).

[0337] According to the proposed method, the interpretation method of the RO index can be changed depending on the RO set applied by the terminal. The method defined in the technical specification can be used in the RA procedure using the RO set mapped from the SD resource (or ND resource). The RO indexing method for the RA procedure using the RO set mapped from the ND resource and the SD resource can be defined. Based on the above-described method, the RO index can be derived.

[0338] According to the proposed method, a PRACH mask index can be indicated to a terminal for each RO set. The PRACH mask index applied to the RO set mapped in the ND resource may be different from the PRACH mask index applied to the RO set mapped in the SD resource. RO indexing can be performed based on the above-described method. For example, the SSB-RO mapping considered in the ND resource and the SSB-RO mapping considered in the SD resource can be performed independently. The preamble index used in the CFRA procedure can be indicated for each RO set.

[0339] For example, a terminal may receive a PDCCH order for a CFRA procedure. The DCI format that triggers the CFRA procedure may include a separate field that explicitly indicates the set of ROs on which the terminal performs the CFRA procedure.

[0340] According to another proposed method, a single PRACH mask index can be indicated to the terminal, and a single PRACH mask index can be commonly applied to the RO set mapped to the ND resource and the RO set mapped to the SD resource. The PRACH mask index can be introduced for load balancing for msg1 transmission. The PRACH mask index can reduce the demodulation burden for msg1 at the base station. The preamble index used in the CFRA procedure can be indicated to the terminal for each RO set.

[0341] According to another proposed method, one PRACH mask index can be indicated to the terminal, and one PRACH mask index can be applied to one of the RO sets mapped on ND resources and the RO sets mapped on SD resources. The RA configuration indicated to the terminal can include information indicating the resource type (e.g., ND resources or SD resources) to which the RA configuration (e.g., PRACH mask index) is applied. There may be no explicit signaling regarding the resource type to which the PRACH mask index is applied. A default operation for the above-described situation can be introduced. For example, the terminal can perform the CFRA procedure on the RO set mapped on ND resources. Alternatively, the terminal can perform the CFRA procedure on the RO set mapped on SD resources.

[0342] In method 1 (e.g., a method using one RA configuration information (e.g., one RACH configuration information)), the terminal can receive information from the base station through signaling (e.g., higher layer signaling) indicating the resource type (e.g., SD resource or ND resource) to which the CFRA procedure is applied.

[0343] In Method 2 (e.g., a method using two RA configuration information (e.g., two RACH configuration information)), the following methods may be applied. The UE may receive information indicating the RA configuration information used for the CFRA procedure from the base station through signaling (e.g., higher layer signaling). As another example, the UE may perform the CFRA procedure in the RO set to which the ND resources are mapped. In other words, the UE may perform the CFRA procedure using RA configuration information (e.g., existing RA configuration information) rather than additional RA configuration information.

[0344] According to the proposed method, a terminal can select an SD resource or an ND resource using SS-RSRQ. SS-RSRQ can be measured on each of the SD resource and the ND resource. Once an SD resource or an ND resource is selected, the terminal can derive a set of ROs associated with the selected resource. The terminal can select an RO belonging to the earliest SSB-RO mapping cycle and transmit msg1 using the selected RO. The above-described method can be applied to a CFRA procedure triggered by signaling (e.g., higher layer signaling) and / or a CFRA procedure triggered by a PDCCH order.

[0345] In the embodiments of FIGS. 13 and 14, the terminal can perform RO indexing for a set of ROs mapped from SD resources.

[0346] In the embodiments of FIGS. 15 and 16, the terminal may use a RO set mapped to an ND resource and a RO set mapped to an SD resource. In the embodiment of FIG. 15, the terminal may map independent SSB indices to each of the ND resource and the SD resource. In this case, the PRACH mask index may mean an RO index mapped to one of the ND resource and the SD resource. The PRACH mask index may be defined in a technical specification. For example, the PRACH mask index may be defined as an RO index mapped to an ND resource. Alternatively, the resource type (e.g., ND resource or SD resource) associated with the PRACH mask index may be indicated to the terminal by signaling (e.g., higher layer signaling). In the embodiment of FIG. 16, the RO set mapped to the ND resource may be considered first, and then the RO set mapped to the SD resource may be considered. In the same order as or similar to the order described above, the RO index for the PRACH mask index may be considered to be referred to.

[0347] RO Validity (Time Domain)

[0348] A single RO can be mapped to an ND resource or an SD resource. One PRACH configuration index may indicate a set of ROs belonging to an ND resource and / or an SD-FL symbol, and another PRACH configuration index may indicate a set of ROs belonging to an SD resource and / or an SD-DL symbol. Alternatively, one PRACH configuration index may indicate a set of ROs belonging to each of "ND resources and / or SD-FL symbols" and "SD resources and / or SD-DL symbols." A single RO (e.g., a single RACH slot) may include multiple UL symbols or multiple non-UL symbols (e.g., an FL symbol, a DL symbol, and / or an SD symbol). In this case, methods for interpretation and SSB mapping of the single RO may be required.

[0349] Figure 17 is a conceptual diagram illustrating a first embodiment in which one RO is mapped across SD symbols and non-SD symbols.

[0350] Referring to FIG. 17, RO (1510) may include SD symbols and non-SD symbols (e.g., FL symbols and / or UL symbols). RO (1510) may be a special RO. RO (1520) may include non-SD symbols (e.g., FL symbols and / or UL symbols). RO (1520) may be a legacy RO. The symbol pattern may be indicated to the terminal by signaling (e.g., RRC signaling). Alternatively, the symbol pattern may be indicated to the terminal by common DCI (e.g., group common DCI). RO may be divided into a set of ROs mapped in SD resources (e.g., ROs belonging to the RO set) and a set of ROs mapped in ND resources (e.g., ROs belonging to the RO set).

[0351] According to the conventional technical specifications, an RO mapped to an UL symbol may be judged as a valid RO, and an RO mapped to an FL symbol may not be judged as a valid RO. According to the proposed method, when an SD symbol is indicated (e.g., set) to a terminal and one RO includes an SD symbol and a non-SD symbol, RO validity determination can be performed on the FL symbol and UL symbol constituting the non-SD symbol. The above-described method can be illustrated in FIG. 18. Alternatively, RO validity determination can be performed on a non-SD symbol composed of an FL symbol or a UL symbol. The above-described method can be illustrated in FIG. 19. RO validity determination can be performed on an RO composed of a non-SD symbol. The above-described method can be illustrated in FIG. 20.

[0352] According to the proposed method, if an RO includes at least one SD symbol and at least one non-SD symbol, the validity of the RO can be derived based on the validity of the RO resource belonging to the SD symbol.

[0353] Figure 18 is a conceptual diagram illustrating a second embodiment in which one RO is mapped across SD symbols and non-SD symbols.

[0354] Referring to Fig. 18, non-SD symbols included in an RO may include FL symbols and UL symbols. If the frequency resources of an RO mapped to a non-UL symbol (e.g., an SD symbol and an FL symbol) belong to a UL subband (or a UL subband and a guard band), the terminal may determine the RO as a valid RO. The validity of the RO may be additionally determined by considering the interval between the SSB and the RO in the time domain.

[0355] Figure 19 is a conceptual diagram illustrating a third embodiment in which one RO is mapped across SD symbols and non-SD symbols.

[0356] Referring to Fig. 19, non-SD symbols included in an RO may include only FL symbols. If the non-SD symbols included in an RO include only UL symbols, the RO may be determined to be a valid RO. In other words, if the non-SD symbols included in an RO include only UL symbols, the RO validity may be determined based on the validity of the SD symbol(s) included in the RO. On the other hand, if the non-SD symbols included in an RO include only FL symbols, the method for determining the RO validity may be different. According to the proposed method, if the frequency resources of an RO mapped to an SD symbol belong to a UL subband (or a UL subband and a guard band), the terminal may determine the RO to be a valid RO. In other words, the validity of an RO mapped to an FL symbol (e.g., some resources of an RO) may be determined based on the validity determination for an SD symbol. The RO validity may be additionally determined by considering the interval between the SSB and the RO in the time domain.

[0357] Figure 20 is a conceptual diagram illustrating a first embodiment in which one RO is mapped to a non-SD symbol.

[0358] Referring to Fig. 20, an RO may contain only non-SD symbols without SD symbols. In other words, a validity determination may be performed for an RO containing only FL symbols. According to the proposed method, if an SBFD operation is instructed (e.g., configured) to a terminal, the terminal may determine an RO mapped to an FL symbol as a valid RO. If an SD symbol (e.g., an SBFD operation) is instructed to a terminal and the RO contains only non-SD symbols, the RO validity may be determined (e.g., derived) based on the validity of the RO resources belonging to the FL symbol. The RO validity may be additionally determined by considering the interval between the SSB and the RO in the time domain.

[0359] Figure 21 is a conceptual diagram illustrating a fourth embodiment in which one RO is mapped across SD symbols and non-SD symbols.

[0360] Referring to FIG. 21, resources (e.g., time resources) constituting an RO can be subdivided. An RO can include an SD-DL symbol (1810), an SD-FL symbol (1820), an FL symbol (1830), and an UL symbol (1840). The length of each symbol can be 0 or greater. The duplex of a symbol can be derived based on common slot pattern information. The duplex of a symbol can be a duplex determined by a legacy terminal. In this case, an SD-DL symbol can be regarded as a DL symbol, and an SD-FL symbol can be regarded as an FL symbol. The embodiments of FIGS. 17 to 20 can be interpreted as any embodiment of FIG. 21. The validity of an RO can be additionally determined by considering the interval between an SSB and an RO in the time domain.

[0361] FIG. 22 is a conceptual diagram illustrating an embodiment of an RO composed of SD-FL symbol(s) and / or ND-UL symbol(s).

[0362] Referring to FIG. 22, an RO (1850) consisting of only SD-FL symbols, an RO (1860) consisting of SL-FL symbol(s) and ND-FL symbol(s), and / or an RO (1870) consisting of only ND-FL symbols may be considered. An existing terminal (e.g., a legacy terminal) may regard an RO (1850) including an SD-FL symbol as a legacy RO. In this case, the RO may exceed the UL available PRB. The base station may configure the terminal to prevent the above-described situation from occurring. An RO including at least one SD-DL symbol may be determined to be a valid RO. An RO (1850) including only an SD-FL symbol may be determined to be an invalid RO. An RO (1870) including only an ND-FL symbol may be determined to be a valid RO.

[0363] SSB-RO mapping

[0364] According to the proposed method, different SSB-RO mappings can be applied to each of 'RO including SD-DL symbol(s)' and 'RO including SD-FL symbol(s) and / or non-SD symbol(s)'. In the embodiments of FIGS. 13 to 16, a UL symbol can be interpreted as a non-(SD-DL) symbol, and an SD symbol can be interpreted as an SD-DL symbol (e.g., 1810 of FIG. 21).

[0365] The RO validity determination and other procedures defined in the technical specifications may remain as is. Alternatively, the RO validity determination and other procedures defined in the technical specifications may be modified. For example, a predetermined interval may be maintained between SSB and RO in the same slot. SSB may be received before RO. A minimum time interval may be maintained between the last symbol of SSB and the first symbol of RO. RO cannot be positioned before SSB in the same slot. Since a base station supporting SBFD operation can transmit SSB in SD resources (e.g., SD-DL symbols and / or SD-FL symbols), RO can be positioned before SSB in the same slot.

[0366] A predetermined interval can be maintained between SSB (or RO) and other UL signals / channels. According to another proposed method, if SBFD operation is supported, a predetermined interval can be maintained in non-SD resources (e.g., DL symbols). The above-described operation may mean that a minimum time interval is maintained between a DL signal / channel not scheduled for a UE and the first symbol of an RO. To avoid causing CLI to other UEs, an RO that has a predetermined interval from a previous transmission may be considered a valid RO.

[0367] If the SBFD operation is not instructed (e.g., configured) to the terminal, the terminal may perform the RO validity determination procedure defined in the technical specification. In this case, the terminal may determine the above-mentioned RO as an invalid RO.

[0368] Modulo and scaling

[0369] The frequency resources of ROs belonging to SD resources (e.g., SD symbols) may be different from the frequency resources of ROs belonging to ND resources (e.g., non-SD symbols). The above situation may occur because the number of PRBs belonging to UL subbands is different from the number of PRBs belonging to UL BWPs. When ROs belonging to SD resources and ROs belonging to ND resources are indicated (e.g., configured) to a UE using one RACH configuration, the frequency resources of ROs belonging to SD resources may be different from the frequency resources of ROs belonging to ND resources. One or more ROs configured at the same time in ND resources may be indicated (e.g., configured) to the UE through signaling (e.g., RRC signaling). The number of one or more ROs may be 1, 2, 4, 8, or msg1-FDM. The value of msg1-FDM may be a natural number. The RO mapped to the lowest frequency resource among one or more ROs can be indicated (e.g., configured) to the terminal via separate signaling (e.g., separate RRC signaling). msg1-FrequencyStart can indicate the RO mapped to the lowest frequency resource among one or more ROs.

[0370] In the SD symbol where the UL subband is defined, the terminal must be able to know the number of ROs and the starting frequency resources of the ROs. The number of ROs and the starting frequency resources of the ROs can be derived using parameter(s) (e.g., RRC parameter(s)) available in the UL symbol defined in the UL BWP. In the present disclosure, the bandwidth of the UL subband may be referred to as N1 PRB (e.g., N1 PRBs), and the bandwidth of the UL BWP may be referred to as N2 PRB (e.g., N2 PRBs). Each of N1 and N2 may be a natural number.

[0371] Figure 23 is a conceptual diagram illustrating a first embodiment in which ROs are mapped to different frequency resources in SD resources and non-SD resources, respectively.

[0372] Referring to FIG. 23, the terminal can identify ROs (110, 120, 130) defined in SD resources (e.g., SD symbols, SD-DL symbols, and / or SD-FL symbols) and ROs (140) defined in ND resources (e.g., UL symbols and / or FL symbols). In each of the ROs (110, 120, 130, 140), msg1-FDM ROs can be FDMed. The terminal can derive the frequency resources of the ROs (110, 120, 130) by reinterpreting msg1-FrequencyStart, and can derive the frequency resources of the ROs (140) by directly applying msg1-FrequencyStart. The terminal can identify the start frequency resource of the first RO of the ROs (140) by applying msg1-FrequencyStart to the first PRB of the UL BWP.

[0373] The terminal can identify the starting frequency resource of the first RO of each of the ROs (110, 120, 130) by applying a predefined offset to the first PRB of the UL subband.

[0374] The terminal can perform a modulo operation so that the frequency resources of the RO belonging to the SD resource always belong to the UL subband. The terminal can derive the starting frequency (F) and / or the frequency offset (F2) of the RO based on the technical specification, and can perform a modulo operation on the starting frequency (F) or the frequency offset (F2) using the bandwidth (N1) of the UL subband. The terminal can determine F1 by performing the operation of F2 % N1, and can derive the starting frequency resource of the RO by adding F1 to the starting PRB of the UL subband. The terminal can obtain the result of performing the operation of F % N1, and the result of the operation can indicate the starting frequency resource of the RO. The terminal can derive the starting frequency resource of the RO by adding the result of the operation to the starting PRB of the UL subband. % can represent a modulo operation.

[0375] In order to ensure that the frequency resources of the RO belonging to the SD resource always belong to the UL subband, a product of an appropriate proportional constant can be utilized. For example, a scaling operation can be used. For example, floor(N2 / N1) can represent the relative ratio of the bandwidth of the UL BWP to the bandwidth of the UL subband, and floor(N2 / N1) can have a value greater than or equal to 0 and less than 1. The range of the frequency offset (F2) of the RO in the UL BWP (e.g., the frequency offset applied to the start frequency of the UL BWP) can be 0, 1, ..., N2-1. The range of the frequency offset (F1) of the RO in the UL subband (e.g., the frequency offset applied to the start frequency of the UL subband) can be 0, 1, ..., N1-1.

[0376] For example, the value of F1 can be considered as the result of F2×floor(N1 / N2). The value of F1(=F2×floor(N1 / N2)) can be 0, 1, ..., x. x can be a number less than or equal to N1-1. The terminal can derive the start frequency of the RO based on the sum of F1 and the start frequency of the UL subband.

[0377] For example, the value of F1 may not be defined separately, and the proportionality constant for the frequency resource of RO can be applied directly. F1 can be the value of floor(F2×N1 / N2). The value of F1(=floor(F2×N1 / N2)) can be 0, 1, ..., y. y can be a number less than or equal to N1-1. F1 can be used as the starting frequency of RO.

[0378] Figure 24 is a conceptual diagram illustrating a second embodiment in which ROs are mapped to different frequency resources in SD resources and non-SD resources, respectively.

[0379] Referring to FIG. 24, ROs can be FDM, and RO(s) that fall outside the UL subband can exist. msg1-FDM ROs can be arranged consecutively in the frequency domain, and the first PRB of the ROs can belong to the UL subband, but other PRBs (e.g., the last PRB) of the ROs may not belong to the UL subband. Additional modulo operations can be performed so that all ROs belong to the UL subband. ROs (110) can have the frequency resource of the first RO and can include ROs belonging to the UL subband. ROs (111) can include ROs starting from the lowest frequency of the UL subband. ROs can be obtained based on modulo operations using the size of the UL subband. In SSB-RO mapping, ROs can be mapped to SSB in ascending order of frequency. In the embodiment of FIG. 24, ROs (110, 111) can be derived. Considering the order of SSB-RO mapping, ROs (111) can be considered first, and then ROs (110) can be considered.

[0380] The same method can be applied to ROs (120, 121, 130, 131) belonging to SD resources (e.g., SD-DL resources). There may be ROs (e.g., ROs) that are distinguished into two cases. In the embodiment of Fig. 24, the proposed methods described above (e.g., modulo, scaling, etc.) can be applied to derive the first RO from which ROs (110, 120, 130) begin.

[0381] In another proposed method, ROs can be FDMed, and the frequency occupied by the ROs can be N3. N3 can indicate the number of PRBs occupied by msg1-FDM ROs to which FDM is applied. N3 can be a natural number. An operation considering N3 can be performed. The range of the starting frequency (F2) of the RO defined in the UL BWP can be 0, 1, ..., N1-1-N3. To derive the starting frequency (F1) of the RO defined in the UL subband, a modification of the above-described methods can be used.

[0382] When a modulo operation is applied, the terminal can perform a modulo operation using N1-N3. In a method in which the starting frequency of the RO is directly derived, the starting frequency (G1) of the RO in the UL subband can be the result of G2 % (N1-N3). G2 can be the starting frequency of the RO in the UL BWP. In a method in which the starting frequency offset of the RO is derived, the starting frequency offset (F1) of the RO in the UL subband can be the result of F2 % (N1-N3). F2 can be the starting frequency offset of the RO in the UL BWP.

[0383] When a scaling operation is applied, (N1-N3) / (N2-N3) can be used for the scaling operation. Considering how the starting frequency offset of the RO is derived, the starting frequency (F1) of the RO in the UL subband can be the result of F2×floor({N1-N3} / {N2-N3}). Alternatively, the starting frequency (F1) of the RO in the UL subband can be the result of floor(F2×{N1-N3} / {N2-N3}). F2 can be the starting frequency of the RO in the UL BWP.

[0384] Option 2 Settings

[0385] Figure 25 is a conceptual diagram illustrating embodiments in which one RO is scheduled across two or more slots.

[0386] Referring to FIG. 25, the slot pattern indicated to the terminal may be DDDSU. In the slot pattern (DDDSU), D may denote a DL slot, S may denote a special slot, and U may denote a UL slot. In each slot, 'D:F:U' may denote 'the number of DL symbols:the number of FL symbols:the number of UL symbols'. The base station may indicate a long format to the terminal(s) to secure wide coverage for PRACH preamble transmission. The embodiment of the present disclosure may be described with a focus on a preamble format corresponding to 1 ms (or 2 slots). The terminal may determine a valid RO (1610, 1620, 1630) based on configuration index 1, configuration index 2, and configuration index 3. The configuration index may denote a PRACH configuration index.

[0387] According to the proposed method, the terminal can determine whether the RO derived based on the configuration index belongs to a UL subband in order to determine the validity of the RO. If an RO includes a UL symbol (or a UL symbol and / or an FL symbol), the terminal can determine the RO as a valid RO. If an RO includes a UL symbol and a non-UL symbol, and the RO belongs to a UL subband of the non-UL symbol, the terminal can determine the RO as a valid RO.

[0388] According to the proposed method, in order to derive a UL subband, a guard bandwidth (e.g., a guard band) can be indicated to the terminal via signaling (e.g., RRC signaling). In order to determine RO validity, the terminal can determine whether the RO belongs to a frequency resource of a non-UL symbol (e.g., a frequency resource considering the UL subband and the guard band). If the UL subband is configured considering the guard band, the terminal may not consider the separate guard band to determine RO validity. The terminal can derive a valid UL subband (e.g., a frequency resource allowed to be used for the RO) and utilize the valid UL subband to determine the RO validity.

[0389] A terminal can determine an RO belonging to a valid UL subband as a valid RO. Time resources or the duplex type of a symbol (e.g., UL symbol or non-UL symbol) can be used as a criterion for determining RO validity. According to the proposed method, frequency resources can be used as a criterion for determining RO validity.

[0390] According to the proposed method, a terminal can determine that some symbols of an RO belonging to UL symbols are valid by considering time resources, and the terminal can determine the validity of the remaining symbols of an RO belonging to non-UL symbols by considering frequency resources. If all symbols of an RO are determined to be valid, the terminal can determine the RO as a valid RO.

[0391] If a base station supporting SBFD operation does not indicate slot pattern information to the terminal(s), the terminal can determine RO validity by using the minimum interval between an RO and an SSB among the RO set derived based on the PRACH configuration index (e.g., the time interval between the last symbol of the SSB and the first symbol of the corresponding RO).

[0392] In order to indicate the SD symbol to the terminal(s), the information of the slot pattern may include information of the SD symbol and “information on the UL subband and / or guard band.” The information of the slot pattern may be indicated to the terminal(s) through signaling. Alternatively, the information of the slot pattern may include information of the SD symbol, and the information on the UL subband and / or guard band may be indicated to the terminal(s) through separate signaling. In the embodiment of FIG. 25, RO (1610) may be mapped across the S (special) slot and the U (uplink) slot, RO (1620) may be mapped across the D (downlink) slot and the S slot, and RO (1630) may be mapped across the D slots. RO (1610) may be mapped across 14 non-UL symbols. The terminal may determine the validity of RO (1610) in the DL symbol and the FL symbol. The terminal can determine the validity of the RO (1610) by considering the UL subband and / or guard band in the DL symbol and FL symbol of the RO (1610).

[0393] To determine the validity of an RO, the terminal may consider time resources regardless of whether the Option-2 or Option-1 configuration is used. An RO determined to be valid based on the Option-1 configuration may also be determined to be valid based on the Option-2 configuration. An RO determined to be invalid based on the Option-1 configuration may also be determined to be invalid based on the Option-2 configuration. The above-described operation may imply that the embodiments of FIGS. 17 to 21 are applicable as is.

[0394] Considering the Option-2 configuration, multiple PRACH configuration indices may be indicated to the terminal, and the multiple PRACH configuration indices may include a first PRACH configuration index and a second PRACH configuration index. The legacy RO set and the additional RO set may be derived based on the first PRACH configuration index. The legacy RO set and the additional RO set may be derived based on the second PRACH configuration index.

[0395] According to the proposed method, among the RO sets derived based on the first PRACH configuration index, the legacy RO set can be determined to be valid, and among the RO sets derived based on the second PRACH configuration index, the additional RO set can be determined to be valid. The procedure for determining RO validity can be performed based on the method(s) described above.

[0396] A base station supporting SBFD operation can change the connection status of an antenna at the boundary of a slot. The above-described operation can be illustrated in the embodiments of FIGS. 6 to 8. When the connection status of an antenna of a base station changes at the boundary between an S slot and a U slot, the terminal can determine the RO (e.g., a set of ROs) mapped to the S slot and the U slot as a valid RO or an invalid RO.

[0397] Referring again to FIGS. 6 and 8, the receiver of the base station may not be changed in the SD symbol, the UL symbol, and / or the FL symbol. Even if the RO is mapped to the SD symbol, the UL symbol, and / or the FL symbol, the base station can normally demodulate the PRACH preamble received in the RO.

[0398] Referring again to FIG. 7, the receiver of the base station can change between SD symbols, UL symbols, and / or FL symbols. Even when the RO is mapped to the SD symbol, UL symbol, and / or FL symbol, the base station must perform a complex algorithm to receive the PRACH preamble because the gain changes while receiving the PRACH preamble in the RO.

[0399] When the base station is implemented based on the embodiment illustrated in FIG. 6 or FIG. 8, an RO mapped in an SD symbol, an UL symbol, and / or an FL symbol may be determined as a valid RO. When the base station is implemented based on the embodiment illustrated in FIG. 7, an RO mapped in an SD symbol, an UL symbol, and / or an FL symbol may not be determined as a valid RO. According to the proposed method, a terminal can determine an RO mapped in an SD symbol, an UL symbol, and / or an FL symbol as a valid RO or an invalid RO based on signaling (e.g., RRC signaling) of the base station. The signaling can indicate an implementation state of the base station (e.g., a base station based on the embodiment illustrated in FIG. 6 or FIG. 8 or a base station based on the embodiment illustrated in FIG. 7). Through the signaling, the base station can indirectly inform the terminal of the implementation state of the base station.

[0400] Referring again to FIG. 25, RO (1610) and RO (1620) can be mapped across SD symbols, UL symbols, and FL symbols. The terminal can determine each of RO (1610) and RO (1620) as a valid RO or an invalid RO based on the signaling described above (e.g., signaling indicating the implementation status of the base station).

[0401] SSB-RO mapping

[0402] If an RO mapped in an SD symbol and an ND symbol (e.g., a UL symbol and / or an FL symbol) is determined to be a valid RO, the RO may be regarded as an RO supported by the PRACH configuration index (or SD-RO) mapped in the SD symbol.

[0403] Referring back to FIG. 25, configuration index 3 (e.g., PRACH configuration index 3) may configure (e.g., indicate) a RO (1630) mapped on an SD symbol (e.g., an SD-DL symbol). The RO set may follow the SSB-RO mapping between RO sets mapped on the ND resource of the SD symbol. Configuration index 1 (e.g., PRACH configuration index 1) may configure (e.g., indicate) a RO (1610) mapped on an UL resource (e.g., an SD symbol, a UL symbol, an FL symbol). Configuration index 2 (e.g., PRACH configuration index 2) may configure (e.g., indicate) a RO (1620) mapped on an UL resource (e.g., an SD symbol, a UL symbol, an FL symbol). The above-described ROs may be considered as a set of ROs mapped on UL symbols and / or FL symbols. The above-described RO can be considered as a set of ROs mapped from UL resources and / or FL resources of SD symbols.

[0404] According to the proposed method, ROs (1610, 1620, 1630) illustrated in FIG. 25 can be considered as a set of ROs mapped from SD resources. Since ROs (1610, 1620, 1630) are mapped from time resources that include at least SD resources, validity determination for ROs (1610, 1620, 1630) can be performed. For ROs judged to be valid among ROs (1610, 1620, 1630), SSB-RO mapping for the set of ROs mapped from SD resources can be performed.

[0405] CFRA

[0406] When the CFRA procedure is triggered, the terminal may select a set of ROs associated with (e.g., mapped to) the SSB in the earliest SSB-RO mapping cycle after the information triggering the CFRA procedure is transmitted to the L1 (layer 1) layer of the terminal. When the CFRA procedure is triggered by the PDCCH order, the terminal may perform the above-described procedure using a DCI format scrambled by the C-RNTI.

[0407] Considering a terminal supporting Method 2, the set of ROs mapped to ND resources can be derived using RA settings, and the set of ROs mapped to SD resources can be derived using additional RA settings. Since the CFRA procedure is performed by a single RA trigger event, the terminal must select SD resources and / or ND resources.

[0408] According to the proposed method, information for performing the CFRA procedure can be set separately for two RA settings.

[0409] According to the proposed method, the base station can use signaling (e.g., higher layer signaling) to indicate to the terminal one RA configuration associated with the CFRA procedure. The terminal can identify one RA configuration associated with the CFRA procedure based on the signaling from the base station. In this case, the procedure for the terminal to select SD resources and / or ND resources may be unnecessary. For example, the PRACH mask (e.g., PRACH mask index) can be indicated to the terminal for each RA configuration (e.g., RA configuration index).

[0410] According to another proposed method, the terminal can select SD resources and / or ND resources using SS-RSRQ. In this case, the terminal can derive the RO set by selecting the CFRA resources associated with the RA configuration.

[0411] The PRACH mask index can be applied after the RO set is derived. Optionally, a single PRACH mask index can be applied to both the RO set mapped to ND resources and the RO set mapped to SD resources. Alternatively, a single PRACH mask index can be applied to one RO set from among the RO sets mapped to ND resources and the RO sets mapped to SD resources.

[0412] Preamble repetition

[0413] When a terminal transmits a PRACH preamble and another UL signal / channel (e.g., PRACH, SRS, PUSCH, PUCCH) in the same slot, a predefined time interval (e.g., N symbols) may be maintained between the transmission of the PRACH preamble and the transmission of the other UL signal / channel. N may be a natural number. When a PRACH (e.g., a PRACH preamble) is transmitted in a first slot and another UL signal / channel is transmitted in a second slot, a predefined time interval (e.g., N symbols) may be maintained between the transmission of the PRACH preamble and the transmission of the other UL signal / channel. N may be a value determined based on a smaller SCS among the SCS of the UL BWP in which the PRACH is transmitted and the SCS of the UL BWP in which the other UL signal / channel is transmitted.

[0414] A terminal may repeatedly transmit a PRACH preamble in different slots. The time interval between repeated transmissions of the PRACH preamble may not be less than a predefined time interval (e.g., N symbols). The first and second slots may be sequentially concatenated, and the ROs may be selected such that the time interval between the last symbol of the RO included in the first slot and the first symbol of the RO included in the second slot is not less than N symbols.

[0415] When a PRACH preamble is repeatedly transmitted, the RO set derived from SD resources and the RO set derived from non-SD resources may have different frequencies. Even if the frequencies of the RO sets are different, the UE can form a single RO group. If a predefined time interval is not secured between the RO with the changed frequency (e.g., the first RO belonging to non-SD resources) and the previous RO (e.g., the last RO belonging to SD resources), the PRACH preamble may not be transmitted. In other words, the PRACH preamble transmission may be dropped in the above situation.

[0416] How to use SD and ND resources simultaneously

[0417] An RO group may include ROs corresponding to the number of transmissions of msg1. The UE may derive the number of transmissions of msg1 based on the received strength of the SSB (e.g., RSRP). An RO group may include valid ROs associated with the same SSB. ROs belonging to an RO group may have the same frequency resources. A time offset may be applied to another RO group adjacent to an RO group. In this case, the time offset of the first ROs of the RO groups may be indicated to the UE by signaling from the base station (e.g., higher layer signaling).

[0418] According to the proposed method, a set of ROs (e.g., an RO group) for a base station and / or a terminal supporting SBFD operation may include a set of ROs mapped to ND resources or a set of ROs mapped to SD resources. In other words, ROs belonging to an RO group may have the same symbol type. When a terminal selects an SD resource or an ND resource based on a predefined rule, an RO group may be composed of ROs belonging to the selected resource (e.g., an SD resource or an ND resource).

[0419] According to another proposed method, a base station and / or a terminal supporting SBFD operation can configure an RO group using both a set of ROs mapped from ND resources and a set of ROs mapped from SD resources. When the size of an RO group is defined as M, M can be the sum of M1 and M2. M1 ROs in the RO group can belong to the set of ROs mapped from ND resources, and msg1 can be transmitted using the M1 ROs. M2 ROs in the RO group can belong to the set of ROs mapped from SD resources, and msg1 can be transmitted using the M2 ROs. Each of M, M1, and M2 can be a natural number. The method of dividing M into M1 and M2 can be defined in a technical specification. Alternatively, M, M1, and / or M2 can be fixed values. Alternatively, M, M1, and / or M2 can be configured to the terminal by signaling from the base station. The terminal can perform the CBRA procedure or the CFRA procedure by applying the above-described method.

[0420] For example, M, M1, and M2 can be fixed as M1=M2=M / 2. An RO group can be divided into one or more RO subgroups. The RO subgroups can be set in each of the SD resources and ND resources.

[0421] According to the proposed method, among the RO subgroups, one RO subgroup (e.g., an RO subgroup in an SD resource or an RO subgroup in an ND resource) can be temporally selected first by technical specifications or signaling (e.g., upper layer signaling). For example, the first RO belonging to an RO subgroup associated with an ND resource can be selected first, and then the first RO belonging to an RO subgroup associated with an SD resource can be selected. Alternatively, the first RO belonging to an RO subgroup associated with an SD resource can be selected first, and then the first RO belonging to an RO subgroup associated with an ND resource can be selected.

[0422] According to another proposed method, the order of RO subgroups can be derived based on the symbol type of the RO that occurs first with respect to the subframe boundary of the BWP or the radio frame boundary. Since the SBFD pattern period is not always the same as the TDD pattern period, the RO subgroup containing the RO mapped from the ND resource may be positioned earlier in the time domain than the RO subgroup containing the RO mapped from the SD resource. Alternatively, the RO subgroup containing the RO mapped from the SD resource may be positioned earlier in the time domain than the RO subgroup containing the RO mapped from the ND resource.

[0423] According to the proposed method, the ra-SearchSpaceSet for receiving msg2 can start from the last RO belonging to the RO group. In other words, the random access response (RAR) window can start from the last RO belonging to the RO subgroup associated with the last transmitted PRACH preamble.

[0424] According to the proposed method, the size of the RO subgroup can be M1 or M2, and the size of the preamble set can be determined by the size (M) of the RO group. The terminal can determine the preamble set based on the function combination. The preamble set (or function set) can be set according to the number of transmissions of the PRACH preamble. For example, the number of transmissions of the PRACH preamble for the first preamble set (or the first function set) can be different from the number of transmissions of the PRACH preamble for the second preamble set (or the second function set). Based on the RO subgroup, the number of transmissions of the PRACH preamble for the preamble set can be regarded as M1 or M2. In other words, the size of the preamble set (M1 or M2) can be regarded as the number of transmissions of the PRACH preamble. According to the proposed method, the size of the RO group (M) can be considered as the number of transmissions of the PRACH preamble, and M can be considered as the size of the preamble set.

[0425] SBFD-PRACH TPC(transmit power control), BI(backoff indicator), timer

[0426] The method(s) for a camping terminal to transmit a PRACH (e.g., a PRACH preamble) at a base station performing SBFD operation will be described.

[0427] A terminal can select a set of ROs, select an RO (or a group of ROs) within the selected set of ROs, and transmit a PRACH to a base station from the ROs. PRACH configuration information can be derived from a SIB. The Tx beam for the PRACH can be derived based on the Rx beam of the SSB selected by the terminal. The power allocated for PRACH transmission can compensate for path loss to match the value defined by preambleReceivedTargetPower. The path loss can be derived based on the RSRP measured based on the SSB selected by the terminal.

[0428] Interference between terminals may occur depending on the implementation of the base station performing SBFD operation, the type of SD resources, the size of the guard band, and / or the amount of guard symbols. Interference between terminals may be CLI. A PRACH transmission by a terminal may act as CLI for DL ​​reception by another terminal geographically adjacent to the terminal.

[0429] When a terminal selects an RO mapped from an ND resource, it does not need to consider the CLI. When a terminal selects an RO mapped from an SD resource, it may need to consider the CLI.

[0430] electrical energy

[0431] According to the proposed method, when a terminal transmits a PRACH in an RO mapped to SD resources, reduced power can be allocated to the PRACH. In other words, the terminal can transmit the PRACH using reduced power.

[0432] For example, a SIB may include two or more preambleReceivedTargetPowers. The transmit power of a PRACH applied in an ND resource and the transmit power of a PRACH applied in an SD resource may be distinguished.

[0433] For example, a SIB may include one preambleReceivedTargetPower and a power offset. The transmit power of a PRACH in an ND resource (e.g., an UL resource and / or an FL resource) may be determined based on the preambleReceivedTargetPower, and the transmit power of a PRACH in an SD resource may be determined by applying a power offset to the transmit power of the PRACH in the ND resource.

[0434] For example, two or more P CMAX,f,c can be derived based on SIB. One P CMAX,f,c can be applied to the transmission power of PRACH in ND resources (e.g., UL resources and / or FL resources). Other P CMAX,f,c can be applied to the transmission power of PRACH in SD resources. SD resources can be divided into SD-DL symbols (e.g., DL symbols) and SD-FL symbols. Different P can be applied to the transmission power of PRACH in each of the SD-DL symbols and SD-FL symbols. CMAX,f,c can be applied. To support the above-described operations, the SIB must have two or more P CMAX,f,c may include. Or SIB is a criterion P CMAX,f,c and may include one or more power offsets.

[0435] For the same SSB (e.g., SSBs having the same SSB index), SS-RSRP measured on DL resources and SS-RSRP measured on SD resources can be distinguished, and the two SS-RSRPs can be transmitted from the physical layer of the terminal to the upper layer of the terminal. When the terminal selects one RO from the set of ROs mapped on the SD resource, the SSB index used to select the one RO may be the SSB index for the SSB received on the SD resource. When the terminal selects one RO from the set of ROs mapped on the ND resource, the SSB index used to select the one RO may be the SSB index for the SSB received on the ND resource.

[0436] ramping counter

[0437] A ramping counter can be used to determine the amount of increase in the transmit power of msg1 during the retransmission procedure of msg1. The amount of increase in the transmit power of msg1 can be determined based on the ramping counter and the ramping step. The ramping counter can be related to the number of retransmissions of msg1. The value of the power ramping can be determined based on the product of the ramping counter and the ramping step (or the product of the ramping counter-1 and the ramping step).

[0438] According to the proposed method, the same ramping counter can be applied to a set of ROs mapped from SD resources and a set of ROs mapped from ND resources.

[0439] According to another proposed method, the ramping counter applied to the set of ROs mapped from the SD resource may be different from the ramping counter applied to the set of ROs mapped from the ND resource.

[0440] According to the proposed method, there can be one ramping step (e.g., power ramping step), and the ramping step can be applied equally to ND resources and SD resources.

[0441] According to another proposed method, there may be two or more ramping steps (e.g., power ramping steps). One of the two or more ramping steps may be applied to the transmit power of a PRACH transmitted on an ND resource (e.g., an UL resource and / or an FL resource). Another of the two or more ramping steps may be applied to the transmit power of a PRACH transmitted on an SD resource. The values ​​for the two or more ramping steps may be included in the SIB. Alternatively, the value for a reference ramping step and one or more offsets may be included in the SIB.

[0442] BI(backoff indicator)

[0443] A method of applying BI in a PRACH retransmission procedure of a terminal camping on a base station performing SBFD operation can be described.

[0444] A terminal can transmit msg1 to a base station and receive msg2 from the base station in response to msg1. The terminal can determine whether contention has been resolved based on the information contained in msg2. If contention has not been resolved (e.g., contention exists), the terminal can obtain the maximum value of the probability variable based on the BI contained in msg2. Using the maximum value of the probability variable, the terminal can derive a slot for retransmitting msg1.

[0445] According to the proposed method, msg2 can indicate BI by symbol type (e.g., ND symbol or SD symbol). The terminal can apply different BI values ​​based on the symbol type (e.g., ND symbol or SD symbol) of the resource through which msg1 is transmitted.

[0446] Repeat transmission

[0447] The number of repeated transmissions of msg1 can be defined as M. M can be a natural number. The RO group can be divided into two RO subgroups. In this case, the number of repeated transmissions of msg1 in the first RO subgroup can be M1, and the number of repeated transmissions of msg1 in the second RO subgroup can be M2. Each of M1 and M2 can be a natural number. The sum of M1 and M2 can be M. A situation requiring retransmission of msg1 may occur. The above-described situation can be confirmed based on the reception result of msg2 in the RA window (e.g., RAR window) derived based on the last RO belonging to the RO group.

[0448] When RO subgroups are defined for different symbol types and a single BI is defined, the terminal can use a single BI. When BIs are defined for different symbol types, the terminal may not know which BI to use. The BI for an RO subgroup mapped to SD resources can be defined as BI-SD. The BI for an RO subgroup mapped to ND resources can be defined as BI-ND.

[0449] According to the proposed method, the terminal can apply the BI associated with the symbol type to the RO subgroup to which the RO to which the last msg1 was transmitted belongs. For example, if BI-ND (or BI-SD) is obtained in msg2, the terminal can determine a random number based on the BI-ND (or BI-SD) and retransmit msg1 based on the random number.

[0450] A terminal may not be able to infer the BI of a different symbol type based on the BI for one symbol type. Even if an arbitrary number is determined and BI-ND is the maximum value, considering BI-SD, the above-described method may not be a fair way to resolve contention for the set of ROs mapped to SD resources.

[0451] In another proposed method, the terminal can perform retransmission of msg1 by considering both BI-SD and BI-ND. The terminal can determine a first random number using BI-SD and a second random number using BI-ND. The terminal can determine a single random number based on a combination of the first and second random numbers, and use the single random number to derive an RO for transmitting msg1.

[0452] For example, the terminal may select one random number having a larger value from among the first random number and the second random number, and an RO subgroup may start from a symbol type associated with the one random number. Since one random number having a larger value from among the first random number and the second random number is selected, a fair backoff operation may be performed for the set of ROs mapped to the ND resource and the set of ROs mapped to the SD resource. The RO subgroup may be determined such that the ROs mapped to a specific symbol type occur first in the time domain, and the RO subgroup may be determined such that the ROs mapped to another symbol type occur later in the time domain. The order between the RO subgroups in the time domain may be determined such that the set of ROs mapped to the ND resource is selected first.

[0453] Preamble repetition with dropping

[0454] A terminal can perform PRACH repeated transmission. The number of PRACH repeated transmissions can be 2 or more. If the terminal can use both an RO set mapped to SD resources and an RO set mapped to ND resources, the terminal can select two or more RO groups to perform PRACH repeated transmission. ROs belonging to an RO group (e.g., the same RO group) can have the same frequency resources. The terminal can transmit PRACH while maintaining the same Tx beam in the ROs belonging to the RO group.

[0455] If ROs belonging to an RO group belong to different slots (e.g., adjacent slots), a PRACH transmission in any RO belonging to a slot may be dropped. For example, a PRACH transmission in an RO belonging to the second slot may be dropped. A PRACH may be transmitted in a valid RO belonging to the first UL slot among different UL slots, and a PRACH transmission may be dropped in a valid RO belonging to the second UL slot among different UL slots.

[0456] According to the proposed method, ROs belonging to SD resources and ROs belonging to ND resources can be arranged consecutively in the time domain, and ROs belonging to SD resources and ROs belonging to ND resources can belong to the same RO group. A terminal can transmit a PRACH in one of the ROs belonging to SD resources and ROs belonging to ND resources, and can drop the PRACH transmission in the remaining ROs. Since the physical layer of the terminal is involved in the dropping operation of PRACH transmission, the dropping operation of PRACH transmission may not affect the configuration operation of the RO group.

[0457] An RO belonging to an SD resource and an RO belonging to an ND resource may belong to the same slot. In this case, based on the implementation of the base station performing the SBFD operation, the processing operation applied to the SD resource and the processing operation applied to the ND resource may be changed. Alternatively, the processing operation applied to the SD resource and the processing operation applied to the ND resource may be maintained. In the embodiments of FIGS. 6 and 8, the connection state between the Rx chain of the base station and the panel element may be maintained in the SD resource and the ND resource. In the embodiment of FIG. 7, the connection state between the Rx chain of the base station and the panel element may be changed in the SD resource and the ND resource. Even if an RO belonging to an SD resource and an RO belonging to an ND resource belong to the same slot, if the RO belonging to the SD resource and the RO belonging to the ND resource form one RO group, the PRACH transmission in one of the ROs may be dropped. For example, a PRACH transmission in an RO that is later in the time domain among the ROs may be dropped. The above-described embodiment can also be applied to cases where ROs belonging to SD resources and ROs belonging to ND resources belong to different slots.

[0458] RO validity

[0459] PRACH repetition or preamble repetition can be considered. ROs associated with the same SSB can form an RO group. ROs belonging to an RO group can have the same frequency resources. All ROs belonging to an RO group can be valid ROs. If an RO belongs to an UL symbol or an FL symbol, a minimum gap (Ngap) between an SSB and an RO can be secured. Considering a base station performing SBFD operation, a terminal can perform preamble repetition transmission using at least one of an RO set belonging to SD resources or an RO set belonging to ND resources. Alternatively, the terminal can perform preamble repetition transmission in a subset (e.g., an RO subset) of one of the RO set belonging to SD resources or the RO set belonging to ND resources.

[0460] In the embodiments of FIGS. 23 and 24, the terminal may perform preamble repetition transmission in all RO sets. The RO sets may be divided into a first RO set (110, 120, 130) defined by SD symbols (e.g., SD-DL symbols and / or SD-FL symbols) and a second RO set (140) defined by ND symbols (e.g., UL symbols and / or FL symbols). If the first RO in each of the RO sets has the same frequency resource, and the first RO set (110, 120, 130) and the second RO set (140) have the same frequency resource, the terminal may configure an RO group.

[0461] According to different interpretations of the same index (e.g., the same frequency index), the frequency resources allocated to the second RO set (140) may be different from the frequency resources of the first RO set (110, 120, 130). For example, a modulo operation or a scaling operation for the starting frequency indices (F1 and F2) may be performed using the number of UL-available PRBs (or a value derived based on the number of UL-available PRBs). In this case, F1 and F2 having different values ​​(e.g., different offsets) may be obtained.

[0462] Since the condition that RO groups have the same frequency resources is not satisfied, the proposed method allows a terminal to configure an RO group only with ROs having the same frequency. The above-described embodiment may mean that a longer PRACH combining period, a longer PRACH combining pattern period, and / or a longer time period are derived.

[0463] According to another proposed method, the terminal can set an RO group for the set of ROs mapped from the SD resource and an RO group for the set of ROs mapped from the ND resource. There may be no intersection between the RO group for the set of ROs mapped from the SD resource and the RO group for the set of ROs mapped from the ND resource.

[0464] According to another proposed method, a terminal can establish an RO group for all RO sets, and ROs with different frequency resources can belong to a single RO group. At the boundary where frequency resources change, preamble transmission may not be performed in any RO.

[0465] Figure 26 is a conceptual diagram illustrating a third embodiment in which ROs are mapped to different frequency resources in SD resources and non-SD resources, respectively.

[0466] Referring to FIG. 26, RO sets (110, 120, 130, 140) can be configured, and some of the RO sets (110, 120, 130, 140) can be configured as RO groups. The RO set (140) can be configured across SD resources and ND resources. The terminal can determine an RO as a valid RO or an invalid RO based on the RRC configuration.

[0467] Two RACH configurations can be indicated to a terminal. The terminal can derive an RO set (e.g., a legacy RO set) from ND resources (e.g., UL symbols and / or FL symbols) based on a certain RACH configuration (e.g., a legacy RACH configuration). The terminal can derive an RO set (e.g., an additional RO set) from SD resources based on an additional RACH configuration. The RO (140) derived based on the additional RACH configuration can be configured across SD symbols (e.g., SD-DL symbols and / or SD-FL symbols) and other symbols (e.g., ND symbols, other symbols). The terminal can determine the validity of the RO set (140) based on the RRC configuration indicated to the terminal. The terminal can determine the RO set (140) as a valid RO set or an invalid RO set. If the RRC configuration is not indicated to the terminal, the terminal can determine the RO set (140) as an invalid RO set.

[0468] The terminal can set up an RO group using four RO sets (110, 120, 130, 140). The RO set can mean RO. If the terminal determines the RO set (140) as a valid RO set, the four RO sets (110, 120, 130, 140) can belong to the RO group. If the terminal determines the RO set (140) as an invalid RO set, the three RO sets (110, 120, 130) and other RO sets can belong to the RO group. The other RO sets can be RO sets belonging to a subsequent cycle.

[0469] Figure 27 is a conceptual diagram illustrating a fourth embodiment in which ROs are mapped to different frequency resources in SD resources and non-SD resources, respectively.

[0470] Referring to FIG. 27, the size of the RO group may be 8. For example, the RO group may include 8 RO sets (110, 120, 130, 140, 150, 160, 170, 180). The first symbol of the RO set (150) may be mapped to an SD resource (e.g., an SD-DL resource), and the last symbol of the RO set (150) may be mapped to an ND resource (e.g., an UL resource and / or an FL resource). The RO set (150) may be determined as a valid RO set or an invalid RO set based on the RRC configuration.

[0471] According to the proposed method, the terminal can set up one RO group using RO sets (110, 120, 130, 140, 150, 160, 170, 180). If the RO set (150) is determined to be a valid RO set, the terminal can drop preamble transmission in the RO set (160). Alternatively, even if the RO set (150) is determined to be a valid RO set, the terminal can drop preamble transmission in the RO set (150) and transmit a preamble in the RO set (160).

[0472] According to another proposed method, if the RO set (150) is determined to be a valid RO set and the gap between the RO set (150) and the RO set (160) is greater than or equal to a predefined gap, the terminal can transmit a preamble in both the RO set (150) and the RO set (160).

[0473] Fallback behavior

[0474] The terminal can operate based on either Method 1 or Method 2. The terminal can select an RO set from either the legacy RO set or the additional RO set. For example, the terminal can select an RO set based on SS-RSRQ. Alternatively, the terminal can select an RO set based on another metric.

[0475] Different parameters or different values ​​of the same parameter can be applied for the RA procedure in different RO sets.

[0476] The terminal can select an additional RO set. The additional RO set can be defined in the SD symbol. To reduce self-interference from the camping cell, serving cell, and / or TRP, the terminal can use a lower transmit power. If the terminal uses a lower transmit power, the maximum self-interference that the TRP must remove may be reduced.

[0477] To reduce self-interference, a small transmit power may be used for msg1 transmission. To support the above-described operation, the UE may be located at the center of the SIB1 coverage of the camping cell. SIB1 coverage may refer to an area where SIB1 reception is possible. The UE may attempt to transmit msg1 in an additional RO set and, for various reasons, may not obtain a UL grant (e.g., an RAR UL grant) in msg2. This may be due to persistent contention for resources for the RA procedure (e.g., an additional RO set, an RAR window).

[0478] In the above situation, msg1 may be repeatedly transmitted, and the ramping counter may reach its maximum value. Before the ramping counter reaches its maximum value, the transmit power of msg1 may reach its maximum value. In this case, the terminal may restart the RA procedure. In other words, the terminal may perform the SSB selection (e.g., reselection) operation again.

[0479] According to the proposed method, if a terminal continuously fails the RA procedure in an additional RO set, the terminal can re-perform the RA procedure in a legacy RO set. The terminal can change the RO set without performing an SSB selection (e.g., reselection) operation. When the RO set for the RA procedure is changed, the ramping counter and / or the contention resolution timer can be reset. The power level can be recalculated. If a terminal continuously fails the RA procedure in a legacy RO set, the terminal can re-perform the SSB selection (e.g., reselection) operation.

[0480] Preamble repetition

[0481] In the RA procedure, a case in which a terminal selects an additional RO and a case in which preamble repetition is indicated to the terminal may be considered. In the above-described case(s), one or more PRACH configuration indices indicated to the terminal may all be applied. A set of ROs (e.g., ROs) selected by the terminal in an SD resource may be regarded as an additional RO set. The additional RO set may refer to a set of ROs mapped in the SD resource based on one PRACH configuration index. Based on at least one of the two PRACH configuration indices, the set of ROs mapped in the SD resource may be determined to be a valid set of ROs. In other words, a set of ROs derived based on at least one PRACH configuration index may be a valid set of ROs.

[0482] If a terminal selects an additional RO set, the terminal may be considered a terminal located at the cell center. In this case, the terminal may not perform preamble repetition transmission. Configuration information related to preamble repetition transmission may not be indicated (e.g., configured) to the terminal. Alternatively, even if configuration information related to preamble repetition transmission is indicated to the terminal, the terminal may not perform preamble repetition transmission.

[0483] If the terminal fails the CBRA procedure, the terminal may not perform preamble repetition transmission. For example, the terminal may perform the CBRA procedure repeatedly based on a counter. If the counter expires, the terminal may not be able to perform the CBRA procedure on an additional RO set. According to the proposed method, the terminal may perform the CBRA procedure using a legacy RO set. In other words, in the RO determination procedure, the terminal may determine a legacy RO set and perform the CBRA procedure based on the legacy RO set. The base station may indicate one or more repetition transmission counts to the terminal through signaling, and the terminal may derive an RO group using one of the one or more repetition transmission counts. The repetition transmission count may refer to a repetition factor or a transmission count.

[0484] The terminal may perform the CBRA procedure based on the first repetition transmission count. If the CBRA procedure continues to fail, the counter may expire. In this case, the terminal may perform the CBRA procedure again based on the second repetition transmission count. The second repetition transmission count may be greater than the first repetition transmission count.

[0485] A terminal located at a cell edge can select an additional set of ROs (e.g., a set of ROs mapped from SD resources). According to the proposed method, if an RA procedure (e.g., a CBRA procedure or a CFRA procedure) continuously fails and the counter expires, the terminal can re-perform the RA procedure.

[0486] The terminal may perform an RA procedure in an additional RO set based on the first repetition transmission count. If the RA procedure continuously fails and the counter expires, the terminal may select a second repetition transmission count. The terminal may additionally perform an RA procedure based on the second repetition transmission count. The RA procedure based on the second repetition transmission count may be performed in the additional RO set. Same as or similar to the above-described embodiment, the terminal may perform an RA procedure in a legacy RO set based on the first repetition transmission count. If the RA procedure continuously fails and the counter expires, the terminal may select a second repetition transmission count. The terminal may additionally perform an RA procedure based on the second repetition transmission count. The RA procedure based on the second repetition transmission count may be performed in the legacy RO set. The RO set may not be changed while the terminal performs the RA procedure.

[0487] For another example, the terminal can perform the RA procedure on the additional RO set based on the number of repetition transmissions. If the RA procedure on the additional RO set continuously fails and the counter expires, the terminal can perform the RA procedure on the legacy RO set instead of the additional RO set. The boundary values ​​of RSRP (e.g., SS-RSRP) can be different for the legacy RO set and the additional RO set. In this case, the number of repetition transmissions determined based on the same SS-RSRP (or the same SS-RSRQ) can have different values ​​for the legacy RO set and the additional RO set, respectively. For example, the terminal can derive the first number of repetition transmissions for the additional RO set based on SS-RSRP (or SS-RSRQ), and the terminal can derive the second number of repetition transmissions for the legacy RO set based on SS-RSRP (or SS-RSRQ). If the boundary values ​​of RSRP (e.g., SS-RSRP) are the same in the legacy RO set and the additional RO set, the number of repetition transmissions derived based on SS-RSRP (or SS-RSRQ) may be the same in the additional RO set and the legacy RO set. In other words, the number of first repetition transmissions may be the same as the number of second repetition transmissions.

[0488] The terminal can perform an RA procedure in the additional RO set, and if the counter expires, it can perform an RA procedure in the legacy RO set. If the counter expires, the terminal can perform the RA procedure in the additional RO set based on the increased number of repeated transmissions. The above-described operation can be performed repeatedly. Same as or similar to the above-described embodiment, if the RA procedure in the legacy RO set continuously fails and the counter expires, the terminal can perform the RA procedure in the additional RO set. Before considering a method of increasing the number of repeated transmissions, a method of changing the RO set can be considered first. If the boundary value(s) of RSRP applied to the legacy RO set are different from the boundary value(s) of RSRP applied to the additional RO set, the number of repeated transmissions derived based on the same SS-RSRP (or the same SS-RSRQ) can be different in each of the legacy RO set and the additional RO set. If the RA procedure continues to fail based on the first repetition transmission count in the legacy RO set and the counter expires, the terminal may perform the RA procedure based on the second repetition transmission count in the additional RO set. If the RA procedure continues to fail, the terminal may derive a repetition transmission count greater than the first repetition transmission count using the legacy RO set, and perform the RA procedure again based on the derived repetition transmission count. The above-described operations may be performed repeatedly.

[0489] Receive SBFD-msg2 / SBFD-msgB

[0490] Methods for a camping terminal to receive msg2 and / or msgB at a base station performing SBFD operation will be described.

[0491] A terminal may perform a 4-step RA procedure or a 2-step RA procedure to establish an RRC connection with a base station. The base station, upon receiving msg1 or msgA, may transmit msg2 or msgB to the terminal in response to msg1 or msgA. msg2 and msgB may be collectively referred to as RAR. The RAR may be broadcast by the base station. In the RA procedure, the terminal may expect to receive an RAR from the base station. The RAR reception operation may be performed by the terminal monitoring a search space (e.g., ra-SearchSpace) and CORESET. The search space indicated by ra-SearchSpace may be referred to as an RA search space. According to the technical specification, the RA search space may only be configured in a DL symbol. In other words, a DCI scheduling an RAR may be received in an RA search space configured in a DL symbol. When SBFD operation is supported, the RA search space can be established not only in the DL symbol but also in the SD symbol. In other words, the DCI scheduling the RAR can be received in the RA search space established in the SD symbol and / or the DL symbol. Another common search space (e.g., another set of common search spaces) can be established not only in the DL symbol but also in the SD symbol. Among the common search sets, the Type 0-PDCCH CSS (common search space) set can be established only in the DL symbol.

[0492] The Type 0A-PDCCH CSS set can be used to search for DCIs scheduling SIB(s) other than SIB1. The Type 0A-PDCCH CSS set can be mapped to SD symbols.

[0493] The Type 1-PDCCH-CSS set can be used to search for DCIs scheduling RARs (e.g., msg2 and / or msgB). A terminal performing SDT (small data transmission) operation can search for DCIs scheduling PDSCHs in the Type 1A-PDCCH-CSS set. The Type 1-PDCCH-CSS set and / or the Type 1A-PDCCH-CSS set can be mapped to SD symbols.

[0494] The Type 2-PDCCH CSS set can be used to search for DCIs that schedule paging information. The Type 2A-PDCCH CSS set can be used to search for DCIs that schedule paging early indicators used to predict paging information. The Type 2-PDCCH CSS set and / or the Type 2A-PDCCH CSS set can be mapped to SD symbols.

[0495] The terminal may search for some CSS sets in the SD symbol. In the RA procedure, the terminal may search for DCI for scheduling msg2 and / or msgB in the Type 1-PDCCH CSS set and / or the Type 1A-PDCCH CSS set after a predefined time has elapsed from the transmission time of msg1 and / or msgA. In other words, the terminal may perform a monitoring operation for the Type 1-PDCCH CSS set and / or the Type 1A-PDCCH CSS set. The monitoring operation of the terminal may start from the first DL symbol within the earliest slot of the Type 1-PDCCH CSS set and / or the Type 1A-PDCCH CSS set. The above-described monitoring operation may be performed during slots configured for the terminal. The CSS set may be indicated (e.g., configured) to the terminal in the SD symbol. In other words, the "Type 1-PDCCH CSS set and / or the Type 1A-PDCCH CSS set" and the CORESET associated with the CSS set may be configured in the SD symbol. In this case, the terminal can perform monitoring operation starting from the first DL symbol or the first SD symbol within the earliest slot of the Type 1-PDCCH CSS set and / or the Type 1A-PDCCH CSS set. Accordingly, the terminal can receive msg2 and / or msgB more quickly.

[0496] According to the proposed method, a DL symbol or SD symbol may be present after a predefined time from the transmission time of msg1 and / or msgA. The terminal may perform monitoring operations starting from the first DL symbol or the first SD symbol within the earliest slot of the Type 1-PDCCH CSS set and / or the Type 1A-PDCCH CSS set.

[0497] The CSS set indicated in the DL resource and the CSS set indicated in the SD resource may have different settings and / or different CORESETs. According to the proposed method, the monitoring operation in the DL resource and the monitoring operation in the SD resource may be indicated differently. In other words, SIB1 may indicate the monitoring operation in the DL resource and the monitoring operation in the SD resource differently. According to the conventional technical specification, the CSS set may be indicated (e.g., configured) only in the DL symbol. It may be desirable for a base station performing the SBFD operation to indicate (e.g., configure) the CSS set in the DL symbol and / or the SD symbol. The bandwidth of the DL symbol may be different from the bandwidth of the DL resource in the SD symbol. Therefore, it may be desirable for the CORESET for the DL symbol and the CORESET for the DL resource in the SD symbol to be configured differently. The CSS set configured in the DL symbol may be associated with a CORESET having a wide bandwidth. The CSS set configured in the SD symbol may be associated with a CORESET having a narrow bandwidth. Alternatively, a CSS set configured in an SD symbol may be associated with a CORESET containing non-contiguous RBs in the frequency domain. The CSS set may include a Type 1-PDCCH CSS set and / or a Type 1A-PDCCH CSS set.

[0498] The terminal can receive the PDSCH scheduled by the DCI received in the Type 1-PDCCH CSS set and / or the Type 1A-PDCCH CSS set in the DL symbol and / or the SD symbol. If the RO set is set in the UL symbol and the terminal transmits the PRACH in the RO set, the terminal can assume that the Type 1-PDCCH CSS set and / or the Type 1A-PDCCH CSS set is set in the DL symbol.

[0499] When the RO set is set in the SD symbol or "SD symbol and UL symbol" and the terminal transmits a PRACH in the RO set, the terminal can assume that the Type 1-PDCCH CSS set and / or the Type 1A-PDCCH CSS set is set in the DL symbol or SD symbol.

[0500] If the RO set is set in the SD symbol and the terminal transmits a PRACH in the RO set, the terminal can assume that the Type 1-PDCCH CSS set and / or the Type 1A-PDCCH CSS set is set in the SD symbol.

[0501] RAR Windows

[0502] In the RA procedure, msg1 and msg2 can be transmitted and received between the terminal and the base station. Transmission of msg3 can be scheduled by msg2. It may be desirable that the above-described operation (e.g., transmission and reception of a msg in the RA procedure) does not exceed a predefined time. An RAR window (e.g., ra-ResponseWindow) may start after a predefined time from the transmission time of msg1, and the RAR window may be stopped at the time of reception of msg2 (or the time of reception of DCI scheduling msg2). Information about the length of the RAR window may be included in the RACH configuration information. The terminal may receive the RACH configuration information from the base station and determine the length of the RAR window based on the information included in the RACH configuration information. If msg2 is not successfully received even after the expiration of the RAR window, the terminal may determine that the collision is not resolved. In this case, the terminal may consider retransmitting msg1.

[0503] The reception operation of msg2 can be performed on SD resources or ND resources. All resources for reception of msg2 can belong to SD resources or ND resources. If the PRACH configuration index indicating the set of ROs mapped on the SD resources is different from the PRACH configuration index indicating the set of ROs mapped on the ND resources, the RAR window related to the resource (e.g., resource type) scheduled for reception of msg2 can be applied. If one PRACH configuration index indicates the set of ROs mapped on both the SD resources and the ND resources, a common RAR window can be applied. Alternatively, the RAR window can be independently indicated for each resource (e.g., resource type), and the RAR window related to the resource (e.g., resource type) scheduled for reception of msg2 can be applied.

[0504] The RAR window may start after the initial transmission of msg1. Alternatively, in a repeat transmission procedure of msg1, the RAR window may start after the transmission of msg1 by the last RO in the RO group. The final transmission and retransmission of msg1 may be performed on the same resource type (e.g., SD resource or ND resource) or on different resource types. The retransmission of msg1 may be performed on SD resource or ND resource.

[0505] If the transmission of msg1 is set to be performed in the same resource type, the terminal can set a RAR window based on the technical specifications and operate within the RAR window. If the RAR window is implemented in a decreasing form, the RAR window with the maximum value can decrease after the initial transmission of msg1. If the RAR window is implemented in an increasing form, a timer (e.g., a timer associated with the RAR window) can increase from 0.

[0506] If the transmission of msg1 is set to be performed in different resource types, the terminal may regard the initial value of the RAR window as "the value of the RAR window associated with the resource type in which the initial transmission of msg1 is performed" or "the value of the RAR window associated with the PRACH configuration index." The above-described embodiment may mean that, when the RAR window is implemented in a decreasing form, the maximum value of the RAR window is derived based on the resource type (e.g., SD resource or ND resource). Even if the resource type in which msg1 is transmitted is changed, the RAR window may not be reset, and the value of the RAR window may be maintained. The value of the RAR window may decrease over time.

[0507] Send SBFD-msg3 / SBFD-msgA

[0508] The method(s) for transmitting msg3 and / or msgA by a camping terminal at a base station performing SBFD operation will be described. The msg3 transmission method described below can be applied identically or similarly to msgA transmission.

[0509] A terminal can transmit msg3 (e.g., msg3 PUSCH) to a base station in a resource indicated by a RAR UL grant (or DCI format 1_0). According to the technical specification, msg3 can be transmitted in a UL symbol and / or a FL symbol. A base station performing SBFD operation can schedule msg3 transmission using SD resources. The RAR UL grant (or DCI format 1_0) can indicate time resources and / or frequency resources for msg3 transmission. Frequency hopping information of msg3 can be indicated to the terminal through signaling from the base station together with information on the number of transmissions of msg3. The frequency hopping information of msg3 can include information indicating whether frequency hopping is applied to msg3 transmission.

[0510] The frequency resource through which msg3 is transmitted may include RB(s). The frequency resource (e.g., RB(s)) through which msg3 is transmitted may be located in an SD symbol, an UL symbol, and / or an FL symbol. Frequency hopping for msg3 transmission may be indicated to the terminal through signaling from the base station. In this case, all resources of one frequency hop for msg3 in the ND resource may be included in the UL BWP, and some resources of another frequency hop for msg3 in the SD resource may not be included in the UL BWP. Frequency hopping for msg3 may be indicated by an offset, and the offset may be a UL bandwidth ( ), considering the UL resource area of ​​the SD resource, some of the resources of other frequency hops for msg3 in the SD resource may not be included in the UL BWP. The offset for frequency hopping may be referred to as a hopping offset. For example, the hopping offset may be half of the UL BWP (e.g., ) or 1 / 4 ) may be directed to the terminal, and the first PRB of the second frequency hop may be determined based on the frequency resources of the first frequency hop and the hopping offset. In this case, some resources of the second frequency hop may fall outside the UL subband (e.g., UL region) of the SD symbol.

[0511] As a proposed method, the hopping offset is a function of the number of RBs that the UL region of the SD symbol has instead of the UL BWP. ) can be determined based on the function.

[0512] For example, hopping offset ( ) is half the bandwidth of the UL region of the SD symbol (e.g., ) or 1 / 4 ) can be interpreted as, and the first PRB of the second frequency hop is the frequency resource of the first frequency hop and the hopping offset ( ) can be determined based on.

[0513] The base station and / or terminal may use modulo arithmetic to calculate the first PRB of the second frequency hop to fall within the UL region of the SD symbol. For example, the base station and / or terminal may calculate the first PRB of the second frequency hop based on Equation 1 below.

[0514]

[0515] can point to the first PRB of the second frequency hop. can indicate the first PRB of the first frequency hop. can indicate a hopping offset. can indicate the bandwidth size of the UL region of the SD symbol. In other words, can indicate the number of PRBs belonging to the bandwidth of the UL region of the SD symbol.

[0516] The hopping offset can always be interpreted as the same value in the SD symbol domain. The terminal can transmit msg3 without frequency hopping. The terminal can ignore the field indicating the hopping offset.

[0517] To extend the transmission coverage of msg3, the base station can signal the number of repetitions of msg3 to the terminal. The number of repetitions of msg3 can be 2 or more. According to existing technical specifications, msg3 can only be transmitted in UL symbols. If SBFD operation is supported, the terminal can transmit msg3 to the base station not only in UL symbols but also in the UL region of SD symbols.

[0518] In the repeated transmission procedure for msg3, the terminal can transmit msg3 from a valid resource. The valid resource may be an UL resource. Both the time resource and frequency resource to which msg3 is mapped can be interpreted as a UL resource (e.g., a valid resource).

[0519] Frequency hopping can be instructed to the terminal, and the terminal can repeatedly transmit msg3. In the above-described situation, according to the conventional technical specification, msg3 can be transmitted using the same frequency resources. The first frequency hops in the repeated transmissions can be mapped to the same RBs, and the second frequency hops in the repeated transmissions can be mapped to the same RBs. When msg3 is transmitted in an SD symbol, the same frequency hops (e.g., the second frequency hops) in the repeated transmissions can be mapped to different RBs.

[0520] In the repeat transmission procedure of msg3, msg3 can be transmitted in an UL symbol or an SD symbol. If the initial transmission of msg3 is performed in an UL symbol, retransmission (e.g., repeat transmission) of msg3 can be performed in an UL symbol. If the initial transmission of msg3 is performed in an SD symbol, retransmission (e.g., repeat transmission) of msg3 can be performed in an SD symbol.

[0521] In the repeated transmission procedure of msg3, the terminal may determine that the resource scheduled for msg3 transmission is invalid. In this case, in order to transmit msg3 additionally, the terminal may determine the validity of the same time resource (e.g., time resource indicated by time domain resource assignment (TDRA)) and / or the same frequency resource (e.g., frequency resource indicated by frequency domain resource assignment (FDRA)) in an adjacent slot. The number of repeated transmissions of msg3 may be the same as the number of repeated transmissions indicated by the RAR UL grant (or DCI format 1_0).

[0522] In the repeated transmission procedure of msg3, depending on the connection status of the antenna of the base station, the reception processing of msg3 mapped across SD symbols and UL symbols may be difficult at the base station. In the embodiments of FIGS. 6 and 8, since the connection status of the antenna of the base station is maintained, separate processing for reception of msg3 at the base station may be unnecessary. In the embodiment of FIG. 7, since the connection status of the antenna of the base station changes, separate processing for reception of msg3 at the base station may be necessary. Since the terminal cannot know the status of the base station described above (e.g., the connection status of the antenna of the base station), it may be difficult to determine the validity of msg3 (e.g., msg3 transmission, resources for msg3 transmission).

[0523] According to the proposed method, the base station can indicate to the terminal the validity of msg3 mapped across SD symbols and UL symbols through signaling (e.g., higher layer signaling). If the terminal is indicated that msg3 mapped across SD symbols and UL symbols may be valid, the terminal can determine whether the frequency resource of msg3 is valid. If the frequency resource of msg3 is valid, the terminal can determine that msg3 is valid. Therefore, the terminal can transmit msg3 mapped across SD symbols and UL symbols to the base station. If the terminal is indicated that msg3 mapped across SD symbols and UL symbols is invalid, the terminal may not determine whether the frequency resource of msg3 is valid. Higher layer signaling can be used to derive the number of transmissions of msg3 (e.g., the number of repeated transmissions).

[0524] According to another proposed method, the base station can indicate the validity of msg3 (e.g., msg3 mapped across SD and UL symbols) to the terminal via physical layer signaling. The scheduling information for msg3 can be included in DCI format 1_0 or a RAR UL grant. The terminal can determine whether msg3 mapped across SD and UL symbols is valid based on a value derived from one or more fields included in the scheduling information.

[0525] If msg3 is transmitted more than once, msg3 may be mapped to an SD symbol or an "SD symbol and a non-SD symbol." A non-SD symbol may include an FL symbol or an UL symbol. Alternatively, a non-SD symbol may include an FL symbol and an UL symbol.

[0526] Figure 28 is a conceptual diagram illustrating a first embodiment in which one Msg3 instance is mapped across SD symbols and non-SD symbols.

[0527] Referring to FIG. 28, when msg3 is repeatedly transmitted, one msg3 instance (2010) can be mapped to an SD symbol and a non-SD symbol. In the repeated transmission of msg3, one msg3 instance can mean one msg3 transmission. According to the proposed method, the signaling of the base station (e.g., upper layer signaling) can indicate to the terminal that the msg3 instance (2010) can be valid, and the terminal can determine whether the msg3 instance (2010) is valid based on the validity of the frequency resource (e.g., UL subband) of the msg3 instance (2010).

[0528] Figure 29 is a conceptual diagram illustrating a second embodiment in which one Msg3 instance is mapped across SD symbols and non-SD symbols.

[0529] Referring to FIG. 29, msg3 (e.g., msg3 instance) can be mapped to SD symbols, FL symbols, and UL symbols. According to conventional technical specifications, a msg3 instance consisting only of UL symbols can be determined to be valid. According to the proposed method, if all frequency resources of the msg3 instance belong to the UL subband of the SD symbol, the terminal can determine the msg3 instance mapped to the FL symbol and the UL symbol to be valid. In other words, the validity of the msg3 instance can be determined based on the UL subband (e.g., frequency resources) of the SD symbol belonging to the msg3 instance.

[0530] FIG. 30 is a conceptual diagram illustrating a third embodiment in which one Msg3 instance is mapped across SD symbols and non-SD symbols.

[0531] Referring to FIG. 30, a msg3 instance can be mapped across SD symbols and FL symbols. The validity of a msg3 instance can be determined based on the UL subband (e.g., frequency resource) of the SD symbol belonging to the msg3 instance.

[0532] Figure 31 is a conceptual diagram illustrating a first embodiment in which one Msg3 instance is mapped to a non-SD symbol.

[0533] Referring to Fig. 31, the msg3 instance can be mapped to an FL symbol. If the SBFD operation is supported, the proposed method can be extended. While an SD symbol may be required to determine the validity of an msg3 instance, the msg3 instance may not be mapped to an SD symbol. The terminal can determine that an msg3 instance that is mapped only to an FL symbol is valid.

[0534] According to another proposed method, the base station can indicate the validity of msg3 (e.g., msg3 instance) to the terminal through physical layer signaling. The scheduling information of msg3 can be included in DCI format 1_0 or RAR UL grant. The terminal can determine whether msg3 transmission is performed in one symbol type or two symbol types based on a value derived from one or more fields in the scheduling information. In other words, a value derived from one or more fields in the scheduling information can indicate whether msg3 transmission is performed in one or two symbol types. The symbol type in which msg3 is transmitted can be maintained across all msg3 instances. Alternatively, the symbol type in which msg3 is transmitted can be changed across each msg3 instance.

[0535] Based on the scheduling information, the time resource and / or frequency resource through which the first msg3 instance is transmitted can be derived. The resource through which the first msg3 instance is transmitted can include an SD symbol or an ND symbol. The resource through which the first msg3 instance is transmitted can have a single resource type (e.g., an SD symbol or an ND symbol). The terminal can interpret the scheduling information so that the msg3 instance(s) following the first msg3 instance have the same resource type as the first msg3 instance. Alternatively, the terminal can interpret the scheduling information so that the resource type of the msg3 instance(s) following the first msg3 instance is determined regardless of the resource type of the first msg3 instance.

[0536] The SBFD configuration information may include information indicating that a resource type (e.g., a symbol type) for transmitting msg3 (e.g., a msg3 instance) is derived based on a combination of one or more fields included in the scheduling information. If one or more fields indicating a resource type (e.g., a symbol type) for transmitting msg3 (e.g., a msg3 instance) are not included in the scheduling information, the terminal may transmit the remaining msg3 instance(s) on a resource of the same symbol type as the first msg3 instance.

[0537] The power (e.g., transmit power) allocated to msg3 can be derived by applying an offset (e.g., msg3-DeltaPreamble or deltaPreamble) to the power of the SSB (e.g., EPRE or ss-PBCH-BlockPower). Depending on the implementation of the base station performing the SBFD operation, the power allocated to the SSB transmitted in the DL symbol may be the same as or different from the power allocated to the SSB transmitted in the SD symbol. If the power allocated to the SSB transmitted in the DL symbol is different from the power allocated to the SSB transmitted in the SD symbol, the power allocated to msg3 in each resource type may be different.

[0538] According to the proposed method, the power of msg3 transmitted in the SD symbol can be derived based on the power of the SSB received in the SD symbol, and the power of msg3 transmitted in the UL symbol can be derived based on the power of the SSB received in the DL symbol. The base station can allocate DL power and UL power in the SD symbol considering the CLI. The terminal can allocate power differently in the SD symbol and the UL symbol. In other words, the terminal can allocate power considering the CLI.

[0539] According to the proposed method, the power allocated to msg3 can vary based on the SSB (e.g., SSB index) and / or symbol selected by the terminal. If the reference SSB is transmitted in a DL symbol, the terminal can determine the power of msg3 using existing methods. If the reference SSB is transmitted in an SD symbol, the terminal can determine the power of msg3 using existing methods. In certain scenarios, the terminal can manage generalized SSBs by distinguishing symbols as well as SSB indexes. The above-described method for determining msg3 power can be applied to the above-described specific scenarios.

[0540] When the power allocated to an SSB transmitted in a DL symbol is the same as the power allocated to an SSB transmitted in an SD symbol, the base station may transmit SIB1 including two sets of parameters to the terminal. The two sets of parameters may include a set of parameters utilized to transmit msg3 in an SD resource (e.g., an SD symbol) and a set of parameters utilized to transmit msg3 in an UL resource (e.g., an UL symbol). The terminal may determine the power of msg3 based on the resource type for transmitting msg3.

[0541] The terminal can determine the power of msg3 based on the TPC command included in the RAR UL grant. If msg3 is repeatedly transmitted and an msg3 instance is also transmitted in an SD symbol or an FL symbol, the TPC command can be applied to a reference msg3 instance (e.g., the first msg3 instance), and the TPC command or another value derived based on the TPC command can be applied to other msg3 instance(s). For example, the offset can be indicated to the terminal through signaling from the base station. The terminal can determine the power (e.g., transmit power) of the msg3 instance by applying the offset to the TPC command. The offset for the TPC command can be appropriately applied depending on the configuration of the resources (e.g., SD symbol, FL symbol, and / or UL symbol) over which the msg3 instance is transmitted. The offset for the TPC command can mean two or more values. Alternatively, two or more offsets for the TPC command can be indicated to the terminal through signaling from the base station. One value derived based on the offset can be used to determine the power of an msg3 instance mapped to an SD symbol. Another value derived based on the offset can be used to determine the power of an msg3 instance mapped to a non-SD symbol (e.g., an ND symbol), an FL symbol, or an UL symbol.

[0542] For repeated transmission of msg3, different frequency resources may be configured for SD resources (e.g., SD-DL symbols and / or SD-FL symbols) and ND resources (e.g., UL symbols and / or FL symbols). An msg3 instance may be mapped to an UL symbol and / or an FL symbol, and the number of repeated transmissions of msg3 may be determined based on an MCS field included in an UL grant. The UL grant may be a RAR UL grant or a DCI format 0_0 scrambled by a temporary cell (TC)-RNTI. PUSCH repetition type A may be applied.

[0543] According to the proposed method, msg3 can be repeatedly transmitted on SD resources. According to another proposed method, transmission of msg3 instances can be allowed on both SD and ND resources. The frequency resources for transmission of msg3 instances on SD resources can be the same as or different from the frequency resources for transmission of msg3 instances on ND resources.

[0544] F1 and F2 can each indicate the starting frequency resource or starting frequency offset of the msg3 instance. If frequency hopping is not applied to msg3 or if frequency hopping is applied to msg3, F1 can indicate the starting frequency resource of the first frequency hop of msg3. If frequency hopping is applied to msg3, F2 can indicate the starting frequency resource or starting frequency offset of the second frequency hop of msg3. If msg3 is repeatedly transmitted, both F1 and F2 can be used.

[0545] According to the proposed method, F1 and F2 can be reinterpreted, and F1 and F2 can be utilized as different values ​​in the SD resource. F1 applied in the SD resource can be referred to as F1'. F2 applied in the SD resource can be referred to as F2'. F1' and F2' can each indicate the starting frequency resource or the starting frequency offset of the msg3 instance transmitted in the SD resource.

[0546] F1' and F2' can be set to always belong to the UL subband. For example, F1' can be determined using a modulo operation on F1, and F2' can be determined using a modulo operation on F2. For the modulo operation, the number of PRBs (N1) belonging to the UL subband and / or the number of PRBs scheduled for transmission of the msg3 instance (N3) can be utilized. F1' can be the result of F1 mod N1 or F1 mod (N1-N3). F2' can be the result of F2 mod N1 or F2 mod (N1-N3).

[0547] F1' can be determined using a scaling operation on F1, and F2' can be determined using a scaling operation on F2. For the scaling operation, the number of PRBs belonging to a UL subband (N1), the number of PRBs belonging to a UL BWP (N2), and / or the number of PRBs scheduled for transmission of an msg3 instance (N3) can be utilized. F1' can be a result of ceil(F1×N1 / N2), F1×ceil(N1 / N2), ceil(F1×{N1-N3} / {N2-N3}), or F1×ceil({N1-N3} / {N2-N3}). F2' can be the result of ceil(F2×N1 / N2), F2×ceil(N1 / N2), ceil(F2×{N1-N3} / {N2-N3}), or F2×ceil({N1-N3} / {N2-N3}). ceil() can be a rounding function.

[0548] According to the proposed method, the msg3 transmission scheduled by the RAR UL grant can be distinguished from the msg3 transmission scheduled by the DCI format 0_0. The msg3 transmission scheduled by the RAR UL grant can be performed on at least one of the SD resource and the ND resource. The msg3 transmission scheduled by the DCI format 0_0 can be performed on one of the SD resource and the ND resource. Alternatively, the msg3 transmission scheduled by the RAR UL grant can be performed on one of the SD resource and the ND resource. The msg3 transmission scheduled by the DCI format 0_0 can be performed on at least one of the SD resource and the ND resource.

[0549] Competition Resolve Timer

[0550] In the CBRA procedure, contention (e.g., collision) can be resolved by transmitting and receiving msg1, msg2, msg3, msg4, and HARQ-ACK, and the C-RNTI can be transmitted to the terminal. It may be desirable for the above procedure to be performed within a predefined time. A timer (e.g., ra-ContentionResolutionTimer) may start after the transmission time of msg3, and the timer may be stopped at the reception time of msg3. The RACH configuration information may include information about the maximum value, minimum value, and / or expiration condition of the timer. The terminal may receive the RACH configuration information from the base station and check the information included in the RACH configuration information. If the timer has expired but the terminal has not successfully received msg4, the terminal may determine that the contention has not been resolved and may discard the TC-RNTI.

[0551] It can be considered that msg3 transmission is performed on SD resources or ND resources. All transmission resources of msg3 scheduled by RAR UL grant can belong to SD resources or ND resources. If the PRACH configuration index indicating the RO set mapped on SD resources is different from the PRACH configuration index indicating the RO set mapped on ND resources, the timer associated with the resources scheduled for msg3 transmission can be used. If one PRACH configuration index indicates the RO set mapped on SD resources and ND resources, a common timer can be applied. Alternatively, timers can be indicated (e.g., configured) to the terminal for each resource type, and among the timers, the timer associated with the resources scheduled for msg3 transmission can be used.

[0552] The timer can start from the initial transmission of msg3. The initial transmission of msg3 and the retransmission of msg3 can be performed on resources of the same type (e.g., SD resources or ND resources). Alternatively, the retransmission of msg3 can be performed on SD resources or ND resources.

[0553] If the configuration applies to the initial transmission and retransmission of msg3 from the same type of resource, the timer's behavior may be based on conventional technical specifications. If the timer is implemented in a decrementing manner, the timer may decrease from its maximum value after the initial transmission of msg3. If the timer is implemented in an increasing manner, the timer may increase from 0 after the initial transmission of msg3.

[0554] When a configuration is applied in which initial transmission and retransmission of msg3 are performed on resources of different types, the terminal may regard the initial value of the timer as the value of the timer associated with the resource (or PRACH configuration index) in which the initial transmission of msg3 is performed. The above-described embodiment may mean that, when the timer is implemented in a decreasing form, the maximum value of the timer (e.g., ra-ContentionResolutionTimer) is determined based on the resource type (e.g., SD resource or ND resource). Even when the type of resource in which msg3 is transmitted is changed, the timer may not be reset, the value of the timer may be maintained, and the value of the timer may be decreased over time.

[0555] SBFD-CFRA Procedure

[0556] The method(s) for a terminal camping at a base station performing SBFD operation to perform CFRA procedures will be described.

[0557] When the CFRA procedure is triggered, the terminal can select the RO set associated with the SSB in the earliest SSB-RO mapping cycle after the trigger information is transmitted to the L1 layer of the terminal. If the PRACH mask (e.g., the PRACH mask index) is indicated to the terminal through signaling from the base station, the terminal can select the allowed RO based on the PRACH mask. If the PRACH mask is not indicated to the terminal, the terminal can select the first RO or the RO corresponding to a predefined number.

[0558] When the CFRA procedure is triggered for the purpose of requesting other system information (OSI), the terminal may perform the CFRA procedure. A base station (e.g., a camping base station) may assign separate preamble indices to unspecified terminals for each OSI set or SI combination. The base station may perform SI scheduling based on the preamble indices selected by the terminal. A camping base station may refer to a base station where the terminal is camping.

[0559] If the CFRA procedure is triggered for the purpose of a synchronized reconfiguration (e.g., reconfigurationWithSync), the terminal can perform the CFRA procedure. The preamble index can be independently indicated to each terminal via signaling from the base station. The base station (e.g., the serving base station) can identify the terminal performing the CFRA procedure based on the received preamble index.

[0560] When the CFRA procedure is triggered by the PDCCH order, the terminal can perform the CFRA procedure using a DCI format scrambled by the C-RNTI.

[0561] According to the existing technical specifications, the RO set can only be configured in UL or FL symbols. Only UL or FL symbols can be indicated by tdd-UL-DL-ConfigurationCommon. According to the proposed method, a base station performing SBFD operation can indicate various symbols (e.g., symbols of various types) to the terminal through signaling.

[0562] To derive an RO set and a valid RO, various proposed methods may be applied. The base station and / or the terminal may derive an RO set applicable to SD symbols and non-SD symbols (e.g., ND symbols) based on a single configuration information. Alternatively, the base station and / or the terminal may derive an RO set applicable to SD-DL symbols, SD-FL symbols, FL symbols, and / or UL symbols based on a single configuration information. The RO set may be divided into a first RO set and a second RO set. The first RO set may refer to an RO set mapped to an ND symbol, and the second RO set may refer to an RO set mapped to an SD symbol. Alternatively, the first RO set may refer to an RO set mapped to an SD symbol, and the second RO set may refer to an RO set mapped to an ND symbol. Alternatively, a single RO set may be used. A single RO set may be regarded as a union of different types of RO sets. Considering SSB-RO mapping, a single RO set may have a single indexing.

[0563] Two or more configuration information can be used, and the base station and / or the terminal can determine an RO set based on each configuration information. A first RO set can be derived based on one configuration information. The first RO set can be an RO set that reuses existing technical specifications. A second RO set can be derived based on other configuration information. The second RO set can be an RO set that considers SBFD operation. One or more second RO sets can be derived. The terminal can select one RO set to perform the CFRA procedure.

[0564] According to the proposed method, a base station can indicate (e.g., configure) a single RO set to a terminal through signaling (e.g., RRC signaling). The terminal can perform a CFRA procedure based on the RO set indicated by the signaling from the base station. If a single RO set is configured for the terminal, the above-described signaling can be omitted. If two or more RO sets are derived based on one or more pieces of configuration information, the RO set for performing the CFRA procedure can be indicated to the terminal through signaling from the base station (e.g., RRC signaling).

[0565] The first RO set can be used for CFRA procedures without separate signaling (e.g., RRC signaling). The first RO set can be an RO set to which legacy SSB-RO mapping is applied. To support the above-described embodiment, ROs can be mapped only to UL symbols.

[0566] The second RO set can be designated as an RO set for the CFRA procedure by the base station signaling to the terminal. The second RO set can be an RO set to which the legacy SSB-RO mapping or a separate SSB-RO mapping is applied. In this case, the second RO set (e.g., RO) can be mapped to SD-DL symbols and / or SD-FL symbols.

[0567] According to the proposed method, different RO sets can be used based on the purpose of the CFRA procedure. For example, the use of the first RO set for requesting OSI or SIB1 can be indicated to the terminal through signaling from the base station, and the use of at least one RO set from the first RO set or the second RO set for a synchronized reconfiguration (e.g., reconfigurationWithSync) can be indicated to the terminal through signaling from the base station.

[0568] In both CFRA and CBRA procedures, msg1 can be repeatedly transmitted. For one SSB, valid ROs having the same frequency resources can be temporally adjacent, and an RO group including the valid ROs can be established. An RO set can be established when msg1 is transmitted once. An RO group (e.g., a set of RO groups) can be established when msg1 is transmitted two or more times. The time interval between the first ROs in the RO groups can correspond to the number of repetitions, and the time interval can be referred to as a time offset.

[0569] To manage the number of RO groups for different repetition counts similarly, the base station can signal a time offset to the terminal. The time offset value can be an integer multiple of the repetition count. A separate time offset can be specified for each repetition count. According to the proposed method, a separate time offset can be specified for each RO group.

[0570] When the CFRA procedure is triggered by a PDCCH order, the UE may not know which RO set to select. The UE may receive a PDCCH order from a base station performing SBFD operation, receive a configuration indicating the RO set from the base station, and transmit msg1 to the base station using the resources indicated by the DCI format. The valid RO may be determined by considering SD resources or ND resources.

[0571] When two or more configurations indicate RO sets, the UE must be able to identify which RO set msg1 is transmitted to. This is because the UE performs a CFRA procedure triggered by a PDCCH order related to two or more TRPs (or two or more base stations), and each TRP performs different SBFD operations, or only one TRP performs the SBFD operation. In the above-described situation, the base station can signal to the UE different RO sets for each TRP, SD resource, or ND resource, and the UE can identify the different RO sets through the signaling from the base station.

[0572] According to the proposed method, a new field can be introduced into the DCI format. Alternatively, an existing field within the DCI format (e.g., an existing field with an increased size) can be reinterpreted for a different purpose. The new field or the existing field (e.g., an existing field with an increased size) can dynamically indicate the set of ROs in which the UE's preamble is transmitted. The UE can transmit msg1 to the base station, taking into account the SSB-RO mapping cycle in the set of ROs indicated by the base station.

[0573] According to another proposed method, the terminal can determine the type of resource to which the preamble of the terminal is transmitted (or the RO set to which the resource to which the preamble of the terminal is transmitted belongs) based on the type of the resource (e.g., symbol) to which the DCI format is received. If the resource (e.g., search space set) to which the DCI format is received is an SD symbol, the terminal can transmit the preamble (e.g., PRACH preamble) in the RO set mapped to the SD symbol. If the resource (e.g., search space set) to which the DCI format is received is an ND symbol, the terminal can transmit the preamble (e.g., PRACH preamble) in the RO set mapped to the ND symbol.

[0574] A terminal may receive a DCI format including a PDCCH order from a serving TRP, and the terminal may transmit a PRACH preamble to another TRP adjacent to the serving TRP. The other TRP may be a non-serving TRP. If the TRP receiving the PRACH preamble transmitted by the terminal is a serving TRP, the type of resource (e.g., symbol) on which the PDCCH order is received may be the same as the type of resource to which the RO set is mapped. If the TRP receiving the PRACH preamble transmitted by the terminal is an adjacent TRP and SBFD operation is supported, it may be desirable to dynamically indicate to the terminal the type of resource to which the RO set is mapped.

[0575] According to the proposed method, the operations of adjacent TRPs and serving TRPs can differ. The adjacent TRP can utilize a set of ROs mapped to ND symbols. The serving TRP can utilize a set of ROs mapped to SD symbols or ND symbols based on information in the PDCCH order.

[0576] mask

[0577] When the CFRA procedure is performed, the PRACH mask index may be indicated to the terminal through signaling from the base station. The PRACH mask index may be applied to a set of ROs mapped to SD resources and / or ND resources.

[0578] According to the proposed method, the base station can independently signal to the terminal the PRACH mask index for the RO set mapped to the ND resource and the PRACH mask index for the RO set mapped to the SD resource. The terminal can check the PRACH mask index for each resource type through the signaling from the base station.

[0579] The operations of the method according to the embodiments of the present disclosure can be implemented as a computer-readable program or code on a computer-readable recording medium. A computer-readable recording medium includes any type of recording device that stores information readable by a computer system. Furthermore, a computer-readable recording medium can be distributed across network-connected computer systems, allowing the computer-readable program or code to be stored and executed in a distributed manner.

[0580] Additionally, the computer-readable recording medium may include hardware devices specifically configured to store and execute program instructions, such as ROM, RAM, flash memory, etc. The program instructions may include not only machine language codes produced by a compiler, but also high-level language codes that can be executed by a computer using an interpreter, etc.

[0581] While some aspects of the present disclosure have been described in the context of a device, they may also represent a description of a corresponding method, wherein a block or device corresponds to a method step or a feature of a method step. Similarly, aspects described in the context of a method may also be described as a corresponding block or item or a feature of a corresponding device. Some or all of the method steps may be performed by (or using) a hardware device, such as, for example, a microprocessor, a programmable computer, or an electronic circuit. In some embodiments, at least one or more of the most significant method steps may be performed by such a device.

[0582] In embodiments, a programmable logic device (e.g., a field-programmable gate array) may be used to perform some or all of the functions of the methods described herein. In embodiments, the field-programmable gate array may operate in conjunction with a microprocessor to perform one of the methods described herein. In general, the methods are preferably performed by some hardware device.

[0583] Although the present disclosure has been described with reference to preferred embodiments thereof, it will be understood by those skilled in the art that various modifications and changes may be made to the present disclosure without departing from the spirit and scope of the present disclosure as set forth in the claims below.

Claims

1. As a terminal method, A step of receiving system information including SBFD (subband full duplex) configuration information, UL (uplink)-DL (downlink) configuration information, and RACH (random access channel) configuration information from a base station; A step of checking the SD (SBFD) resource indicated by the above SBFD setting information; A step of checking ND (non-SD) resources indicated by the above UL-DL configuration information; A step of determining a valid RO set from among an additional RO (RACH occasion) set set in the SD resource or a legacy RO set set in the ND resource based on the RACH setting information; and A step of transmitting a RA (random access) preamble from the valid RO set to the base station, Terminal method.

2. In claim 1, The SD resource is a resource capable of UL communication and DL communication, the ND resource includes at least one of a UL resource, a DL resource, or a FL (flexible) resource, the UL resource is a resource capable of the UL communication, the DL resource is a resource capable of the DL communication, the FL resource is a resource capable of the UL communication or the UL communication, and each of the additional RO set and the legacy RO set includes one or more ROs. Terminal method.

3. In claim 1, Further comprising a step of receiving a SSB (synchronization signal block) from the base station, Among the above additional RO set or the above legacy RO set, the RO set located after a preset time from the reception time of the SSB is determined as the valid RO set. Terminal method.

4. In claim 1, Further comprising the step of performing an SSB-RO mapping operation for the above valid RO set, The above SSB-RO mapping operation is not performed on an invalid RO set among the additional RO set or the legacy RO set. Terminal method.

5. In claim 1, The additional RO set set in the above SD resource is determined as the valid RO set, and the additional RO set is an RO set set in an SD-DL resource or an SD-FL resource among the SD resources, and the SD-DL resource is a DL resource having a UL subband, and the SD-FL resource is an FL resource having the UL subband or an FL resource not having the UL subband. Terminal method.

6. In claim 1, The step of determining the above valid RO set is: performing a validation procedure for the additional RO set including at least one SD resource; and A step of determining the legacy RO set set in the ND resource as the valid RO set without performing the validity determination procedure, Terminal method.

7. In claim 1, The legacy RO set set in the ND resource is considered invalid in the SD resource, and the additional RO set set in the SD resource is considered invalid in the ND resource. Terminal method.

8. In claim 1, The RACH configuration information includes one or more RACH general configurations associated with one or more PRACH (physical random access channel) configuration indices, and each of the one or more RACH general configurations includes at least one of time resource information or frequency resource information of the RO set. Terminal method.

9. In claim 8, If the above RACH configuration information includes one RACH general configuration associated with one PRACH configuration index, at least one of the additional RO set or the legacy RO set is configured based on the one RACH general configuration. Terminal method.

10. In claim 8, If the above RACH configuration information includes a first RACH general configuration and a second RACH general configuration, the legacy RO set is configured based on the first RACH general configuration associated with the first PRACH configuration index, and the additional RO set is configured based on the second RACH general configuration associated with the second PRACH configuration index. Terminal method.

11. In claim 8, The above system information further includes information indicating that one PRACH configuration index or two PRACH configuration indices are configured in the terminal. Terminal method.

12. As a terminal, Contains at least one processor, At least one processor of the terminal, Receive system information including SBFD (subband full duplex) configuration information, UL (uplink)-DL (downlink) configuration information, and RACH (random access channel) configuration information from a base station; Check the SD (SBFD) resources indicated by the above SBFD setting information; Check the ND (non-SD) resources indicated by the above UL-DL configuration information; Based on the above RACH configuration information, a valid RO set is determined from among an additional RO (RACH occasion) set set in the SD resource or a legacy RO set set in the ND resource; and Causing the base station to transmit a random access (RA) preamble from the above valid RO set, Terminal.

13. In claim 12, The SD resource is a resource capable of UL communication and DL communication, the ND resource includes at least one of a UL resource, a DL resource, or a FL (flexible) resource, the UL resource is a resource capable of the UL communication, the DL resource is a resource capable of the DL communication, the FL resource is a resource capable of the UL communication or the UL communication, and each of the additional RO set and the legacy RO set includes one or more ROs. Terminal.

14. In claim 12, At least one processor of the terminal, Further causing the reception of SSB (synchronization signal block) from the above base station, Among the above additional RO set or the above legacy RO set, the RO set located after a preset time from the reception time of the SSB is determined as the valid RO set. Terminal.

15. In claim 12, At least one processor of the terminal, Further causes the SSB-RO mapping operation to be performed on the above valid RO set, The above SSB-RO mapping operation is not performed on an invalid RO set among the additional RO set or the legacy RO set. Terminal.

16. In claim 12, The additional RO set set in the above SD resource is determined as the valid RO set, and the additional RO set is an RO set set in an SD-DL resource or an SD-FL resource among the SD resources, and the SD-DL resource is a DL resource having a UL subband, and the SD-FL resource is an FL resource having the UL subband or an FL resource not having the UL subband. Terminal.

17. In claim 12, When determining the above valid RO set, the at least one processor is configured to cause the terminal to: Performing a validation procedure for said additional RO set containing at least one SD resource; and Causing the legacy RO set set in the ND resource to be judged as the valid RO set without performing the above validity determination procedure, Terminal.

18. In claim 12, The RACH configuration information includes one or more RACH general configurations associated with one or more PRACH (physical random access channel) configuration indices, and each of the one or more RACH general configurations includes at least one of time resource information or frequency resource information of the RO set. Terminal.

19. In claim 18, If the above RACH configuration information includes one RACH general configuration associated with one PRACH configuration index, at least one of the additional RO set or the legacy RO set is configured based on the one RACH general configuration. Terminal.

20. In claim 18, If the above RACH configuration information includes a first RACH general configuration and a second RACH general configuration, the legacy RO set is configured based on the first RACH general configuration associated with the first PRACH configuration index, and the additional RO set is configured based on the second RACH general configuration associated with the second PRACH configuration index. Terminal.

Images