Power control method and device for random access process in sub-band full duplex communication system

Abstract

The present disclosure relates to a random access process. A terminal receives, from a base station, random access channel (RACH) configuration information including a first power offset and a second power offset, and performs a random access process including message 1 (Msg1) transmission and message 3 (Msg3) transmission to the base station. Each of the first power offset and the second power offset is related to a power offset between the Msg3 transmission and the Msg1 transmission, the transmission power of the Msg3 transmission performed using a resource type which is the same as that of the Msg1 transmission is determined on the basis of the first power offset, and the transmission power of the Msg3 transmission performed using a resource type different from that of the Msg1 transmission is determined on the basis of the second power offset.

Description

Power control method and apparatus for a random access process in a subband full-duplex communication system

[0001] The present disclosure relates to a wireless communication system, and more specifically to a method and apparatus for power control of a random access process in an SBFD system of a terminal that recognizes subband full duplex (SBFD).

[0002] Wireless access systems are being widely deployed to provide various types of communication services, such as voice and data. Generally, a wireless access system is a multiple access system capable of supporting communication with multiple users by sharing available system resources (bandwidth, transmission power, etc.). Examples of multiple access systems include CDMA (code division multiple access), FDMA (frequency division multiple access), TDMA (time division multiple access), OFDMA (orthogonal frequency division multiple access), and SC-FDMA (single carrier frequency division multiple access) systems.

[0003] As more communication devices require larger communication capacities, the need for enhanced mobile broadband communication compared to existing radio access technology (RAT) is emerging. Furthermore, Massive Machine Type Communications (MTC), which connects multiple devices and objects to provide various services anytime and anywhere, is also one of the major issues to be considered in next-generation communication. In addition, communication system designs that take into account services and terminals sensitive to reliability and latency are being discussed. Thus, the introduction of next-generation radio access technologies that consider enhanced mobile broadband communication, massive MTC, and Ultra-Reliable and Low Latency Communication (URLC) is being discussed, and for convenience, this technology is referred to as new RAT or NR in this disclosure.

[0004] In wireless communication systems NR or later, full duplex (FD) operation can be performed. When performing FD operation, the device can simultaneously perform downlink reception and uplink transmission within a specific time resource. This differs from half duplex (HD) operation, which can only perform either downlink reception or uplink transmission within a specific time resource.

[0005] For FD operation, some frequency resources within the same time resource may be allocated as a downlink subband for downlink communication and other frequency resources as an uplink subband for uplink communication, which can be referred to as subband full duplex (SBFD). Alternatively, for FD operation, frequency resources within the same time resource may be allocated that can be used for both downlink and uplink communication. This can be referred to as spectrum-sharing full duplex (SSFD).

[0006] Meanwhile, in an environment where the aforementioned SBFD is used in a wireless communication system, it is necessary to define how an SBFD-aware terminal (SBFD aware UE) performs a random access process, and more specifically, how to obtain the transmission power when performing a PUSCH (physical uplink shared channel) transmission of the random access process using SBFD resources.

[0007] In the prior art, the RACH opportunity (random access channel occasion: hereinafter abbreviated as RO) for transmitting the preamble (message 1) of the random access process was set only on the HD resource, and the scheduled PUSCH transmission (message 3 PUSCH) according to the random access response (message 2) was also set only on the HD resource.

[0008] However, in wireless communication systems after NR or NR, RO may not be set only in HD resources but may also be set in SBFD resources. In addition, the resources for transmitting the message 3 PUSCH may not be limited only to HD resources but may also be set in SBFD resources.

[0009] In conventional technology, power control for message 3 PUSCH transmission is based on the power (or power parameter) of message 1 transmission. However, if the transmission resource type for message 1 transmission and the transmission resource type for message 3 transmission are different from each other, applying this conventional technology as is may result in the message 3 transmission power being determined differently from what the terminal intended.

[0010] In addition, for configuring RO, there are RACH configuration options 1 (which may be simply abbreviated as Option 1) and RACH configuration options 2 (which may be abbreviated as Option 2). In Option 1, RO can be configured using legacy RACH configuration, and in Option 2, RO can be configured using legacy RACH configuration and additional RACH configuration (in other words, using two separate RACH configurations).

[0011] Depending on the RACH setting method and whether SBFD resources are used in Message 1 / Message 3, it is necessary to clearly define how power control parameters for Message 3 PUSCH transmission will be set / instructed.

[0012] The technical problem that the present disclosure aims to solve is to provide a method for power control during the random access process of a device in a subband full-duplex communication (SBFD) system and a device utilizing said method.

[0013] The present invention provides a method for power control in a random access process of a terminal recognizing subband full-duplex communication (SBFD) in a wireless communication system, and a device utilizing said method. According to said method, the terminal receives random access channel (RACH) configuration information including a first power offset and a second power offset from a base station, and performs a random access process including the transmission of Message 1 (Msg1) and Message 3 (Msg3) to said base station, wherein each of said first power offset and said second power offset is related to the power offset between the transmission of Msg3 and the transmission of Msg1, and the transmission power of Msg3 transmitted in the same resource type as Msg1 is determined based on said first power offset, and the transmission power of Msg3 transmitted in a different resource type from said Msg1 is determined based on said second power offset.

[0014] In another aspect, a terminal, device, or computer-readable medium is provided to execute the above method.

[0015] In another aspect, a method of operation of a base station and a base station utilizing said method are provided. According to the method of operation of said base station, the base station transmits random access channel (RACH) configuration information including a first power offset and a second power offset to a terminal, and performs a random access process including receiving a message 1 (Msg1) transmission and a message 3 (Msg3) transmission from said terminal. At this time, the first power offset and the second power offset are each related to the power offset between the transmission of Msg3 and the transmission of Msg1, and the transmission power of Msg3 transmission performed in the same resource type as the transmission of Msg1 is determined based on the first power offset, and the transmission power of Msg3 transmission performed in a different resource type from the transmission of Msg1 is determined based on the second power offset.

[0016] According to the present disclosure, when Message 1 and Message 3 are transmitted through different resource types (e.g., Message 1 is transmitted through a UL resource, which is a non-SBFD resource, and Message 3 is transmitted through an SBFD resource), Message 3 can be transmitted with sufficient power to compensate for the increased level of interference in the SBFD resource by applying a separately defined second power offset. This can improve the random access success rate and reliability.

[0017] In addition, if the transmission resources of message 1 and message 3 are of the same resource type (for example, when message 1 and message 3 are both transmitted through a UL resource that is a non-SBFD resource), unnecessary power boosting can be prevented by using the first power offset.

[0018] In addition, by preventing the problem of excessive transmission power (over-powering) that may occur when applying a uniform offset without considering the characteristics (interference level) of each resource type, unnecessary interference to adjacent cells or other SBFD terminals can be minimized.

[0019] In addition, a failure to transmit Message 3 implies a random access re-transmission, which causes an initial connection delay. However, according to the method of the present disclosure, even if the resource type for transmitting Message 3 changes compared to the transmission of Message 1, the success rate of the random access can be increased by applying appropriate power, and as a result, the latency required for the terminal to connect to the network can be reduced.

[0020] Furthermore, in situations where different resource types are mixed, the method for setting / instructing parameters related to transmission power control during the random access process is clarified to prevent ambiguity between the network and the terminal.

[0021] The effects obtainable from the embodiments of the present disclosure are not limited to those mentioned above, and other unmentioned effects can be clearly derived and understood by a person skilled in the art to which the technical configuration of the present disclosure applies from the description of the embodiments of the present disclosure below. That is, unintended effects resulting from implementing the configuration described in the present disclosure can also be derived by a person skilled in the art from the embodiments of the present disclosure.

[0022] The drawings attached below are intended to aid in understanding the present disclosure and may provide embodiments of the present disclosure together with the detailed description. However, the technical features of the present disclosure are not limited to specific drawings, and features disclosed in each drawing may be combined with one another to form new embodiments. Reference numerals in each drawing may denote structural elements.

[0023] FIG. 1 illustrates an example of signal transmission through physical channels according to an embodiment of the present disclosure.

[0024] FIG. 2 illustrates the structure of a wireless frame of NR according to one embodiment of the present disclosure.

[0025] FIG. 3 illustrates a slot structure of an NR frame according to one embodiment of the present disclosure.

[0026] FIG. 4 illustrates the structure of a self-contained slot according to an embodiment of the present disclosure.

[0027] FIG. 5 illustrates an example of a method for applying full duplex (FD) in an intra-carrier according to an embodiment of the present disclosure.

[0028] FIG. 6 illustrates examples of resource structures in which a time resource operating in HD (half duplex) and a time resource operating in FD (full duplex) coexist according to one embodiment of the present disclosure.

[0029] FIG. 7 illustrates an example of the position of a random access channel occasion (RO) on a time axis according to one embodiment of the present disclosure.

[0030] Figure 8 illustrates RO groups in the case where the number of repetitions is 4, the number of SSBs (synchronization signal blocks) is 2, the FDMed (frequency domain multiplexed) RO is 2, and the number of SSBs per RO is 1 / 2.

[0031] Figure 9 illustrates RO groups in the case where the number of repetitions is 4, the number of SSBs is 3, the FDMed RO is 4, and the number of SSBs per RO is 1.

[0032] FIG. 10 illustrates an example of a structure in which SBFD slots are allocated in the time and frequency axes according to one embodiment of the present disclosure.

[0033] FIG. 11 illustrates an example of a downlink slot to which an SBFD setting according to one embodiment of the present disclosure is applied.

[0034] FIG. 12 illustrates an example of a flexible slot to which an SBFD setting according to one embodiment of the present disclosure is applied.

[0035] FIG. 13 illustrates another example of a flexible slot to which an SBFD setting according to one embodiment of the present disclosure is applied.

[0036] FIG. 14 illustrates an example of a separated RO setting according to one embodiment of the present disclosure.

[0037] FIG. 15 illustrates an example of setting msg3-DeltaPreamble and deltaPreamble through RRC information elements (information element: IE) / parameters and the terminal operation accordingly.

[0038] Figure 16 shows an example of setting / instructing msg3-DeltaPreamble and deltaPreamble by RRC when an additional RACH configuration (additional RACH config IE) is added.

[0039] FIG. 17 shows an example in which SBFD is configured as a separate feature from half-duplex operation, and deltaPreamble is configured for the case where the terminal receives a single RACH configuration.

[0040] FIG. 18 shows another example in which the SBFD is configured as a separate feature from the half-duplex operation, and the terminal receives a single RACH configuration, and the deltaPreamble is configured.

[0041] FIG. 19 illustrates a method for setting / applying deltaPreamble when SBFD is set as a separate function from half-duplex operation and the terminal operates with a separate RACH setting (Option 2).

[0042] FIG. 20 illustrates another method of setting / applying deltaPreamble for a case where SBFD is set as a separate function from half-duplex operation and the terminal operates with a separate RACH setting (Option 2).

[0043] FIG. 21 illustrates a method for setting / applying deltaPreamble when SBFD is not set as a separate function from half-duplex operation and the terminal receives a single RACH setting (Option 1).

[0044] FIG. 22 illustrates a different method of setting deltaPreamble when SBFD is not set as a separate function from half-duplex operation and the terminal receives a single RACH setting.

[0045] FIG. 23 illustrates another method of setting / applying deltaPreamble when SBFD is not set as a separate function from half-duplex operation and the terminal receives a single RACH setting (Option 1).

[0046] FIG. 24 illustrates a method for setting / applying deltaPreamble when SBFD is not set as a separate function from half-duplex operation and the terminal receives individual RACH settings (Option 2).

[0047] FIG. 25 illustrates a different method of setting / applying deltaPreamble when SBFD is not set as a separate function from half-duplex operation and the terminal receives individual RACH settings (Option 2).

[0048] FIG. 26 illustrates a first method for defining independent parameters for each operation case of msg1 transmission and msg3 transmission.

[0049] FIG. 27 illustrates a second method of applying different msg3-deltaPreambles for cases where the types of each operation are the same or different in the msg1 transmission and msg3 transmission operations.

[0050] FIG. 28 illustrates a method of operation of a terminal according to one embodiment of the present disclosure.

[0051] FIG. 29 illustrates a signaling process and operation method between a base station and a terminal according to one embodiment of the present disclosure.

[0052] FIG. 30 illustrates a wireless device that can be applied to the present specification.

[0053] Figure 31 illustrates another example of a wireless device.

[0054] Figure 32 illustrates an example of a signal processing module structure.

[0055] Figure 33 illustrates another example of a signal processing module structure within a transmission device.

[0056] FIG. 34 illustrates an example of a wireless communication device according to an embodiment of the present disclosure.

[0057] FIG. 35 illustrates a communication system (1) applicable to the present specification.

[0058] The following embodiments are combinations of the components and features of the present disclosure in a predetermined form. Each component or feature may be considered optional unless otherwise explicitly stated. Each component or feature may be implemented in a form not combined with other components or features. Additionally, some components and / or features may be combined to form embodiments of the present disclosure. The order of operations described in the embodiments of the present disclosure may be changed. Some components or features of any embodiment may be included in other embodiments, or may be replaced with corresponding components or features of other embodiments.

[0059] In the description of the drawings, procedures or steps that could obscure the gist of the present disclosure have not been described, nor have procedures or steps that are understandable to those skilled in the art been described.

[0060] Throughout the specification, when a part is described as "comprising" or "including" a component, this means that, unless specifically stated otherwise, it does not exclude other components but may include additional components. Furthermore, terms such as "...part," "...unit," and "module" as used in the specification refer to a unit that performs at least one function or operation, and this may be implemented in hardware, software, or a combination of hardware and software. Additionally, "one (a or an)," "one," "the," and similar related terms may be used in the context describing the present disclosure (particularly in the context of the following claims) in both singular and plural forms, unless otherwise indicated in the specification or clearly contradicted by the context.

[0061] In this specification, the embodiments of the present disclosure are described with a focus on the data transmission and reception relationship between a base station and a mobile station. Here, the base station refers to a terminal node of a network that communicates directly with a mobile station. Specific operations described in this document as being performed by a base station may, in some cases, be performed by an upper node of the base station.

[0062] That is, in a network consisting of multiple network nodes including a base station, various operations performed for communication with a mobile station may be performed by the base station or other network nodes other than the base station. In this case, 'base station' may be replaced by terms such as fixed station, Node B, eNB (eNode B), gNB (gNode B), ng-eNB, advanced base station (ABS), or access point.

[0063] Additionally, in the embodiments of the present disclosure, the term terminal may be replaced with terms such as user equipment (UE), mobile station (MS), subscriber station (SS), mobile subscriber station (MSS), mobile terminal, or advanced mobile station (AMS). Hereinafter, for convenience, the terminal may be referred to as a UE.

[0064] Furthermore, the transmitting end refers to a fixed and / or mobile node that provides data or voice services, and the receiving end refers to a fixed and / or mobile node that receives data or voice services. Therefore, in the case of the uplink, a mobile station can be the transmitting end and a base station can be the receiving end. Similarly, in the case of the downlink, a mobile station can be the receiving end and a base station can be the transmitting end.

[0065] Embodiments of the present disclosure may be supported by standard documents disclosed in at least one of wireless access systems, such as IEEE 802.xx systems, 3GPP (3rd Generation Partnership Project) systems, 3GPP LTE (Long Term Evolution) systems, 3GPP 5G (5th generation) NR (New Radio) systems and 3GPP2 systems, for example, embodiments of the present disclosure may be supported by 3GPP TS (technical specification) 38.211, 3GPP TS 38.212, 3GPP TS 38.213, 3GPP TS 38.321 and 3GPP TS 38.331 documents.

[0066] In addition, the embodiments of the present disclosure may be applied to other wireless access systems and are not limited to the systems described above. For example, they may be applicable to systems applied after the 3GPP 5G NR system and are not limited to specific systems.

[0067] That is, obvious steps or parts not described in the embodiments of the present disclosure may be described by referring to the aforementioned documents. Additionally, all terms disclosed in this document may be explained by the aforementioned standard documents.

[0068] Hereinafter, preferred embodiments according to the present disclosure will be described in detail with reference to the accompanying drawings. The detailed description disclosed below, together with the accompanying drawings, is intended to describe exemplary embodiments of the present disclosure and is not intended to represent the only embodiment in which the technical configuration of the present disclosure can be implemented.

[0069] Additionally, specific terms used in the embodiments of the present disclosure are provided to aid in understanding the present disclosure, and the use of such specific terms may be modified in other forms without departing from the technical spirit of the present disclosure.

[0070] The following technology can be applied to various wireless access systems such as CDMA (code division multiple access), FDMA (frequency division multiple access), TDMA (time division multiple access), OFDMA (orthogonal frequency division multiple access), and SC-FDMA (single carrier frequency division multiple access).

[0071] For the sake of clarity, the following description is based on 3GPP communication systems (e.g., LTE, NR, etc.), but the technical scope of this disclosure is not limited thereto. LTE may refer to technology from 3GPP TS 36.xxx Release 8 onwards. Specifically, LTE technology from 3GPP TS 36.xxx Release 10 onwards is referred to as LTE-A, and LTE technology from 3GPP TS 36.xxx Release 13 onwards may be referred to as LTE-A pro. 3GPP NR may refer to technology from TS 38.xxx Release 15 onwards. 3GPP 6G may be an example of a next-generation wireless communication system. "xxx" indicates a specific standard document number. LTE / NR / 6G may be collectively referred to as 3GPP systems.

[0072] Regarding the background technology, terms, abbreviations, etc. used in this disclosure, reference may be made to standard documents published prior to this disclosure. For example, reference may be made to standard documents 36.xxx and 38.xxx.

[0073] In this disclosure, “A or B” may mean “only A,” “only B,” or “both A and B.” Alternatively, “A or B” may be interpreted as “A and / or B.” For example, “A, B or C” may mean “only A,” “only B,” “only C,” or “any combination of A, B and C.”

[0074] As used herein, a slash ( / ) or a comma may mean “and / or.” For example, “A / B” may mean “A and / or B.” Accordingly, “A / B” may mean “only A,” “only B,” or “both A and B.” For example, “A, B, C” may mean “A, B or C.”

[0075] In this specification, “at least one of A and B” may mean “only A,” “only B,” or “both A and B.” Additionally, in this specification, the expressions “at least one of A or B” or “at least one of A and / or B” may be interpreted as synonymous with “at least one of A and B.”

[0076] Additionally, in this specification, “at least one of A, B and C” may mean “only A,” “only B,” “only C,” or “any combination of A, B and C.” Additionally, “at least one of A, B or C” or “at least one of A, B and / or C” may mean “at least one of A, B and C.”

[0077] Additionally, parentheses used in this specification may mean “for example.” Specifically, when indicated as “Control Information (PDCCH),” “PDCCH” may be proposed as an example of “Control Information.” In other words, “Control Information” in this specification is not limited to “PDCCH,” and “PDCCH” may be proposed as an example of “Control Information.” Furthermore, even when indicated as “Control Information (i.e., PDCCH),” “PDCCH” may be proposed as an example of “Control Information.”

[0078] In this specification, transmitting a specific channel (e.g., a terminal transmitting PRACH) may mean transmitting related information / data / signals (e.g., a preamble) through said specific channel (e.g., PRACH). Likewise, receiving a specific channel (e.g., a base station receiving PRACH) may mean receiving related information / data / signals (e.g., a preamble) through said specific channel (e.g., PRACH).

[0079] Technical features described individually within a single drawing in this specification may be implemented individually or simultaneously.

[0080] The following drawings are prepared to illustrate a specific example of the present specification. The names of specific devices or specific signals / messages / fields described in the drawings are presented as examples, and therefore the technical features of the present specification are not limited to the specific names used in the following drawings.

[0081] The effects obtainable through the specific examples of this specification are not limited to those listed. For example, there may be various technical effects that a person having ordinary skill in the related art can understand or derive from this specification. Accordingly, the specific effects of this specification are not limited to those explicitly described herein, but may include various effects that can be understood or derived from the technical features of this specification.

[0082] FIG. 1 illustrates an example of signal transmission through physical channels according to an embodiment of the present disclosure.

[0083] Referring to FIG. 1, when a terminal is turned on again after being turned off or newly enters a cell, it performs an initial cell search operation, such as synchronizing with a base station (S11). Specifically, the terminal receives a Primary Synchronization Channel (P-SCH) and a Secondary Synchronization Channel (S-SCH) from the base station, synchronizes with the base station, and obtains information such as a cell ID. Afterward, the terminal can obtain cell broadcast information by receiving a Physical Broadcast Channel (PBCH) signal from the base station. Meanwhile, during the initial cell search phase, the terminal can check the downlink channel status by receiving a Downlink Reference Signal (DL RS).

[0084] After completing the initial cell search, the terminal performs a system information reception task (S12). For example, the terminal can obtain more specific system information by receiving the PDCCH (Physical Downlink Control Channel) and the PDSCH (Physical Downlink Control Channel) based on the PDCCH information.

[0085] Subsequently, the terminal may perform a random access procedure to complete the connection to the base station (S13~S16). For example, the terminal may transmit a preamble through a physical random access channel (PRACH) (S13) and receive a random access response (RAR) for the preamble through a PDCCH and a corresponding PDSCH (S14). The terminal may transmit a physical uplink shared channel (PUSCH) using scheduling information within the RAR (S15) and perform a contention resolution procedure, such as receiving a PDCCH signal and a corresponding PDSCH signal (S16).

[0086] Meanwhile, when the random access process is performed in two stages, the preamble transmission and PUSCH transmission of the terminal can be performed as a single operation, and the RAR transmission and PDSCH transmission of the base station can be performed as a single operation.

[0087] Afterwards, the terminal may receive PDCCH signals and / or PDSCH signals as a general up / down link signal transmission procedure (S17), or transmit PUSCH signals and / or PUCCH signals (S18).

[0088] The control information transmitted by a terminal to a base station is referred to as Uplink Control Information (UCI). UCI may include at least one of HARQ ACK / NACK (Hybrid Automatic Repeat and reQuest Acknowledgement / Negative-ACK), SR (Scheduling Request), and CSI (Channel State Information). CSI may include at least one of CQI (Channel Quality Indicator), PMI (Precoding Matrix Indicator), and RI (Rank Indication). UCI is generally transmitted periodically via PUCCH, but it may be transmitted via PUSCH if control information and data need to be transmitted simultaneously. Additionally, the terminal may transmit UCI aperiodically via PUSCH in response to network requests or instructions.

[0089] Wireless resource structure

[0090] FIG. 2 illustrates the structure of a wireless frame of NR according to one embodiment of the present disclosure. The embodiment of FIG. 2 may be combined with various embodiments of the present disclosure.

[0091] Referring to FIG. 2, radio frames can be used for uplink and downlink transmission in NR. The radio frame has a length of 10 ms and can be defined as two 5 ms half-frames (HF). A half-frame may contain five 1 ms subframes (SF). A subframe may be divided into one or more slots, and the number of slots within a subframe may be determined by the subcarrier spacing (SCS). Each slot may contain 12 or 14 OFDM(A) symbols according to the cyclic prefix (CP).

[0092] When normal CP is used, each slot may contain 14 symbols. When extended CP is used, each slot may contain 12 symbols. Here, the symbols may include OFDM symbols (or CP-OFDM symbols) and SC-FDMA (Single Carrier - FDMA) symbols (or DFT-s-OFDM (Discrete Fourier Transform-spread-OFDM) symbols).

[0093] When normal CP is used, the number of symbols per slot (N) according to the SCS setting (μ) slot symb ), number of slots per frame (N frame,μ slot ) and the number of slots per subframe (N subframe,μ slot ) can change.

[0094] The following Table 1 shows an example of SCS setting μ.

[0095] [Table 1]

[0096]

[0097] The following Table 2 shows the number of symbols in a slot (N) according to the SCS setting μ. slot symb ), number of slots in the frame (N frame,μ slot ), number of slots in the subframe (N subframe,μ slot ) exemplifies.

[0098] [Table 2]

[0099]

[0100] Table 3 below shows the number of symbols in a slot (N) according to the SCS setting μ when an extended CP is used. slot symb ), number of slots in the frame (N frame,μ slot ), number of slots in the subframe (N subframe,μ slot) exemplifies.

[0101] [Table 3]

[0102]

[0103] In an NR system, the OFDM(A) numerology (e.g., SCS, CP length, etc.) can be configured differently among multiple cells that are merged into a single terminal. Accordingly, the (absolute time) intervals of time resources (e.g., subframe, slot, or TTI) (collectively referred to as TU (Time Unit) for convenience) configured with the same number of symbols can be configured differently among the merged cells.

[0104] In NR, multiple numerologies or SCSs may be supported to support various 5G services. For example, if the SCS is 15 kHz, a wide area in traditional cellular bands may be supported, and if the SCS is 30 kHz / 60 kHz, dense-urban, lower latency, and wider carrier bandwidth may be supported. If the SCS is 60 kHz or higher, a bandwidth greater than 24.25 GHz may be supported to overcome phase noise.

[0105] The NR frequency band can be defined by two types of frequency ranges (FR1, FR2). The numerical values ​​of the frequency ranges may change; for example, the frequency ranges of the two types (FR1, FR2) may be as shown in Table 4 below. For convenience of explanation, among the frequency ranges used in the NR system, FR1 may mean "sub 6GHz range" and FR2 may mean "above 6GHz range" and may be referred to as millimeter wave (mmW).

[0106] [Table 4]

[0107]

[0108] As described above, the numerical values ​​of the frequency range of the NR system may change. For example, FR1 may include a band of 410 MHz to 7125 MHz as shown in Table 5 below. For example, FR1 may include a frequency band of 6 GHz (or 5850, 5900, 5925 MHz, etc.) or higher. For example, the frequency band of 6 GHz (or 5850, 5900, 5925 MHz, etc.) or higher included within FR1 may include an unlicensed band. The unlicensed band may be used for various purposes, for example, for communication for vehicles (e.g., autonomous driving).

[0109] [Table 5]

[0110]

[0111] FIG. 3 illustrates a slot structure of an NR frame according to one embodiment of the present disclosure. The embodiment of FIG. 3 can be combined with various embodiments of the present disclosure.

[0112] Referring to FIG. 3, a slot contains multiple symbols in the time domain. For example, in the case of a normal CP, one slot may contain 14 symbols, but in the case of an extended CP, one slot may contain 12 symbols. Alternatively, in the case of a normal CP, one slot may contain 7 symbols, but in the case of an extended CP, one slot may contain 6 symbols.

[0113] A carrier includes multiple subcarriers in the frequency domain. A resource block (RB) can be defined as multiple (e.g., 12) consecutive subcarriers in the frequency domain. A bandwidth part (BWP) can be defined as multiple consecutive (P)RBs ((Physical) Resource Blocks) in the frequency domain and can correspond to a single numerology (e.g., SCS, CP length, etc.). A carrier can include up to N (e.g., 4 or 5) BWPs. Data communication can be performed through an active BWP. Each element can be referred to as a resource element (RE) in a resource grid and can be mapped to a single complex symbol.

[0114] FIG. 4 illustrates the structure of a self-contained slot according to an embodiment of the present disclosure. In an NR system, the frame is characterized by a self-contained structure in which a DL control channel, DL or UL data, a UL control channel, etc., can all be included within a single slot. For example, the first N symbols within the slot may be used to transmit a DL control channel (hereinafter referred to as the DL control area), and the last M symbols within the slot may be used to transmit a UL control channel (hereinafter referred to as the UL control area). N and M are each integers greater than or equal to 0. A resource area (hereinafter referred to as the data area) located between the DL control area and the UL control area may be used for transmitting DL data or for transmitting UL data. For example, the following configuration may be considered. Each section is listed in chronological order.

[0115] 1. DL only setting

[0116] 2. UL only setting

[0117] 3. Mixed UL-DL Settings

[0118] - DL Area + GP (Guard Period) + UL Control Area

[0119] - DL Control Area + GP + UL Area

[0120] DL Area: (i) DL Data Area, (ii) DL Control Area + DL Data Area

[0121] UL Area: (i) UL Data Area, (ii) UL Data Area + UL Control Area

[0122] PDCCH can be transmitted in the DL control area, and PDSCH can be transmitted in the DL data area. PUCCH can be transmitted in the UL control area, and PUSCH can be transmitted in the UL data area. Downlink Control Information (DCI), such as DL data scheduling information and UL data scheduling information, can be transmitted in PDCCH. UCI, such as ACK / NACK (Positive Acknowledgement / Negative Acknowledgement) information for DL ​​data, Channel State Information (CSI) information, and Scheduling Request (SR), can be transmitted in PUCCH. The Guard Period (GP) provides a time gap during the process in which a Base Station (BS) and a terminal switch from transmit mode to receive mode or from receive mode to transmit mode. Within a subframe, some symbols at the point of transition from DL to UL can be set as GP.

[0123] DAPS-HO (Dual active protocol stack based handover)

[0124] From a UE functional perspective, DAPS can generally be characterized as follows:

[0125] Transmission operation:

[0126] Common SN;

[0127] Individual header compression for source and target cells;

[0128] Individual encryption for source and target cells.

[0129] Receiving operation:

[0130] Individual decoding for source cells and target cells;

[0131] Restoration of individual headers for source and target cells;

[0132] Common PDCP reordering;

[0133] Sequential delivery and duplicate detection;

[0134] Common buffer management.

[0135] Generally, the network side and the UE have the same processes and functions for transmission and reception operations. The only difference is whether these functions exist in the same location. On the network side, since all functions except for DL ​​PDCP SN allocation and UL PDCP reordering are performed separately at the source eNB and target eNB, two PDCP entities located at the source eNB and target eNB are assumed.

[0136] On the other hand, since all functions including SN allocation and PDCP reordering exist in the same location on the UE side, all functions for DAPS on the UE side can be modeled as a single PDCP entity. For a single UL data transmission, header compression and security processing for the source eNB or target eNB are used.

[0137] UE RF / Baseband Requirements

[0138] To minimize interruptions, the UE must continue data transmission and reception with the source cell when performing random access procedures to the target cell, regardless of whether it is SAPS or DAPS. This is possible only when the UE supports simultaneous transmission and reception with two cells. This works in most cases for UEs with Dual Rx / Dual Tx chains, and more restrictions may be required for UEs with Dual Rx / Single Tx RF chains or Single Rx / Single Tx RF chains.

[0139] Additionally, functional partitioning of the UE is necessary for the effective use of baseband and RF resources. In the case of SAPS, coordinating UE baseband and RF resources is not simple, leading to additional interruptions and UE complexity.

[0140] For UEs with a Dual Rx / Single Tx RF chain, simultaneous UL data transmission to two cells can be supported if certain requirements are met, such as when the bandwidth of the source cell is greater than that of the target cell. Otherwise, a UL TDM (time division multiplexing) pattern is required, which increases additional interrupt time and UL switching complexity. However, this UE option provides various UE implementation methods in terms of hardware and power efficiency for low-cost devices (including UEs that do not support UL CA and / or UL MIMO).

[0141] For a UE with a single Rx / single Tx RF chain, simultaneous transmission and reception can be supported if certain requirements are met. Otherwise, a TDM design is required for both the DL and UL, which increases complexity on both the UE and network sides. Additionally, RF chain switching is required for both the DL and UL, which increases HO interrupt time and switching complexity.

[0142] In general, solutions should be designed for all types of UE functions rather than being limited to specific ones. Therefore, solutions should be considered that support Dual Rx / Dual Tx as the standard, and Dual Rx / Single Tx and Single Rx / Single Tx as alternatives.

[0143] Explain DAPS-HO in the standard specification (e.g., TS 38.213).

[0144] If the UE represents the function for DAPS HO, the UE can be provided with a source MCG (Master Cell Group) and a target MCG.

[0145] If the UE is configured as an MCG and SCG (Secondary Cell Group) using NR radio access in FR1 and / or FR2, the maximum power P for transmission in the MCG by p-DAPS-FR1 and / or p-DAPS-FR2 MCG Maximum power P for transmission in and SCG SCG It is configured, and an inter-CG power sharing mode by UplinkPowerSharingDAPS-HO-mode for FR1 and / or FR2 is configured. The UE determines the transmission power of the MCG and SCG for each frequency band.

[0146] If the UE indicates UplinkPowerSharingDAPS-HO = Semi-static-mode1 and is provided with UplinkPowerSharingDAPS-HO-mode = Semi-static-mode1, the UE considers the target MCG as the MCG and the source MCG as the SCG to determine the transmission power for the target MCG or the source MCG.

[0147] If the UE indicates UplinkPowerSharingDAPS-HO = Semi-static-mode2 and is provided with UplinkPowerSharingDAPS-HO-mode = Semi-static-mode2, the UE considers the target MCG as the MCG and the source MCG as the SCG to determine the transmission power for the target MCG or the source SCG.

[0148] If the UE indicates UplinkPowerSharingDAPS-HO = Dynamic and is provided with UplinkPowerSharingDAPS-HO-mode = Dynamic, the UE considers the target MCG as the MCG and the source MCG as the SCG to determine the transmission power for the target MCG or the source MCG.

[0149] If the UE does not provide UplinkPowerSharingDAPS-HO and transmissions overlap between the target cell and the source cell, the UE performs transmission only in the target cell.

[0150] The cases in which the transmission of the target cell and the source cell is considered to overlap are as follows:

[0151] When the carrier frequencies of the target MCG and source MCG are in the same frequency (intra-frequency) and same band (intra-band) and are within an overlapping time resource.

[0152] When the carrier frequencies of the target MCG and the source MCG are not of the same frequency and band, and are within overlapping time resources and overlapping frequency resources.

[0153] In the case of same-frequency DAPS HO operation, the UE expects that the active DL BWP and active UL BWP of the target cell are contained within the active DL BWP and active UL BWP of the source cell, respectively.

[0154] The UE is N for the target MCG cells targetpdcch-BlindDetectionMCG1-UE can be provided to indicate the ability to monitor the maximum number of PDCCH candidates per slot corresponding to downlink cells, and for the source MCG N cells source pdcch-BlindDetectionMCG2-UE may be provided to indicate the ability to monitor the maximum number of PDCCH candidates per slot corresponding to a downlink cell. If the UE is provided with a search space set for both the target MCG and the source MCG, the UE expects that no USS set in any slot will have any assigned PDCCH candidates for both the target MCG and the source MCG.

[0155] Full duplex operation for NR

[0156] In 5G, new service types such as XR (Extended Reality), AI-based services, and self-driving cars are emerging. In these services, traffic fluctuates dynamically in both the DL and UL directions, and low latency may be required for transmitted packets. In 5G services, traffic load can increase explosively to support various new use cases.

[0157] On the other hand, existing semi-static or dynamic TDD UL / DL configurations have limitations related to transmit time delay and interference between operators. In addition, existing FDD methods have limitations in terms of efficient frequency resource utilization in the DL / UL direction. Therefore, in NR, the introduction of full-duplex operation within a single carrier can be discussed to achieve low latency and efficient resource utilization.

[0158] FIG. 5 illustrates an example of a method for applying full duplex in the intra-carrier according to an embodiment of the present disclosure.

[0159] Referring to Fig. 5, the structure in which DL and UL are allocated on the frequency axis of SBFD (subband-wise full duplex, also referred to as subband full duplex) and SSFD (spectrum-sharing full duplex) can be identified. In the case of SBFD as shown in Fig. 5(a), transmission and reception of DL and UL are performed through different frequency resources within a single carrier. That is, DL and UL have different frequency resources for the same time resource. In the case of SSFD as shown in Fig. 5(b), transmission and reception of DL and UL are performed through the same frequency resource or overlapping frequency resources within a single carrier. That is, DL and UL can have the same or overlapping frequency resources for the same time resource.

[0160] This full-duplex (FD) communication can be used in combination with existing half-duplex (HD) communication. In an existing half-duplex-based TDD communication environment, some time resources may be used for full-duplex communication. In some time resources where full-duplex communication is performed, SBFD or SSFD operations may be performed.

[0161] FIG. 6 illustrates examples of resource structures in which a time resource operating in HD (half duplex) and a time resource operating in FD (full duplex) coexist according to one embodiment of the present disclosure.

[0162] Referring to FIG. 6(a), some time resources are used for SBFD-based communication, and the remaining time resources are used for HD-based communication. Referring to FIG. 6(b), some time resources are used for SSFD-based communication, and the remaining time resources are used for HD-based communication. Here, time resources can be set to slots, symbols, subframes, or other similar time units.

[0163] In a time resource operating as an SBFD, some frequency resources are used as DL resources, and some frequency resources are used as UL resources. Hereinafter, for convenience of explanation, the present disclosure may refer to the frequency resources operating as DL among the total frequency resources in a time resource operating as an FD as DL subbands, and the frequency resources operating as UL may be referred to as UL subbands.

[0164] Base stations and terminals can perform full-duplex communication in various ways. For example, both the base station and the terminal can perform full-duplex operations. That is, both the base station and the terminal can simultaneously transmit and receive DL and UL using the same or different frequency resources within the same time resource. As another example, only the base station can perform full-duplex communication, while the terminal can perform half-duplex communication. In this case, the base station can simultaneously transmit and receive DL and UL using the same or different frequency resources within the same time resource, but the terminal performs only DL reception or UL transmission within a specific time resource. Here, the base station performs full-duplex communication by performing DL transmission and UL reception with different terminals at the same time.

[0165] Hereinafter, for the sake of convenience of explanation, it is assumed that the base station performs full-duplex communication and the terminal performs half-duplex communication, but is not limited thereto. For example, the methods described in this disclosure may be applied even when both the base station and the terminal perform full-duplex communication.

[0166] The following describes a random access procedure / process. The present disclosure proposes a method for setting up a bandwidth part (BWP) resource for intra-carrier full-duplex communication based on the random access procedure described below.

[0167] RACH (random access channel) procedure

[0168] The physical random access procedure can be triggered by a PRACH transmission request or PDCCH command (order) from the upper layer. The upper layer settings for the PRACH transmission may include the following:

[0169] Settings for PRACH transmission.

[0170] Preamble Index, Preamble SCS, P PRACH,target , the corresponding RA-RNTI, and PRACH resources.

[0171] PRACH consists of the PRACH format selected from the specified PRACH resource and the transmission power P PRACH,b,f,c It is transmitted using (i).

[0172] For a type-1 random access procedure, the UE is provided with N, the number of SS / PBCH block indices associated with one PRACH opportunity, and R, the number of competition-based preambles per SS / PBCH block index per valid PRACH opportunity, by ssb-perRACH-OccasionAndCB-PreamblesPerSSB.

[0173] In a Type-2 random access procedure (for a common set of PRACH opportunities), the UE is provided with N, the number of SS / PBCH block indices associated with one PRACH opportunity, by ssb-perRACH-OccasionAndCB-PreamblesPerSSB, and Q, the number of contention-based preambles per SS / PBCH block index per valid PRACH opportunity, by msgA-CB-PreamblesPerSSB-PerSharedRO. PRACH transfers may be performed within an SSB-RO mapping cycle on a subset of PRACH opportunities associated with the same SS / PBCH block index according to the PRACH mask index provided by msgA-SSB-SharedRO-MaskIndex.

[0174] Type-2 random access procedure (in the case of a separately configured PRACH opportunity), the UE is provided with the number of SS / PBCH block indices N associated with one PRACH opportunity and the number of contention-based preambles R per SS / PBCH block index per valid PRACH opportunity if provided by msgA-SSB-PerRACH-OccasionAndCB-PreamblesPerSSB, otherwise provided by ssb-perRACH-OccasionAndCB-PreamblesPerSSB.

[0175] For a Type-1 random access procedure or a Type-2 random access procedure using PRACH opportunities set separately from the Type-1 random access procedure, if N < 1, a single SS / PBCH block index is mapped to 1 / N consecutive valid PRACH opportunities, and the R-competition-based preamble associated with the SS / PBCH block index per valid PRACH opportunity starts at preamble index 0. If N ≥ 1, the R-competition-based preamble associated with the SS / PBCH block index n (0 ≤ n ≤ N-1) per valid PRACH opportunity is preamble index n·N preamble total Starting from / N, where N preamble totalis provided by totalNumberOfRA-Preambles for a type-1 random access procedure, or by msgA-TotalNumberOfRA-Preambles for a type-2 random access procedure, and is an integer multiple of N.

[0176] For a Type-2 random access procedure using commonally configured PRACH opportunities, if N < 1, a single SS / PBCH block index is mapped to 1 / N consecutive valid PRACH opportunities, and the Q-competition-based preamble associated with the SS / PBCH block index per valid PRACH opportunity starts at preamble index R. If N ≥ 1, the Q-competition-based preamble associated with the SS / PBCH block index n (0 ≤ n ≤ N-1) per valid PRACH opportunity is preamble index n·N preamble total Starting from / N+R, where N preamble total is provided by totalNumberOfRA-Preambles.

[0177] For link recovery, the UE is provided with N SS / PBCH block indices associated with one PRACH opportunity by the ssb-perRACH-Occasion of BeamFailureRecoveryConfig. For dedicated RACH configurations provided by RACH-ConfigDedicated, if cfra is provided, the UE is provided with N SS / PBCH block indices associated with one PRACH opportunity by the ssb-perRACH-Occasion of occasions. If N < 1, one SS / PBCH block index is mapped to 1 / N consecutive valid PRACH opportunities. If N ≥ 1, all N consecutive SS / PBCH block indices are associated with one PRACH opportunity.

[0178] SS / PBCH block indexes are provided by ssb-PositionsInBurst of SIB1 or ServingCellConfigCommon and can be mapped to valid PRACH opportunities in the following order depending on specific parameters:

[0179] First, in ascending order of the preamble index within a single PRACH opportunity.

[0180] Second, in ascending order of the frequency resource index of frequency multiplexing PRACH opportunities.

[0181] Third, in ascending order of time resource index within the PRACH slot.

[0182] Fourth, in ascending order of the PRACH slot index.

[0183] The association period for mapping SS / PBCH block indexes to PRACH opportunities starts from frame 0, and at least once N within the association period Tx SSB It is the smallest value in the set determined from the PRACH setup cycle so that SS / PBCH block indexes are mapped to PRACH opportunities. Here, UE is N Tx SSB Obtain from the ssb-PositionsInBurst value of SIB1 or ServingCellConfigCommon. N even after an integer cycle mapping SS / PBCH block indexes to PRACH opportunities within the association cycle. Tx SSBIf there are sets of PRACH opportunities or PRACH preambles that are not mapped to SS / PBCH block indices, the SS / PBCH block index is not mapped to those sets of PRACH opportunities or PRACH preambles. The association pattern period includes one or more association periods, and the pattern between a PRACH opportunity and an SS / PBCH block index is determined to repeat at a maximum of 160ms. PRACH opportunities that are not associated with an SS / PBCH block index after an integer number of association periods are not used for PRACH transmission.

[0184] In the case of a PRACH transfer triggered by a PDCCH command, the PRACH mask index field indicates the PRACH opportunity of the PRACH transfer in the PRACH opportunity associated with the SS / PBCH block index indicated by the SS / PBCH block index field of the PDCCH command, if the value of the random access preamble index field is not zero. The UE is K by CellSpecific_Koffset cell,offset If provided, the PRACH opportunity is UL BWP slot n+2 μ· K cell,offset It is set thereafter. Here, n is the slot of the UL BWP for PRACH transmission that overlaps with the end of the PDCCH command reception, μ is the SCS setting for PRACH transmission, and T TA Assume =0. If the PDCCH reception for a PDCCH command contains two PDCCH candidates from two associated sets of search spaces based on searchSpaceLinking, the last symbol of the PDCCH reception is the last symbol of the PDCCH candidate that ends later. The PDCCH reception contains two PDCCH candidates even if the UE does not need to monitor either of the two PDCCH candidates.

[0185] For a PRACH transfer triggered by a request from an upper layer, if ssb-ResourceList is provided, the PRACH mask index is represented by ra-ssb-OccasionMaskIndex, which indicates the PRACH opportunity of the PRACH transfer in the PRACH opportunity associated with the selected SS / PBCH block index.

[0186] PRACH opportunities are mapped consecutively for each corresponding SS / PBCH block index. The indexing of PRACH opportunities represented by the mask index value is initialized for each mapping cycle of consecutive PRACH opportunities per SS / PBCH block index. The UE selects a PRACH opportunity represented by the PRACH mask index value for the SS / PBCH block index designated for PRACH transmission in the first available mapping cycle.

[0187] For the specified preamble index, the order of PRACH opportunities is as follows:

[0188] First, in ascending order of the frequency resource index of frequency multiplexing PRACH opportunities.

[0189] Second, within the PRACH slot, in ascending order of the time resource index of the time multiplexing PRACH opportunity.

[0190] Third, in ascending order of the PRACH slot index.

[0191] For a PRACH transfer triggered by a request from an upper layer, if csirs-ResourceList is provided, the value of ra-OccasionList represents a list of PRACH opportunities for the PRACH transfer represented by the selected CSI-RS index (csi-RS). The indexing of PRACH opportunities represented by ra-OccasionList is initialized for each association pattern cycle.

[0192] Table 6 shows the mapping between the PRACH setup cycle and the PRACH opportunity association cycle in the SS / PBCH block.

[0193] [Table 6]

[0194]

[0195] For the paired spectrum or supplementary uplink band, all PRACH opportunities are valid.

[0196] For unpaired spectra:

[0197] If the UE is not provided with tdd-UL-DL-ConfigurationCommon, it does not precede the SS / PBCH block in the PRACH slot, and at least N after the last SS / PBCH block received symbol. gap If it starts after the symbol, the PRACH opportunity within the PRACH slot is valid. The above N gap It is provided in Table 7 below. Additionally, if channelAccessMode = "semiStatic" is provided, it must not overlap with the consecutive symbol set prior to the start of the next channel occupancy time, in which case the UE does not perform transmission.

[0198] The candidate SS / PBCH block index for the SS / PBCH block may correspond to the SS / PBCH block index provided by ssb-PositionsInBurst in SIB1 or ServingCellConfigCommon.

[0199] If the UE is provided with a TDD configuration (e.g., tdd-UL-DL-ConfigurationCommon), the PRACH opportunity within the PRACH slot is valid under the following conditions:

[0200] If it is within the UL symbol, or

[0201] Not preceding the SS / PBCH block within the PRACH slot, and at least N after the last downlink symbol gapIt starts after the symbol, and at least N after the last SS / PBCH block symbol. gap In the case where it starts after the symbol. The above N gap This is provided in Table 7 below. Additionally, if channelAccessMode = "semiStatic" is provided, it must not overlap with the consecutive symbol set prior to the start of the next channel occupancy time, in which case transmission must not be performed.

[0202] The candidate SS / PBCH block index for the SS / PBCH block may correspond to the SS / PBCH block index provided by ssb-PositionsInBurst in SIB1 or ServingCellConfigCommon.

[0203] For a specific preamble format (e.g., preamble format B4), N gap It can be 0.

[0204] Table 7 shows N for preamble SCS(μ). gap Represents the value.

[0205] [Table 7]

[0206]

[0207] If a random access procedure is initiated by a PDCCH command, and if requested by an upper layer, the UE transmits a PRACH at a selected PRACH opportunity, and the time between the last symbol of the PDCCH command reception and the first symbol of the PRACH transmission is N T,2 +Δ BWPSwitching +Δ Delay + T switch It must be at least msec.

[0208] N T,2 is the time corresponding to N2 symbols corresponding to the PUSCH preparation time for UE processing capability 1, and μ corresponds to the smaller of the SCS setting of the PDCCH command and the SCS setting of the corresponding PRACH transmission.

[0209] If the active UL BWP does not change, Δ BWPSwitching =0, and if not, Δ BWPSwitching It can be defined in standard specifications.

[0210] In the case of FR1, Δ Delay =0.5 msec, and in the case of FR2, Δ Delay =0.25 msec.

[0211] T switch is the switching gap duration.

[0212] For PRACH transmission using 1.25 kHz or 5 kHz SCS, the UE determines N2 by assuming the SCS setting μ=0.

[0213] In the case of single-cell operation or carrier aggregation operation in the same frequency band, the UE does not transmit PRACH and PUSCH / PUCCH / SRS within the same slot. Nor does it transmit if the interval between the first or last symbol of the PRACH transmission in the first slot and the last or first symbol of the PUSCH / PUCCH / SRS transmission in the second slot is less than N symbols, where N=2 is for μ=0 or μ=1, N=4 is for μ=2 or μ=3, N=16 is for μ=5, and N=32 is for μ=6, and μ is the SCS setting of the active UL BWP. If the PUSCH transmission uses repetition type B, this condition applies to each actual repetition of the PUSCH transmission.

[0214] Hereinafter, examples of PRACH setting tables used in the methods proposed through the present disclosure are described.

[0215] Table 8 shows examples of random access settings for FR1 and unpaired spectrum. PRACH setting indices can range from 0 to 262, and Table 8 provides examples of only some of these. For Table 8, refer to the full Table 6.3.3.2-3 of 3GPP TS 38.211 V19.

[0216] [Table 8]

[0217]

[0218] Table 9 shows examples of random access settings for FR2 and unpaired spectrum. PRACH setting indices can range from 0 to 255, and Table 9 provides examples of only some of these. For Table 9, refer to the full Table 6.3.3.2-4 of 3GPP TS 38.211 V19.

[0219] [Table 9]

[0220]

[0221] Table 10 shows examples of random access settings for FR1 and paired spectrum / supplementary uplink. PRACH setting indices can range from 0 to 255, and Table 10 shows only some of these. For Table 10, refer to the full Table 6.3.3.2-2 of 3GPP TS 38.211 V19.

[0222] [Table 10]

[0223]

[0224] Table 11 shows the supported Δf RA and corresponding combinations of Δf It represents.

[0225] [Table 11]

[0226]

[0227] FIG. 7 illustrates an example of the position of a random access channel occasion (RO) on a time axis according to one embodiment of the present disclosure.

[0228] Referring to FIG. 7, when the PRACH setting index is, for example, 28, the position of RO on the time axis can be represented as in FIG. 7. RO is allocated to each frame set with 40 slots, and 3 ROs can be set in each slot.

[0229] OFDM baseband signal generation for PRACH

[0230] Time continuous signal s of antenna port p for PRACH l (p,u) (t) can be defined as in Equation 1.

[0231] [Equation 1]

[0232]

[0233] Here, t start RA ≤t <t start RA +(N u + N CP,l RA )T c And, is provided by standard specifications.

[0234] Δf RA is the subcarrier spacing of the initial uplink bandwidth portion during initial connection. In the case of non-initial connection, Δf RA is the subcarrier spacing of the active uplink bandwidth portion.

[0235] μ0 is the largest μ value among the subcarrier spacing settings provided by the upper-level parameter scs-SpecificCarrierListscs.

[0236] N BWP,i startis the resource block with the lowest number in the initial uplink bandwidth portion during initial connection, and is determined by the upper layer parameter initialUplinkBWP. If it is not an initial connection, N BWP,i start is the resource block with the lowest number of the active uplink bandwidth portion, and is determined by the upper layer parameter BWP-Uplink.

[0237] n RA start is the frequency offset of the lowest PRACH transmission opportunity in the frequency domain for physical resource block 0 of the active uplink bandwidth portion. n RA star t is provided by the upper-level parameter msgA-RO-FrequencyStart and applies if a Type-2 random access procedure is started. Otherwise, it is provided by msg1-FrequencyStart.

[0238] n RA is a frequency domain PRACH transmission opportunity index for a specific PRACH transmission opportunity at a given time instance.

[0239] N RB RA is the number of occupied resource blocks, and can be provided by parameter allocation expressed as the number of resource blocks for PUSCH.

[0240] N RB,UL,n start,μ is RB n,UL start,μ This is the starting CRB index of the uplink RB set n corresponding to the amount. The UE assumes that the RB set is defined when IntraCellGuardBandsPerSCS is not provided for the UL carrier.

[0241] n0 is n RA startIt is the index of the set of RBs containing the lowest PRACH transmission opportunity in the frequency domain indicated by . UE is n RA start It can be assumed that each PRACH transmission opportunity is set to be fully contained within the RB set.

[0242] L RA and N u It can be provided by standard specifications.

[0243] N CP,l RA = N CP RA +n·16k, and Δf RA When ∈{1.25, 5}kHz, n=0 and Δf RA For ∈{15, 30, 60, 120, 480, 960}kHz, n is the interval [t start RA , t start RA + (N u RA +N CP RA )T c ) within this subframe, time instance 0 or time instance (Δf max N f / 2000)·T c = This is the number of times it overlaps with 0.5ms.

[0244] PRACH preamble starting position start RA is a subframe (Δf RA ∈{1.25, 5, 15, 30}kHz) or in the 60 kHz slot (Δf RA ∈{60,120,480,960}kHz), provided by Equation 2.

[0245] [Equation 2]

[0246]

[0247] Here, it is assumed that the subframe or 60 kHz slot starts at t=0.

[0248] Timing advance value NTA We must assume =0.

[0249] N u μ and N CP,l-1 μ It can be provided according to standard specifications.

[0250] Δf RA If ∈{1.25, 5}kHz, μ=0 must be assumed; otherwise, the value of μ is Δf RA ∈{15, 30, 60, 120, 480, 960} kHz, and symbol position l is l=l0+n t RA N dur RA +14n slot RA It is given as follows:

[0251] Here, l0 can be provided by the "starting symbol" parameter.

[0252] N t RA is a PRACH transmission opportunity within the PRACH slot, ranging from 0 to N within the PRACH slot. t RA,slot Numbers are assigned in ascending order up to -1. Here, N t RA,slot is L RA When ∈{139,571,1151}, it can be provided by a predetermined table, and L RA It is fixed at 1 when =839.

[0253] N dur RA is provided by a predetermined table.

[0254] n slot RA is given as follows:

[0255] Δf RA For the case where ∈{1.25,5,15,60}kHz, n slot RA .

[0256] Δf RAIf ∈{30,120}kHz and the "number of PRACH slots within a subframe" or "number of PRACH slots within a 60 kHz slot" of a predetermined table is 1, then n slot RA =1; otherwise n slot RA ∈{0,1}.

[0257] If Δf RA ∈{480,960} and:

[0258] When the "number of PRACH slots within the 60 kHz slot" in the predetermined table is 1, Δf RA n at 480kHz slot RA =7, Δf RA n at =960kHz slot RA =15.

[0259] If the "number of PRACH slots within the 60 kHz slot" in the predetermined table is 2, Δf RA n at =480kHz slot RA ∈{3,7}, Δf RA n at =960kHz slot RA ∈{7,15}.

[0260] If the preamble format provided in the predetermined table is A1 / B1, A2 / B2, or A3 / B3:

[0261] n t RA =N t RA,slot In the case of -1, the PRACH preamble is transmitted in the corresponding PRACH preamble format among B1, B2, and B3 during the PRACH transmission opportunity.

[0262] Otherwise, during the PRACH transmission opportunity, the PRACH preamble is transmitted in the corresponding PRACH preamble format among A1, A2, and A3.

[0263] Supported N RB RA , ΔfRA , parameter combinations of Δf and The values ​​corresponding to can be represented as shown in Table 12 below.

[0264] [Table 12]

[0265]

[0266] PRACH repetition

[0267] RO groups for PRACH repetition can be introduced to improve coverage. For example, if a base station sets and / or directs N (e.g., 2, 4, 8) repetition numbers, N ROs among the valid ROs existing at the same frequency can be grouped into an RO group in ascending order of time domain index. In the said RO group, N-1 ROs may be located at the same frequency as the first RO, as shown in FIGS. 8 and 9. That is, N ROs existing at the same frequency among the valid ROs associated with the same beam can be grouped into a single RO group.

[0268] Figure 8 illustrates RO groups in the case where the number of repetitions is 4, the number of SSBs (synchronization signal blocks) is 2, the FDMed (frequency domain multiplexed) RO is 2, and the number of SSBs per RO is 1 / 2.

[0269] Figure 9 illustrates RO groups in the case where the number of repetitions is 4, the number of SSBs is 3, the FDMed RO is 4, and the number of SSBs per RO is 1.

[0270] When PRACH transmission is performed with preamble repetitions, the time period starting from frame 0 is defined as an associative pattern period of at least an integer number, and N for all configured preamble repetition counts within that time period. Tx SSBFor each SS / PBCH block index, at least one set of valid PRACH opportunities must be determined. For each set number of preamble iterations, the set of valid PRACH opportunities is repeated at the corresponding time period, and the time period is defined as the minimum integer number of associated pattern periods. Here, the associated pattern period can be set to one or more associated periods, and for each SSB index, an associated pattern having at least one set of valid PRACH opportunities is repeated at a maximum of 160ms.

[0271] The association cycle for mapping SS / PBCH block indexes to PRACH opportunities starts from frame 0, and N Tx SSB It is the minimum integer value in the set determined by the PRACH setup cycle so that the SS / PBCH block index is mapped to a PRACH opportunity at least once within the corresponding association cycle. Here, UE is N Tx SSB Obtain from the ssb-PositionsInBurstssb-PositionsInBurstssb-PositionsInBurst value of SIB1 or ServingCellConfigCommon. The associative pattern cycle includes one or more associative cycles, and is determined so that the pattern between the PRACH opportunity and the SS / PBCH block index repeats at most every 160ms.

[0272] Below, the HD operations supported by NR are described.

[0273] <Slot Settings>

[0274] The slot format includes downlink symbols, uplink symbols, and flexible symbols.

[0275] The following items are applicable to each serving cell.

[0276] If the UE is provided with tdd-UL-DL-ConfigurationCommon, the UE sets the slot format for each slot according to the number of slots specified by tdd-UL-DL-ConfigurationCommon.

[0277] tdd-UL-DL-ConfigurationCommon provides the following:

[0278] i) Reference SCS setting μ by referenceSubcarrierSpacing ref .

[0279] ii) pattern1.

[0280] pattern1 can provide the following:

[0281] Slot setting period in Pmsec by dl-UL-TransmissionPeriodicity,

[0282] The number of slots containing only downlink symbols, d, determined by nrofDownlinkSlots slots ,

[0283] Number of downlink symbols by nrofDownlinkSymbols d sym ,

[0284] The number of slots containing only uplink symbols u by nrofUplinkSlots slots ,

[0285] Uplink symbols u by nrofUplinkSymbols sym .

[0286] The value of P=0.625 msec is μ ref = 3, μ ref = 5 or μ ref It is valid only when = 6. P=1.25 msec. The value is μ ref = 2, μ ref = 3, μ ref = 5 or μ ref It is valid only when = 6. P=2.5 msec. The value is μ ref = 1, μ ref= 2, μ ref = 3, μ ref = 5 or μ ref It is valid only when = 6. P=10 msec value is μ ref = 0, μ ref = 1, μ ref = 2, μ ref = 3 or μ ref Valid only when = 5.

[0287] SCS setting μ for slot setting period P msec ref The slot containing is included. The first d in the S slot slots The slot contains only downlink symbols, and the last slot u slots ...includes only uplink symbols. The first d slots Slot D sym The subsequent symbol is a downlink symbol. The last u slots u in front of the slot sym The symbol is an uplink symbol. The rest (Sd slots -u slots )-N symb slot -d sym -u sym is a flexible symbol.

[0288] In every 20 / P cycle, the first symbol is the first symbol of the even frame.

[0289] If tdd-UL-DL-ConfigurationCommon provides both pattern 1 and pattern 2, the UE sets the slot format per slot for the first number of slots indicated in pattern 1 and sets the slot format per slot for the second number of slots indicated in pattern 2.

[0290] Pattern 2 can provide the following.

[0291] Slot setting period of P2msec by dl-UL-TransmissionPeriodicity,

[0292] The number of slots containing only downlink symbols, d, determined by nrofDownlinkSlots slot,2,

[0293] Number of downlink symbols by nrofDownlinkSymbols d sym,2 ,

[0294] The number of slots containing only uplink symbols u by nrofUplinkSlots slots,2 ,

[0295] Uplink symbols u by nrofUplinkSymbols sym,2 .

[0296] The applicable value of P2 is the same as the applicable value of P.

[0297] The slot setting period P+P2mec is the first S=P·2 μref Slot and the second S2=P2·2 μref Includes slots.

[0298] Among the S2 slots, the first d slots,2 The slot contains only downlink symbols, and the last u slots,2 The slot contains only uplink symbols. The first d slots,2 d after the slot sym,2 The symbol is a downlink symbol. The last u slots,2 u prior to the slot sym,2 The symbol is an uplink symbol. The remainder (S2-d slots,2 -u slots,2 )-N symb slot - d sym,2 -u sym,2 is a flexible symbol.

[0299] UE expects P+P2 to be able to divide 20 ms.

[0300] For every 20 / (P+P2) period, the first symbol is the first symbol of the even frame.

[0301] UE references SCS setting μ refFor this configured DL BWP or UL BWP, it is expected to be less than or equal to the SCS setting μ. Each slot provided by pattern1 or pattern2 is a consecutive 2 of an active DL BWP or active UL BWP. (μ-μref) It can be applied to the slot. The reference SCS setting μ is for the slot. ref Starts at the same time as the first slot of, and reference SCS setting μ ref Each downlink, flexible, or uplink symbol for is 2 for SCS setting μ (μ-μref) It corresponds to a continuous downlink, flexible, or uplink symbol.

[0302] If the UE is additionally provided with tdd-UL-DL-ConfigurationDedicated, the tdd-UL-DL-ConfigurationDedicated parameter overwrites only the slot-specific flexible symbols according to the number of slots provided by tdd-UL-DL-ConfigurationCommon.

[0303] tdd-UL-DL-ConfigurationDedicated can provide the following.

[0304] The set of slot settings provided by slotSpecificConfigurationsToAddModList,

[0305] For each slot configuration in the slot configuration set, the slot index of the slot provided by slotIndex, and the set of symbols of the slot provided by symbols: if symbols = allDownlink, all symbols of the slot are downlinks; if symbols = allUplink, all symbols of the slot are uplinks; if symbols = explicit, nrofDownlinkSymbols provides the number of the first downlink symbols of the slot, and nrofUplinkSymbols provides the number of the last uplink symbols of the slot. If nrofDownlinkSymbols is not provided, the slot has no first downlink symbol, and if nrofUplinkSymbols is not provided, the slot has no last uplink symbol. The remaining symbols of the slot are flexible symbols.

[0306] For each slot having the corresponding index provided by slotIndex, the UE applies the format provided by the corresponding symbols. The UE does not expect tdd-UL-DL-ConfigurationDedicated to mark a symbol designated as a downlink by tdd-UL-DL-ConfigurationCommon as an uplink, or a symbol designated as an uplink as a downlink.

[0307] For each slot configuration provided by tdd-UL-DL-ConfigurationDedicated, the reference SCS configuration is the reference SCS configuration μ provided by tdd-UL-DL-ConfigurationCommon ref am.

[0308] The number of downlink symbols, uplink symbols, and flexible symbols in each slot of the slot configuration cycle and tdd-UL-DL-ConfigurationCommon and tdd-UL-DL-ConfigurationDedicated are determined from each configured BWP.

[0309] The UE considers the symbols in the slots marked as downlink by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated as receiving, and the symbols in the slots marked as uplink by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated as transmitting.

[0310] If the UE has not configured PDCCH monitoring for DCI format 2_0, it applies to the symbol set of the slot indicated by flexible symbols by tdd-UL-DL-ConfigurationCommon and tdd-UL-DL-ConfigurationDedicated (if provided), or if tdd-UL-DL-ConfigurationCommon and tdd-UL-DL-ConfigurationDedicated are not provided to the UE, it applies to the symbol set.

[0311] If the UE receives the corresponding instruction in DCI format, it receives PDSCH or CSI-RS from the symbol set of the slot.

[0312] If the UE receives the corresponding instruction from DCI format, RAR UL grant, fallbackRAR UL grant, or successRAR, it transmits PUSCH, PUCCH, PRACH, or SRS in the symbol set of the slot.

[0313] For operation in the unpaired spectrum on a single carrier, if the UE is configured by an upper layer to receive PDCCH, PDSCH, CSI-RS, or DL ​​PRS in the slot's symbol set, the UE receives PDCCH, PDSCH, CSI-RS, or DL ​​PRS in the slot's symbol set if the UE does not detect a DCI format in at least one symbol indicating an instruction to transmit PUSCH, PUCCH, PRACH, or SRS in the slot's symbol set. Otherwise, the UE does not receive PDCCH, PDSCH, CSI-RS, or DL ​​PRS in the slot's symbol set.

[0314] For shared spectrum channel access in FR1 or operation in FR2-2 where the UE is set to ChannelAccessMode2 = 'enabled', if the UE is provided with csi-RS-ValidationWithDCI and not provided with CO-DurationsPerCell and SlotFormatCombinationsPerCell, and the UE is configured by the upper layer to receive CSI-RS from the symbol set of the slot, if the UE does not detect a DCI format indicating non-periodic CSI-RS reception from the symbol set of the slot or scheduling PDSCH reception, the UE cancels CSI-RS reception from the symbol set of the slot.

[0315] If the UE is provided with channelAccessMode = 'dynamic' and availableRB-SetsToAddModList and availableRB-SetsToReleaseList are provided, the UE expects co-DurationsPerCellToAddModList and co-DurationsPerCellToReleaseList and / or slotFormatCombToAddModList and slotFormatCombToReleaseList to be provided.

[0316] For operation in the unpaired spectrum on a single carrier, if the UE is configured by the upper layer to transmit SRS, PUCCH, PUSCH, or PRACH from the symbol set of a slot, and the UE detects a DCI format to receive CSI-RS or PDSCH from a subset of that symbol set,

[0317] If the UE does not indicate the [partialCancellation] function, the UE receives T from the last symbol of the PDCCH reception. proc,2 It is expected that the transmission of PUCCH, PUSCH, or PRACH will not be cancelled in the symbols occurring within. Otherwise, the UE cancelled the transmission of PUCCH, PUSCH, the actual repetition of PUSCH, or PRACH.

[0318] If the UE indicates the [partialCancellation] function, the UE T from the last symbol of the PDCCH reception proc,2 It is expected that the transmission of PUCCH, PUSCH, or PRACH will not be cancelled in the symbols occurring within. The UE cancelled the transmission of PUCCH, PUSCH, the actual repetition of PUSCH, or PRACH in the remaining symbols.

[0319] The UE receives T from the last symbol of the PDCCH reception proc,2 It is expected that SRS transmission will not be canceled on symbols occurring within this period. The UE cancels SRS transmission on a subset of the remaining symbols.

[0320] T proc,2 is d 2,1It can be assumed to be =1, and it is the PUSCH preparation time for UE processing capability that matches μ, which corresponds to the smallest SCS setting between the SCS setting of PDCCH containing the DCI format and the SCS settings of SRS, PUCCH, and PUSCH. If the SCS setting of PRACH is 15kHz or higher, μ corresponds to the SCS setting of PRACH; otherwise, μ r =0.

[0321] If the symbol set of a slot is indicated as an uplink to the UE by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated, and the symbol set of that slot overlaps with or partially overlaps with PDCCH, PDSCH, or CSI-RS, the UE does not receive PDCCH, PDSCH, or CSI-RS.

[0322] If the symbol set of a slot is indicated as an uplink to the UE by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated, and the UE is not provided with a measurement gap, the UE does not receive DL PRS from the symbol set of that slot.

[0323] If the symbol set of a slot is indicated as a downlink to the UE by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated, and the symbol set of that slot overlaps with or partially overlaps with PUSCH, PUCCH, PRACH, or SRS, the UE does not transmit PUSCH, PUCCH, PRACH, or SRS.

[0324] If the symbol set of a slot is marked as flexible to the UE by tdd-UL-DL-ConfigurationCommon and, if provided, tdd-UL-DL-ConfigurationDedicated, the UE does not expect to receive both upper-layer-only parameters that set the UE's transmit and upper-layer-only parameters that set the UE's receive from the symbol set of that slot.

[0325] When operating as a single carrier in an unpaired spectrum, by ssb-PositionsInBurst of SIB1, ssb-PositionsInBurst of ServingCellConfigCommon, or ssb-PositionsInBurst of SSB-MTCAdditionalPCI associated with the active TCI state of PDCCH or PDSCH, for the symbol set of the slot indicated to the UE for receiving SS / PBCH blocks, or for the symbol set of the slot corresponding to the SS / PBCH block set for L1 beam measurement / reporting, if a transmission overlaps with a symbol of that symbol set, the UE does not transmit PUSCH, PUCCH, or PRACH in the slot, and does not transmit SRS in the symbol set of the slot. The UE does not expect the symbol set of the slot to be indicated to the UE as an uplink by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated.

[0326] If the UE is configured with multiple serving cells and directionalCollisionHandling-r16 = 'enabled' is provided for a specific serving cell among the multiple serving cells, it indicates half-DuplexTDD-CA-SameSCS-r16 feature support; and if none of the multiple serving cells are configured for PDCCH monitoring for DCI format 2_0 detection, the set of slot symbols of the first serving cell indicated to the UE for receiving SS / PBCH blocks, or the symbols of the slots corresponding to the SS / PBCH blocks configured for L1 beam measurement / reporting, by ssb-PositionsInBurst of SSB-MTCAdditionalPCI associated with the active TCI status of PDCCH or PDSCH, provided that the UE is not provided with dl-OrJointTCI-StateList. For a set, if a transmission overlaps with a symbol of that symbol set, the UE does not transmit PUSCH, PUCCH, or PRACH in the slot, and does not transmit SRS within the symbol set of the following slots.

[0327] i) where the UE is not capable of simultaneous transmission and reception via simultaneousRxTxInterBandCA between multiple serving cells, ii) one of the cells corresponding to the same band as the first cell, regardless of whether any of the multiple serving cells are capable of simultaneous transmission and reception via simultaneousRxTxInterBandCA.

[0328] The symbol set of the slot corresponding to the valid PRACH event and N prior to the valid PRACH event gapIn the case of a symbol, if the reception overlaps with a symbol of the symbol set, the UE does not receive PDCCH, PDSCH, or CSI-RS in the slot. The UE does not expect the symbol set of the slot to be indicated as a downlink by tdd-UL-DL-Configuration Common or tdd-UL-DL-ConfigurationDedicated.

[0329] For the symbol set of slots indicated to the UE by pdcch-ConfigSIB1 in the MIB for the CORESET for the Type0-PDCCH CSS set, the UE does not expect that symbol set to be indicated uplinked by tdd-UL-DL-Configuration Common or tdd-UL-DL-ConfigurationDedicated.

[0330] If a UE is scheduled in DCI format to receive PDSCH in multiple slots, and tdd-UL-DL-Configuration Common or tdd-UL-DL-ConfigurationDedicated indicates that at least one symbol in the set of symbols for which the UE is scheduled to receive PDSCH in one of the multiple slots is an uplink symbol, the UE does not receive PDSCH in the slot.

[0331] If a UE is scheduled in DCI format to transmit PUSCH through multiple slots, and tdd-UL-DL-Configuration Common or tdd-UL-DL-ConfigurationDedicated indicates that at least one of the symbols in the series for which the UE is scheduled for one of the multiple slots is a downlink symbol, the UE does not transmit PUSCH in that slot.

[0332] If UE

[0333] It is configured with multiple serving cells, and directional collision handling-r16 = 'enabled' is provided for one of the configured serving cells, and

[0334] Indicates that it supports half-duplex TDD-CA-SameSCS-r16 features, and

[0335] If PDCCH is not configured to monitor to detect DCI format 2_0 in multiple service cells,

[0336] The UE determines the reference cell of the symbol as the active cell with the smallest cell index among the following.

[0337] i) Multiple serving cells configured where the UE cannot transmit and receive simultaneously as indicated by simultaneous RxTxInterBandCA among the multiple serving cells, ii) Multiple serving cells configured such that the UE can transmit and receive simultaneously via RxTxInterBandCA, with each band cell configured accordingly.

[0338] Here, the symbol is set as follows.

[0339] Downlink or uplink. This may be indicated by tdd-UL-DL-Configuration Common or tdd-UL-DL-ConfigurationDedicated.

[0340] If the symbol is flexible and the UE is configured to transmit SRS, PUCCH, PUSCH, or PRACH from the symbol, it can be configured as an uplink.

[0341] If the symbol is flexible and the UE is configured to receive PDCCH, PDSCH, or CSI-RS from the symbol, it can be configured as a downlink.

[0342] If another cell among the cells configured as directionalCollisionHandling-r16 operates in the same frequency band as the reference cell, the UE does not expect the following.

[0343] i) A symbol that is displayed as a downlink or uplink in the reference cell and as an uplink or downlink in other cells, respectively, by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated,

[0344] ii) tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated, which detects a DCI format that marks a symbol as downlink in the reference cell and schedules the transmission of the symbol in other cells,

[0345] iii) Established by the upper layer to receive PDCCH, PDSCH, or CSI-RS on a flexible symbol in a reference cell and to detect a DCI format that schedules transmission in that symbol in another cell.

[0346] If the reference cell and another cell among the cells configured with directionalCollisionHandling-r16 operate in different frequency bands, the UE

[0347] i) When the symbol is represented as a downlink or uplink in other cells and as an uplink or downlink in the reference cell by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated, the symbol is assumed to be a flexible symbol, and there is no need to receive PDCCH, PDSCH, or CSI-RS set by the upper layer, and there is no need to transmit SRS, PUCCH, PUSCH, or PRACH set by the upper layer.

[0348] ii) If the corresponding symbol in the reference cell is marked as a downlink by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated, a signal / channel scheduled by DCI format is transmitted from the symbol in another cell.

[0349] iii) If the UE detects a DCI format that schedules transmission for one or more symbols in another cell, it does not need to receive the PDCCH, PDSCH, or CSI-RS set in the upper layer from the flexible symbols of the reference cell in that symbol set.

[0350] And regardless of whether the reference cell and other cells operate in the same frequency band or different frequency bands, the UE

[0351] 1) It is not expected that the tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated symbol for the reference cell will be identified as an uplink and that the DCI format will be detected to schedule reception at the corresponding symbol of another cell.

[0352] 2) It is not expected that the upper layer will detect a DCI format that is configured to transmit SRS, PUCCH, PUSCH, or PRACH on a flexible symbol in a reference cell and schedule reception on the corresponding symbol in another cell.

[0353] 3) If at least one symbol in the corresponding symbol set is indicated as a downlink by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated in the reference cell, or corresponds to PDCCH, PDSCH, or CSI-RS reception, PUCCH, PUSCH, or PRACH set by the upper layer for the symbol set of another cell is not transmitted.

[0354] 4) If the corresponding symbol set is indicated as a downlink by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated in the reference cell, or corresponds to PDCCH, PDSCH, or CSI-RS reception, the SRS set by the upper layer for the symbol set of another cell is not transmitted.

[0355] 5) If at least one symbol in the corresponding symbol set is indicated as an uplink by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated in the reference cell, or corresponds to an SRS, PUCCH, PUSCH, or PRACH transmission, it does not receive a PDCCH, PDSCH, or CSI-RS set by the upper layer for the symbol set of another cell.

[0356] 6) If the reference cell is configured by the upper layer to transmit SRS, PUCCH, PUSCH, or PRACH, or to receive PDCCH, PDSCH, or CSI-RS, the symbol designated as downlink or uplink by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated in the other cell is considered a flexible symbol.

[0357] 7) It is not expected to detect a first DCI format that schedules transmission or reception for a specific symbol in the first cell, and a second DCI format that schedules reception or transmission for that symbol in the second cell, respectively.

[0358] After applying the above procedure for directional collision handling within a set of cells configured as directionalCollisionHandling-r16, the UE does not expect directional collisions to occur between serving cells that the UE cannot perform simultaneous transmission and reception.

[0359] UE Procedure for Determining Slot Format

[0360] This section applies to serving cells included in the serving cell set by slotFormatCombToAddModList, slotFormatCombToReleaseList, availableRB-SetsToAddModList, availableRB-SetsToReleaseList, switchTriggerToAddModList, switchTriggerToReleaseList, co-DurationsPerCellToAddModList, and co-DurationsPerCellToReleaseList for the UE.

[0361] If the UE is set to the SlotFormatIndicator parameter by the upper layer, the UE is provided with SFI-RNTI by sfi-RNTI and with the payload size of DCI format 2_0 by dci-PayloadSize.

[0362] In addition, the UE L for DCI format 2_0 in one or more serving cells SFI having a CCE aggregation level Receives a search space set for monitoring PDCCH candidates and settings for the corresponding CORESET p. PDCCH candidates are CCE aggregation levels L for the search space set s in CORESET p. SFI The first about PDCCH is a candidate.

[0363] For each serving cell in a serving cell set, the following may be provided to the UE:

[0364] 1) ID of the serving cell by servingCellId

[0365] 2) SFI index field location of DCI format 2_0 by positionInDCI

[0366] 3) A set of slot format combinations by slot format combinations, wherein each slot format combination of the set of slot format combinations may include the following.

[0367] 4) For unpaired spectral operation, the reference SCS setting μ based on the subcarrier spacing SFI , if an auxiliary UL carrier is set in the serving cell, the reference SCS setting μ by subcarrierSpacing2 for the auxiliary UL carrier SFI,SUL

[0368] 5) For paired spectral operation, the reference SCS setting μ for DL ​​BWP by subcarrier spacing SFI,DL and reference SCS setting μ for UL BWP by subcarrierSpacing2 SFI,UL

[0369] 6) The locations of the available RB set indicator fields in DCI format 2_0 and the fields by available RB-SetsPerCell are as follows.

[0370] 1 bit, if the intraCellGuardBandsDL-List for the serving cell indicates that no intra-cell guard bands are set, where a value of '1' indicates that the serving cell is available for receiving and a value of '0' indicates that the serving cell is not available for receiving, and the serving cell remains in a state of being available or unavailable for receiving until the end of the remaining channel occupancy period. Or,

[0371] A bitmap mapped to the RB set of the serving cell, and the intraCellGuardBandsDL-List for the serving cell, where intraCellGuardBandsDL-List for the serving cell is set or if no intraCellGuardBandsDL-List for the serving cell is provided, where the bitmap is N RB,set,DLIncludes bits and N RB,set,DL is the number of RB sets of the serving cell, and if the value is '1', it indicates that the RB set is available for reception, and if the value is '0', it indicates that the RB set is not available for reception, and the RB set remains available or unavailable for reception until the end of the remaining channel occupancy period.

[0372] The location of the Channel Occupancy Period field, indicated by CO-DurationsPerCell in DCI format 2_0; this field represents the remaining channel occupancy period of the serving cell, starting from the first symbol of the slot where the UE detects DCI format 2_0 by providing a value from co-DurationList. In the Channel Occupancy Period field Bits are included, where COdurationListSize is the number of values ​​provided by co-DurationList. If CO-DurationsPerCell is not provided, the remaining channel occupancy period of the serving cell is the number of slots where the SFI-index field value provides the corresponding slot format, starting from the slot where the UE detects DCI format 2_0.

[0373] Reference SCS settings for co-DurationList by subcarrierSpacing.

[0374] Location of the search space set group switching flag field, DCI format 2_0 by SearchSpaceSwitchTrigger, where the field indicates a group of two search space set groups for PDCCH monitoring for scheduling for a serving cell or a serving cell set, and is provided by CellGroupsForSwitching.

[0375] The SFI index field value of DCI Format 2_0 indicates to the UE the slot format for each slot corresponding to the number of slots in each DL BWP or each UL BWP, starting from the slot where the UE detected DCI Format 2_0. The number of slots must be greater than or equal to the PDCCH monitoring period for DCI Format 2_0. The SFI index field contains bits, and maxSFIindex is the maximum value provided by the corresponding slot format combination ID. Slot formats are identified by their corresponding format indices as provided in Table 7, where 'D' represents downlink symbols, 'U' represents uplink symbols, and 'F' represents flexible symbols.

[0376] If the PDCCH monitoring periodicity for DCI format 2_0 provided to the UE for the search space set by the monitoring slot periodicity and offset is less than the duration of the slot format combination obtained by the UE during PDCCH monitoring for DCI format 2_0 by the corresponding SFI index field value, and the UE detects one or more DCI format 2_0s representing a slot format for one slot, the UE expects that each of the one or more DCI format 2_0s represents the same slot format.

[0377] The UE is not expected to be configured to monitor PDCCH for DCI format 2_0 in a second serving cell using an SCS larger than the serving cell.

[0378] Table 13 shows examples of slot formats for normal cyclic prefixes.

[0379] [Table 13]

[0380]

[0381]

[0382] For non-paired spectral operation for the UE in the serving cell, the reference SCS setting μ for each slot format is determined by the subcarrier spacing (SCS).SFI It is provided as a combination of slot formats indicated by the SFI index field value of DCI format 2_0. The UE references the SCS setting μ SFI and for active DL BWP or active UL BWP with SCS setting μ, μ≥μ SFI It is expected to be. Each slot format of the slot format combination indicated by the SFI index field value of DCI format 2_0 is 2 of the active DL BWP or active UL BWP. (μ-μ_SFI) It is applied to consecutive slots, and the first slot is the reference SCS setting μ SFI Starts simultaneously with the first slot of and references SCS setting μ SFI Each downlink, flexible, or uplink symbol corresponds to a succession of downlink, flexible, or uplink symbols in the SCS setting μ.

[0383] For paired spectral operation for the UE of the serving cell, the SFI index field of DCI format 2_0 indicates a combination of slot formats including the slot format combination for the reference DL BWP and the slot format combination for the reference UL BWP of the serving cell. The UE uses the reference SCS setting μ for the slot format combination indicated by the SFI index field value of DCI format 2_0 for the reference DL BWP of the serving cell, determined by the subcarrier spacing. SFI,DL It is provided. subcarrierSpacing2 is the reference SCS setting μ for the slot format combination indicated by the SFI index field value of DCI format 2_0 for the serving cell's reference UL BWP. SFI,UL Provides to the UE. μ SFI,DL ≥μ SFI,UL and each The value of the slot format provided by the value, where the value of the slot format is determined by the value of the slot format combination ID of the slot format combination, and the value of the slot format combination ID is set to the value of the SFI index field value of DCI format 2_0, and the first The value for the slot format combination applies to the reference DL BWP, and the following value applies to the reference UL BWP. μ SFI,DL <μ SFI,UL and each For the value, the first value of the slot format combination is applied to the reference DL BWP, and the next The value is applied to the reference UL BWP.

[0384] UE references SCS setting μ SFI,DL Provided with, the SCS setting μ of the active DL BWP DL μ for DL ≥μ SFI,DL satisfies. The UE references the SCS setting μ SFI,UL Provided with, the SCS setting μ of the active UL BWP UL μ for UL ≥μ SFI,UL It satisfies. For the reference DL BWP, each slot format of the slot format combination indicated by the SFI-index field value of DCI format 2_0 is indicated by the slotFormatCombinationId value mapped to the slotFormats value in slotFormatCombination, starting from the first slot that starts at the same time as the first slot of the reference DL BWP for the active DL BWP. It is applied to consecutive slots. Also, refer to the SCS setting μ SFI,DL Each downlink or flexible symbol is SCS setting μ DL About It corresponds to a number of consecutive downlinks or flexible symbols. For each slot format combination of the reference UL BWP, for the active UL BWP, starting from the first slot that begins at the same time as the first slot of the reference UL BWP. It is applied to consecutive slots. Also, refer to the SCS setting μ SFI,UL Each uplink or flexible symbol is SCS setting μ UL About It corresponds to a number of consecutive uplinks or flexible symbols.

[0385] In the case of an unpaired spectrum operation where the UE uses a second UL carrier in a serving cell, the SFI-index field value of DCI Format 2_0 indicates a slot format combination including a slot format combination for the serving cell's reference first UL carrier and a slot format combination for the serving cell's reference second UL carrier. For the slot format combination indicated by the SFI-index field value of DCI Format 2_0 for the serving cell's reference first UL carrier, the UE sets the reference SCS setting μ by subcarrierSpacing. SFI The UE is provided with the reference SCS setting μ by subcarrierSpacing2 for the slot format combination indicated by the SFI-index field value of DCI format 2_0 for the reference second UL carrier of the serving cell. SFI,SUL Receives. Each For +1 slotFormats value, the first slot format combination The value is applied to the reference 1 UL carrier, and the next value is applied to the reference 2 UL carrier.

[0386] The UE sets the SCS μ for the active UL BWP of the second UL carrier. SUL This μ SUL ≥μ SFI,SUL Reference SCS setting μ to satisfy SFI,SUL It is expected that this will be provided. For the reference first UL carrier, each slot format of the slot format combination indicated by the SFI-index field of DCI format 2_0 is for the active DL BWP and the active UL BWP of the first UL carrier, starting from the first slot that begins at the same time as the first slot of the reference first UL carrier. It applies to consecutive slots. Each slot format for the slot format combination of the reference 2nd UL carrier is for the active UL BWP of the 2nd UL carrier, starting from the first slot that begins at the same time as the first slot of the reference 2nd UL carrier. It applies to consecutive slots.

[0387] If the BWP of the serving cell is set to μ=2 and extended CP, the UE is μ SFI =0, μ SFI =1 or μ SFI Expected to be =2. The format of a slot with an extended CP is determined from the format of a slot with a standard CP. The UE determines the extended CP symbol as a downlink / uplink / flexible symbol if the overlapping standard CP symbols are each a downlink / uplink / flexible symbol. The UE determines the extended CP symbol as a flexible symbol if one of the overlapping standard CP symbols is a flexible symbol. The UE determines the extended CP symbol as a flexible symbol if the pair of overlapping standard CP symbols includes a downlink symbol and an uplink symbol.

[0388] Reference SCS settings μ SFI , μ SFI,DL , μ SFI,UL , or μ SFI,SUL For FR1, it is 0, 1, or 2, and for FR2, it is 2 or 3.

[0389] For a symbol set of a slot, the UE detects DCI format 2_0 containing an SFI-index field value directing the symbol set of the slot to an uplink, and does not simultaneously detect a DCI format directing to receive PDSCH or CSI-RS in the symbol set of the same slot.

[0390] For a symbol set of a slot, the UE detects DCI format 2_0 containing an SFI-index field value directing the symbol set of the slot to a downlink, and does not simultaneously detect DCI format, RAR UL grant, fallbackRAR UL grant, or successRAR directing to transmit PUSCH, PUCCH, PRACH, or SRS in the same symbol set of the slot.

[0391] For a set of symbols in a slot indicated by DCI format 2_0 as being within the remaining channel occupancy period through the channel occupancy period field or the SFI-index field, the UE does not detect DCI format 2_0 indicating that at a later point in time, no symbols in that set of symbols are within the remaining channel occupancy period through the channel occupancy period field or the SFI-index field.

[0392] For a symbol set of a slot indicated as downlink / uplink by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated, the UE does not detect a DCI format 2_0 containing an SFI-index field value indicating the symbol set of the slot as uplink / downlink or flexible, respectively.

[0393] For a symbol set of a slot corresponding to a candidate SS / PBCH block index of an SS / PBCH block, where the index is indicated by ssb-PositionsInBurst of SIB1, ssb-PositionsInBurst of ServingCellConfigCommon, NonCellDefiningSSB, or where the UE is not provided with dl-OrJointTCI-StateList, or by ssb-PositionsInBurst of SSB-MTCAdditionalPCI, or where the UE is indicated by a physical cell ID associated with an active TCI state for PDCCH or PDSCH, or for a symbol set of a slot corresponding to an SS / PBCH block set for L1 beam measurement / reporting, the UE does not detect DCI format 2_0 containing an SFI-index field value indicating the symbol set of the slot as an uplink.

[0394] The symbol set of the slot corresponding to the valid PRACH opportunity and N prior to the valid PRACH opportunity gap For a symbol, the UE does not detect DCI format 2_0 containing an SFI-index field value that indicates the symbol set of the corresponding slot as a downlink.

[0395] For the symbol set of a slot directed to the UE by pdcch-ConfigSIB1 of the MIB as a CORESET for the Type0-PDCCH CSS set, the UE does not detect DCI format 2_0 containing an SFI-index field value that directs the symbol set of the slot to an uplink.

[0396] This applies to the symbol set of slots flexibly directed to the UE by tdd-UL-DL-ConfigurationCommon and tdd-UL-DL-ConfigurationDedicated (if provided), or when tdd-UL-DL-ConfigurationCommon and tdd-UL-DL-ConfigurationDedicated are not provided to the UE, and the UE detects DCI format 2_0 which provides a format for the slot using a slot format value other than 255.

[0397] If one or more symbols in a symbol set are symbols of a CORESET configured for PDCCH monitoring in the UE, the UE receives PDCCH from the CORESET only if the SFI-index field value of DCI format 2_0 indicates that one or more of those symbols are downlink symbols.

[0398] If the SFI-index field value of DCI format 2_0 indicates that the symbol set of the slot is flexible and the UE detects a DCI format that instructs the UE to receive PDSCH or CSI-RS from the symbol set of the slot, the UE receives PDSCH or CSI-RS from the symbol set of the slot.

[0399] If the SFI-index field value of DCI format 2_0 indicates that the symbol set of the slot is flexible, and the UE detects a DCI format, RAR UL grant, fallbackRAR UL grant, or successRAR that instructs the UE to transmit PUSCH, PUCCH, PRACH, or SRS from the symbol set of the slot, the UE transmits PUSCH, PUCCH, PRACH, or SRS from the symbol set of the slot.

[0400] If the SFI-index field value of DCI format 2_0 indicates that the symbol set of the slot is flexible, and the UE does not detect a DCI format that instructs it to receive PDSCH or CSI-RS from the symbol set of the slot, or does not detect a DCI format that instructs the UE to transmit PUSCH, PUCCH, PRACH, or SRS from the symbol set of the slot, a RAR UL grant, fallbackRAR UL grant, or successRAR, the UE does not transmit or receive from the symbol set of the slot.

[0401] When a UE is configured by an upper layer to receive PDSCH or CSI-RS from a symbol set of a slot, the UE receives PDSCH or CSI-RS from a symbol set of a slot only when the SFI-index field value of DCI format 2_0 indicates the symbol set of the slot as downlink, and, if applicable, the symbol set is within the remaining channel occupancy period.

[0402] If the UE is configured by the upper layer to receive DL PRS from the symbol set of a slot, the UE receives DL PRS from the symbol set of a slot only when the SFI-index field value of DCI format 2_0 indicates the symbol set of that slot as downlink or flexible.

[0403] If the UE is configured by the upper layer to transmit PUCCH, PUSCH, or PRACH from the symbol set of a slot, the UE transmits PUCCH, PUSCH, or PRACH from the symbol set of a slot only when the SFI-index field value of DCI format 2_0 indicates the symbol set of that slot as an uplink.

[0404] If the UE is configured by the upper layer to transmit SRS from the symbol set of a slot, the UE transmits SRS only from the subset of the symbol set of the slot indicated by the SFI-index field value of DCI format 2_0 as the uplink symbol.

[0405] The UE does not simultaneously detect a DCI format, RAR UL grant, fallbackRAR UL grant, or successRAR that instructs the UE to transmit SRS, PUSCH, PUCCH, or PRACH in one or more symbols of the symbol set of the slot when the SFI-index field value of the DCI format 2_0 indicates the symbol set of the slot as a downlink.

[0406] The UE does not detect cases where the SFI-index field value of DCI format 2_0 indicates the symbol set of a slot as downlink or flexible for a symbol set of a slot containing symbols corresponding to a repetition of a PUSCH transmission enabled by a UL Type 2 grant PDCCH.

[0407] The UE does not simultaneously detect a DCI format that instructs the UE to receive PDSCH or CSI-RS from one or more symbols in the symbol set of the slot when the SFI-index field value of the DCI format 2_0 indicates the symbol set of the slot as an uplink.

[0408] If the UE is configured by the upper layer to receive CSI-RS or PDSCH from the symbol set of a slot, the UE detects DCI format 2_0 which indicates a slot format where the slot format value is not 255, and the slot format indicates a subset of the symbol set to uplink or flexible, or the UE detects a DCI format that indicates the UE to transmit PUSCH, PUCCH, SRS, or PRACH from at least one symbol in the symbol set, the UE cancels receiving CSI-RS from the symbol set of the slot or cancels receiving PDSCH from the slot.

[0409] In the case of UE operation using shared spectrum channel access in FR1 or in FR2-2 where the UE is set ChannelAccessMode2 = 'enabled', the UE is configured by the upper layer to receive CSI-RS, and if CO-DurationsPerCell is provided, for the symbol set of a slot designated as downlink or flexible by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated, or if tdd-UL-DL-ConfigurationCommon and tdd-UL-DL-ConfigurationDedicated are not provided, the UE cancels CSI-RS reception for the symbol set of the corresponding slot that is not included within the remaining channel occupancy period.

[0410] If the UE is configured by the upper layer to receive DL PRS from a slot's symbol set, the UE detects DCI format 2_0 which indicates a slot format where the slot format value is not 255, and the slot format indicates a subset of the symbol set to the uplink, or the UE detects a DCI format that indicates the UE to transmit PUSCH, PUCCH, SRS, or PRACH in at least one symbol of the symbol set, the UE cancels receiving DL PRS from the slot's symbol set.

[0411] If the UE is configured by the upper layer to transmit SRS, PUCCH, PUSCH, or PRACH in the symbol set of a slot, and the UE detects DCI format 2_0 indicating a slot format where the slot format value is not 255, and such slot format indicates a subset of the symbol set to downlink or flexible, or if the UE detects a DCI format indicating that the UE receives CSI-RS or PDSCH in a subset of the symbol set, then

[0412] If the UE does not indicate the [partialCancellation] function, the UE transmits PUCCH, PUSCH, or PRACH from the last symbol of the PDCCH reception where the first symbol of the symbol set detected the DCI format to T proc,2 If it occurs within [time], the transmission is not canceled. Otherwise, the UE cancels the PUCCH, PUSCH, or the actual iteration of PUSCH or the PRACH transmission in the symbol set.

[0413] If the UE indicates the [partialCancellation] function, the UE detects the DCI format from the last symbol of the received PDCCH T proc,2 PUCCH, PUSCH, or PRACH transmissions are not cancelled in symbols of the symbol set occurring within the following period. The UE cancelled the PRACH transmission in the actual repetition of PUCCH, PUSCH, or PUSCH, or in symbols of the remaining symbol set.

[0414] The UE detects the DCI format from the last symbol of the received PDCCH, T proc,2 The UE does not cancel SRS transmissions on symbols in the symbol subset occurring within [time]. The UE cancels SRS transmissions on symbols in the remaining symbol subset.

[0415] T proc,2 is the PUSCH preparation time for the corresponding UE processing capability, and d 2,1Assuming =1, μ is the SCS setting of PDCCH including the DCI format and the SCS setting of SRS, PUCCH, PUSCH or μ r It corresponds to the smallest SCS setting among them. Here, μ r corresponds to the PRACH SCS setting if the PRACH SCS setting is 15kHz or higher, and otherwise μ r =0.

[0416] If the UE is configured by the upper layer to receive CSI-RS, or detects DCI format 0_1 ​​and is instructed to receive CSI-RS from one or more sets of RBs and the symbol set of the slot, or if the UE detects DCI format 2_0 and indicates that the bitmap is not receivable from any of the one or more sets of RBs, the UE cancels receiving CSI-RS from the symbol set of the slot.

[0417] For PDCCH monitoring, the UE considers the flexible symbols of the CORESET set in the UE as downlink symbols if the UE does not detect the SFI-index field value of DCI format 2_0 which directs the symbol set of the slot to flexible or uplink, and also does not detect the DCI format which directs to transmit SRS, PUSCH, PUCCH, or PRACH in that symbol set.

[0418] For a symbol set of slots designated as flexible (F) by tdd-UL-DL-ConfigurationCommon and tdd-UL-DL-ConfigurationDedicated (if provided), or if tdd-UL-DL-ConfigurationCommon and tdd-UL-DL-ConfigurationDedicated are not provided to the UE, if the UE fails to detect DCI format 2_0 providing a slot format for the slot,

[0419] 1) The UE receives PDSCH or CSI-RS from the symbol set of the corresponding slot, only when the UE receives a DCI format containing instructions for it.

[0420] 2) The UE transmits PUSCH, PUCCH, PRACH, or SRS in the symbol set of the corresponding slot, only when the UE receives a DCI format containing instructions for the corresponding RAR UL grant, fallbackRAR UL grant, or successRAR.

[0421] 3) The UE receives the PDCCH.

[0422] 4) If the UE is configured by the upper layer to receive PDSCH from the symbol set of a slot, the UE does not receive PDSCH from the symbol set of that slot.

[0423] 5) If the UE is configured by the upper layer to receive CSI-RS from the symbol set of a slot, the UE does not receive CSI-RS from the symbol set of that slot unless CO-DurationsPerCell is provided and the symbol set of the slot falls within the remaining channel occupancy period.

[0424] 6) If the UE is configured by the upper layer to receive DL PRS from the symbol set of a slot, the UE receives DL PRS from the symbol set of that slot.

[0425] 7) If the UE is configured by the upper layer to transmit SRS, PUCCH, PUSCH, or PRACH in the slot's symbol set, but enableConfiguredUL is not provided,

[0426] a) If the UE does not instruct the [partialCancellation] function, the first symbol of PUCCH, PUSCH, the actual repetition of PUSCH, or PRACH is T from the last symbol of the PDCCH reception configured to monitor DCI format 2_0. proc,2 If it occurs within the slot, the UE does not cancel the transmission. Otherwise, the UE cancels the transmission of PUCCH, PUSCH, the actual repetition of PUSCH, or PRACH from the slot.

[0427] b) If the UE indicates the [partialCancellation] function, the UE monitors T from the last symbol of the PDCCH reception configured to monitor DCI format 2_0. proc,2 PUCCH, PUSCH, actual repetition of PUSCH, or PRACH transmission in the symbols of the symbol set occurring within [time] is not cancelled. The UE cancelled PUCCH, PUSCH, actual repetition of PUSCH, or PRACH transmission in the symbols of the remaining symbol set.

[0428] The UE is configured to monitor DCI format 2_0 from the last symbol of the received PDCCH T proc,2 The UE does not cancel SRS transmissions on symbols of the symbol set occurring within [timeframe]. The UE cancels SRS transmissions on symbols of the remaining symbol set.

[0429] T proc,2 is the PUSCH preparation time for the corresponding UE processing capability, and d 2,1 It can be assumed that =1. μ is the SCS setting of PDCCH containing DCI format 2_0 and the SCS setting of SRS, PUCCH, PUSCH or μ r It corresponds to the smallest SCS setting among them. Here, μ r corresponds to the PRACH SCS setting if the PRACH SCS setting is 15kHz or higher, and otherwise μ r =0.

[0430] If the UE is configured by the upper layer to transmit SRS, PUCCH, PUSCH, or PRACH from the slot's symbol set and enableConfiguredUL is provided, the UE can transmit SRS, PUCCH, PUSCH, or PRACH, respectively.

[0431] In a cell in the FR1 frequency band, if a UE is performing unpaired spectrum operation and scheduling restrictions based on RRM measurement are not applied, and the UE detects a DCI format that instructs it to transmit in a symbol set, there is no need to perform RRM measurement in another cell based on receiving an SS / PBCH block or CSI-RS containing at least one symbol from the symbol set.

[0432] TDD slot and / or symbol configurations can be determined through multiple operations. For example, all UEs in a cell can be assigned a cell-specific DL / UL pattern via tdd-UL-DL-ConfigurationCommon. Additionally, a UE can receive resources that were previously held as flexible slots and / or symbols as UE-specific allocations via the dedicated RRC signal tdd-UL-DL-ConfigurationDedicated. tdd-UL-DL-ConfigurationCommon can be transmitted via SIB1 or dedicated RRC signaling. For a specific slot and / or symbol to be configured as a flexible slot and / or symbol, both must be configured as flexible through UE and / or cell-specific slot configurations. In this case, since tdd-UL-DL-ConfigurationDedicated is optional, the network may not configure UE-specific slots and / or symbols. In this case, a DL / UL pattern configured based on tdd-UL-DL-ConfigurationCommon is used. If the UE does not receive the SlotFormatIndicator setting, it may receive PDSCH or CSI-RS in some or all symbols of the slot according to the instructions of DCI format 1_0, DCI format 1_1, or DCI format 0_1. Additionally, if the UE does not receive the SlotFormatIndicator setting, the UE may transmit PUSCH, PUCCH, PRACH, or SRS in some or all symbols of the slot according to the instructions of DCI format 0_0, DCI format 0_1, DCI format 1_0, DCI format 1_1, or DCI format 2_3.

[0433] Additionally, the base station does not set RO on resources allocated in slot and / or symbol units for HD DL transmission, and the UE may not expect RO setting. For resources allocated as HD flexible, RO setting may be performed based on several constraints. For example, if RO is not set via tdd-UL-DL-ConfigurationCommon, the PRACH occasion for a resource set as a PRACH slot does not lie before the SS / PBCH block resource, or is at least N with the last SS / PBCH block reception symbol. gap If it is located after the number of symbols, the corresponding PRACH opportunity can be treated as a valid RO.

[0434] On the other hand, if RO is configured via tdd-UL-DL-ConfigurationCommon, the PRACH opportunity of the resource configured as a UL symbol or PRACH slot is not located before the SS / PBCH block resource, or at least N with the last SS / PBCH block repeat symbol. gap If it is located after the number of symbols, the corresponding PRACH opportunity can be treated as a valid RO.

[0435] In the present disclosure, an RO that cannot be used due to the aforementioned constraint is referred to as an invalid RO. Hereinafter, what is specified as a slot and / or symbol may be interpreted as a unit of slots and symbols. Also, what is specified as SBFD (subband full duplex) and / or non-SBFD may be understood as an SBFD slot / symbol and / or non-SBFD slot / symbol.

[0436] FIG. 10 illustrates an example of a structure in which SBFD slots are allocated in the time and frequency axes according to one embodiment of the present disclosure.

[0437] Referring to FIG. 10, when SBFD settings are applied to a resource in which a DL slot or a flexible (F) slot is set by an upper layer, some frequency resources of the SBFD slot may be set to DL, i.e., the SBFD DL subband, and some frequency resources may be set to UL, i.e., the SBFD UL subband. Here, a frequency gap may be set between the frequency resources of the SBFD DL subband and the frequency resources of the SBFD UL subband. Meanwhile, the direction of each SBFD subband may be indicated through a dynamic indication (e.g., DCI format 2_0 or SFI (slot format indicator)).

[0438] FIG. 11 illustrates an example of a downlink slot to which an SBFD setting is applied according to one embodiment of the present disclosure. In the present disclosure, an SBFD-aware UE (1110, which may be referred to as an "SBFD-aware terminal") refers to a terminal capable of performing SBFD operations and HD operations, and a legacy UE (1120) may be understood as a terminal capable of performing HD operations.

[0439] Referring to FIG. 11, the legacy UE (1120) recognizes a downlink slot resource with an SBFD configuration applied as a DL resource (e.g., a DL symbol). Therefore, the legacy UE (1120) does not expect an RO configuration for the downlink slot with an SBFD configuration applied, as in the existing operation.

[0440] However, since the SBFD-aware UE (1110) recognizes the downlink slot resource to which the SBFD setting is applied as an SBFD resource (e.g., an SBFD symbol), it can expect an RO setting in the SBFD UL subband according to the new rule. The new rule is to view the SBFD symbol as a flexible symbol, which specifically means a condition in which a setting can be made in both the UL direction and the DL direction from a single symbol. At this time, the set RO or RO group can only be used by the SBFD-aware UE (1110).

[0441] When determining the RO setting index, the base station may allow RO to be set for SBFD symbols configured as downlink by TDD settings. For example, the base station may inform the terminal of SBFD symbols through information included in the system information block (SIB). Additionally, it may indicate whether the symbols within the slot are downlink symbols, uplink symbols, or flexible symbols by TDD settings. In this case, a symbol designated as a downlink symbol by TDD settings may be a symbol designated as an SBFD symbol by the SIB. In such a case, the said SBFD symbol may be referred to as an SBFD symbol configured as downlink by TDD settings.

[0442] Likewise, a symbol designated as a flexible symbol by the TDD setting may be a symbol designated as an SBFD symbol by the SIB. In this case, the SBFD symbol may be referred to as an SBFD symbol set as flexible (flexible, F) by the TDD setting.

[0443] Based on parameters related to the signaled RO configuration index, ROs may be located in SBFD symbols and non-SBFD symbols. In this case, ROs that can be PRACH transmitted by legacy UEs and SBFD-aware UEs may be referred to as legacy ROs below, and ROs that can be PRACH transmitted only by SBFD-aware UEs may be referred to as SBFD ROs. Legacy UEs may determine that legacy ROs located in non-SBFD symbols and flexible symbols (e.g., SBFD symbols configured as flexible (F) by TDD configuration) are valid ROs, and SBFD-aware UEs may determine that legacy ROs and SBFD ROs located in non-SBFD symbols and SBFD symbols are valid ROs.

[0444] FIGS. 12 and FIGS. 13 illustrate examples of flexible slots to which SBFD settings according to one embodiment of the present disclosure are applied.

[0445] FIG. 12 illustrates an example of a flexible slot when the RO is configured by a legacy RO configuration, and FIG. 13 illustrates an example of a flexible slot when the RO is configured by a separate RO configuration. Since the legacy UE (1220 or 1320) treats the allocated resource as a flexible slot, it determines the RO configuration based on existing rules and determines whether the RO is valid or invalid. On the other hand, since the SBFD-aware UE (1210 or 1310) recognizes the resource as an SBFD resource, it can expect the RO configuration in the SBFD UL subband according to the new rules (the SBFD UL subband may also be expressed as 'UL usable PRBs'. Hereinafter, the SBFD UL subband may be replaced with UL usable PRBs). For example, when there are both legacy UEs (1220, 1320) and SBFD-aware UEs (1210, 1310), when setting up an RO or RO group, the location of the time and frequency resources of the RO can be determined by considering SBFD and non-SBFD. The settings and methods applied to the RO below can be applied in the same way to the RO group.

[0446] A. RO Configuration and Conflicts in SBFD DL Subbands

[0447] Legacy RO can be understood as a resource that legacy UEs and SBFD-aware UEs can use for PRACH transmissions, and SBFD dedicated RO can be understood as a resource that only SBFD-aware UEs can use for PRACH transmissions. SBFD dedicated RO may also be simply referred to as SBFD RO below.

[0448] The following two methods can be proposed as ways to configure legacy RO and SBFD-dedicated RO.

[0449] First, a method may be used in which legacy ROs and SBFD-dedicated ROs are supported through respective RO configurations. To this end, multiple (e.g., two) RO configurations may be configured. In the present disclosure, a configuration in which multiple ROs are configured individually is referred to as a separated RO configuration.

[0450] FIG. 14 illustrates an example of a separated RO setting according to one embodiment of the present disclosure.

[0451] Referring to Fig. 14, it can be seen that RO1 and RO2 can be set at different frequencies by separate RO settings. For example, the ROs can be set by two separate RACH settings (RACH setting option 2). For convenience, let's call the two separate RACH settings the legacy RACH setting and the additional RACH setting. The legacy RACH setting can be described as a RACH setting that can be interpreted by both the legacy UE and the SBFD-cognitive UE, and the additional RACH setting can be a RACH setting that can be interpreted only by the SBFD-cognitive UE. In this case, RO1 can be set by the additional RACH setting, and RO2 can be set by the legacy RACH setting.

[0452] Secondly, a method can be used in which legacy ROs and SBFD-only ROs are supported through a single RO configuration. A configuration in which legacy ROs and SBFD-only ROs are configured simultaneously can be referred to as a shared RO configuration or a single RACH configuration. Through the single RACH configuration, legacy UEs and SBFD-aware UEs can receive the location of the RO together.

[0453] In the following, it is assumed that even if indicated only as a slot or a symbol, it can be applied to both slot and symbol units. For example, even if specified only as SBFD or non-SBFD, it may mean an SBFD slot / symbol or a non-SBFD slot / symbol.

[0454] In conventional standard specifications (e.g., 3GPP NR, Rel-18), SBFD slots can be used in downlink (DL) slots and flexible slots of legacy systems.

[0455] Looking at legacy behavior, current TDD slot / symbol configuration is performed through the following two actions. The first action is tdd-UL-DL-ConfigurationCommon, through which all UEs in the cell are assigned cell-specific DL / UL patterns. The second action is tdd-UL-DL-ConfigurationDedicated, a dedicated RRC signal, which configures resources that remained as flexible slots / symbols to be UE-specific.

[0456] tdd-UL-DL-ConfigurationCommon can be transmitted via SIB1 or dedicated RRC signaling. A specific slot can be configured as a flexible slot / symbol only if it is configured to be flexible through both terminal-specific slot configurations and cell-specific slot configurations.

[0457] Since tdd-UL-DL-ConfigurationDedicated is optional, the network is not obligated to perform the second operation, and in this case, the DL / UP pattern configured by tdd-UL-DL-ConfigurationCommon is used. At this time, if the UE does not have the SlotFormatIndicator set, the UE may receive PDSCH or CSI-RS in some or all symbols of the slot according to the instructions of DCI format 1_0, DCI format 1_1, and DCI format 0_1. If the UE does not have the SlotFormatIndicator set, the UE may transmit PUSCH, PUCCH, PRACH, and SRS in some or all symbols of the slot according to the instructions of DCI format 0_0, DCI format 0_1, DCI format 1_0, DCI format 1_1, and DCI format 2_3.

[0458] Meanwhile, the direction of each SBFD subband may be indicated through dynamic indication (e.g., DCI format 2_0, SFI).

[0459] Parts that cannot be used as RO (random access occasion) or are invalid in legacy systems can be used as RO in SBFD systems. Therefore, it is necessary to develop RO settings and power control-related operations for SBFD systems so that they can operate with legacy systems.

[0460] In accordance with the above needs, the present disclosure describes a shard power control method that can be used with legacy systems centered on SBFD systems, and a separated (or additional) power control method using independent parameters.

[0461] First, the existing operation and limitations of legacy RO will be explained. Legacy RO operates differently in DL / flexible / UL slots. For example, both the base station and the terminal implicitly expect that legacy RO is not configured in downlink slots.

[0462] Legacy ROs may be set in slots of other link directions (e.g., uplink slots), but the base station and the terminal can implicitly determine, based on the same criteria, whether the use of such ROs is valid or invalid through other higher-priority signaling. For example, if the PRACH occasion of a resource set as a PRACH slot does not lie before the SS / PBCH block resource, or if at least N is present with the last SS / PBCH block reception symbol. gap If it is located after the number of symbols, it becomes a valid RO.

[0463] If tdd-UL-DL-ConfigurationCommon is configured, the PRACH opportunity of the resource configured as a UL symbol or configured as a PRACH slot is not located before the SS / PBCH block resource, or at least N with the last SS / PBCH block receiving symbol. gap If it is located after the number of symbols, it becomes a valid RO. An RO that cannot be used due to such constraints is called an invalid RO.

[0464] Multiple (e.g., two) RO types may be provided for the SBFD random access operation.

[0465] For example, in the case of RACH configuration option 1, the RO is configured with a single legacy RACH configuration, and the RO may consist of an additional RO in an SBFD symbol and a legacy RO in a non-SBFD symbol / flexible SBFD symbol.

[0466] For RACH configuration option 2, RO is configured with legacy RACH configuration and additional RACH configuration, legacy RO in non-SBFD symbols is configured by legacy RACH configuration, and additional RO in SBFD symbols (and / or non-SBFD symbols) can be configured by additional RACH configuration.

[0467] For SBFD-aware terminals in the RRC CONNECTED state, both RACH configuration option 1 (hereinafter simply referred to as Option 1, which uses a single RACH configuration and is based only on the existing parameters of said single RACH configuration) and RACH configuration option 2 (hereinafter simply referred to as Option 2, which uses two separate RACH configurations including one legacy RACH configuration and one additional RACH configuration) are supported. Simultaneous activation of both options (Option 1 and 2) for a single terminal is not supported. The terminal is not required to support both options.

[0468] For SBFD-aware terminals in the RRC CONNECTED state, and for RACH configuration option 1, legacy SSB-RO mapping is applied to legacy ROs (which may include ROs within symbols other than SBFD symbols and ROs within SBFD symbols configured as flexible by tdd-UL-DL-ConfigurationCommon, if present). For ROs within SBFD symbols configured as downlink by tdd-UL-DL-ConfigurationCommon, a separate SSB-RO mapping may be used. For RACH configuration option 1, legacy SSB-RO mapping rules may be reused for additional ROs.

[0469] For RACH setting option 1, the following method may be supported to determine the lowest RO of additional ROs within SBFD symbols.

[0470] For example, the parameter msg1-FrequencyStart within rach-ConfigCommon can be reinterpreted as the frequency offset of the lowest RO in the frequency domain relative to the lowest PRB of the UL-available PRBs. ROs outside the UL-available PRBs can be interpreted as invalid or non-existent.

[0471] For RACH setting option 2, in addition to the SSB-RO mapping for legacy-ROs configured by the legacy RACH setting, legacy SSB-RO mapping rules can be used for additional ROs configured by the additional RACH setting.

[0472] N within additional ROs rep preamble For a PRACH transmission with preamble repetition, N rep preambleA set of valid additional ROs and the above N rep preamble It can support the reuse of current standard specification rules to determine the time period of the set(s) of valid additional ROs. The above N rep preamble The time period of the set(s) of valid additional ROs can be determined independently of the time period for legacy ROs.

[0473] In this specification, additional ROs may be defined as follows.

[0474] For RACH configuration option 1 (hereinafter simply referred to as option 1), additional ROs may include ROs within SBFD symbols configured as downlinks by tdd-UL-DL-ConfigurationCommon, and ROs across SBFD symbols configured as downlinks by tdd-UL-DL-ConfigurationCommon and SBFD symbols configured as flexible.

[0475] With respect to RACH setting option 2 (hereinafter simply referred to as option 2), additional ROs may refer to ROs set by additional RACH settings.

[0476] For legacy ROs, legacy SSB-RO mapping rules may be followed. For ROs within SBFD symbols configured as downlinks by tdd-UL-DL-ConfigurationCommon, a separate SSB-RO mapping may be used.

[0477] For Option 1, existing SSB-RO mapping rules can be reused for additional ROs. For Option 2, existing SSB-RO mapping rules can be used for additional ROs configured by additional RACH settings, separate from the SSB-RO mapping for legacy ROs configured by legacy RACH settings.

[0478] In Option 1, for ROs within SBFD symbols configured as downlinks by tdd-UL-DL-ConfigurationCommon, the following additional conditions may be supported for RO validation.

[0479] Condition #1: A valid RO must be at least N after the last downlink non-SBFD symbol. gap It must start after the symbol.

[0480] Condition #2: Valid ROs must be at least N after SSB. gap It must start after the symbol.

[0481] For Option 2, additional RO may be valid in the following cases.

[0482] When additional ROs are located within SBFD symbols. Or, through network configuration, it may be valid when starting from an SBFD symbol and ending at a non-SBFD symbol within the same slot or across different slots.

[0483] At least N after the last downlink non-SBFD symbol gap When starting after a symbol.

[0484] At least N since the latest SSB gap When starting after a symbol.

[0485] Cases where it does not overlap with the SSB in the time domain.

[0486] It may be the network's responsibility to ensure that additional ROs are configured within the bandwidth of uplink available PRBs (UL usable PRBs).

[0487] RACH procedure in multiple features

[0488] In the prior art, the RACH opportunity (random access channel occasion: hereinafter abbreviated as RO) for transmitting the preamble (message 1) of the random access process was set only in HD resources, and the scheduled PUSCH transmission (message 3 PUSCH) following the random access response (message 2) was also set only in HD resources. However, in NR or subsequent wireless communication systems, the RO is not set only in HD resources but can also be set in SBFD resources. Furthermore, the resources for transmitting the message 3 PUSCH are not limited to HD resources but can also be set in SBFD resources.

[0489] In conventional technology, power control for message 3 PUSCH transmission is based on the power (or power parameter) of message 1 transmission. However, if the transmission resource type for message 1 transmission and the transmission resource type for message 3 transmission are different from each other, applying this conventional technology as is may result in the message 3 transmission power being determined differently from what the terminal intended.

[0490] Additionally, for configuring RO, there are RACH configuration options 1 and RACH configuration options 2. In Option 1, RO can be configured using legacy RACH configuration, and in Option 2, RO can be configured using legacy RACH configuration and additional RACH configuration (in other words, using two separate RACH configurations). For example, legacy RACH configuration can be provided by a higher-level information element / parameter (e.g., RRC (radio resource control) layer) called sbfd-RACH-SingleConfig, and additional RACH configuration can be provided by a higher-level information element / parameter called sbfd-RACH-DualConfig. Depending on the RACH setting method and whether SBFD resources are used in Message 1 / Message 3, it is necessary to clearly define how power control parameters for Message 3 PUSCH transmission will be set / instructed.

[0491] First, the prior art is described, and the method according to the present disclosure is described.

[0492] In the case of conventional technology (e.g., up to NR Release 18), the terminal receives specific parameters from the base station, e.g., preambleReceivedTargetPower and Δ_PREAMBLE_Msg3 (e.g., Δ PREAMBLE_Msg3 ) can be received. In this case, Δ_PREAMBLE_Msg3 is provided from the base station via msg3-DeltaPreamble or deltaPreamble, and if deltaPreamble parameters exist, an override is performed even if msg3-DeltaPreamble exists.

[0493] FIG. 15 illustrates an example of setting msg3-DeltaPreamble and deltaPreamble through RRC information elements (information element: IE) / parameters and the terminal operation accordingly.

[0494] The terminal can receive Msg3-DeltaPreamble (hereinafter referred to as msg3-DeltaPreamble) and DeltaPreamble (hereinafter referred to as deltaPreamble) through RRC information elements / parameters. For example, msg3-DeltaPreamble may exist in PUSCH-ConfigCommon IE included in BWP-UplinkCommon, and deltaPreamble may exist in FeatureCombinationPreambles IE included in FeatureCombinationPreamblesList included in RACH-ConfigCommon included in BWP-UplinkCommon.

[0495] Here, BWP-UplinkCommon may be an information element used to configure the common parameters of the uplink BWP.

[0496] RACH-ConfigCommon may be an information element used to specify cell-specific random access parameters.

[0497] FeatureCombinationPreamblesList may be an information element that defines a preamble partition associated with each feature combination. For example, a feature combination may include at least one of features such as RedCap (reduced capability), SDT (small data transmission), slicing, and Msg3 iteration. FeatureCombinationPreamblesList may be a list of information (FeatureCombinationPreambles) that indicates the preambles that the terminal can apply / select according to these feature combinations.

[0498] FeatureCombinationPreambles can be information elements that connect a set of preambles with a feature combination.

[0499] deltaPreamble may mean the power offset between the transmission of message 3 (msg3) (or msgA-PUSCH) and the RACH preamble (message 1).

[0500] msg3-DeltaPreamble refers to the power offset between the transmission of message 3 (msg3) and the RACH preamble (message 1).

[0501] If the deltaPreamble parameter exists, the terminal can override msg3-DeltaPreamble even if msg3-DeltaPreamble exists (deltaPreamble overrides msg3-DeltaPreamble). In other words, the deltaPreamble parameter can be used even if msg3-DeltaPreamble exists.

[0502] Meanwhile, to support multiple features, an additional RACH config IE was introduced using the concept of feature combination. In this case, msg3-DeltaPreamble and deltaPreamble may be configured / instructed as shown in Fig. 16.

[0503] Figure 16 shows an example of setting / instructing msg3-DeltaPreamble and deltaPreamble by RRC when an additional RACH configuration (additional RACH config IE) is added.

[0504] Referring to Fig. 16, deltaPreamble may exist in FeatureCombinationPreambles IE included in FeatureCombinationPreamblesList included in RACH-ConfigCommon included in BWP-UplinkCommon. Additionally, deltaPreamble may exist in FeatureCombinationPreambles IE included in FeatureCombinationPreamblesList included in RACH-ConfigCommon included in Additional RACH-ConfigList included in BWP-UplinkCommon. msg3-DeltaPreamble may exist in PUSCH-ConfigCommon IE included in BWP-UplinkCommon.

[0505] If the deltaPreamble parameter exists, the terminal can override msg3-DeltaPreamble even if msg3-DeltaPreamble exists (deltaPreamble overrides msg3-DeltaPreamble). In other words, the deltaPreamble parameter can be used even if msg3-DeltaPreamble exists.

[0506] As illustrated in FIG. 16, when a terminal performs a RACH process for a certain function (purpose / characteristic, hereinafter the same), the terminal can perform power control of msg3 based on the information of the RACH-ConfigCommon IE containing the said function. The said function may be directly included in BWP-UplinkCommon or may be included in the RACH-ConfigCommon indicated through an additional RACH-Config List.

[0507] Specific embodiments of the present disclosure

[0508] In a random access process, when transmitting Message 3 (which can be denoted as Msg3 / msg3), if SBFD systems and non-SBFD systems are mixed, a case may be considered where different systems are used for Message 1 (which can be denoted as Msg1 / msg1) and for the transmission of Msg3. Since the Msg3 PUSCH transmission calculates power control by referencing the preambleReceivedTargetPower parameter from the Msg1 transmission, if the systems for Msg1 and Msg3 transmissions are different, an unintended transmission power may be calculated at the terminal. To solve the above problem, the present disclosure describes a method for changing the power control in the Msg3 transmission to match the power control intent in the Msg1 transmission when the systems for Msg1 and Msg3 transmissions are different.

[0509] In uplink transmission, SBFD can exhibit lower latency than non-SBFD. Additionally, compared to non-SBFD configurations of DDDSUDDDSU, SBFD allows terminals to be allocated longer uplink time resources and can increase cell range or coverage through long prac or prac repetitions. However, SBFD can cause cross-link interference (CLI) between subbands, and antenna configurations in SBFD may differ from those in non-SBFD. Therefore, system conditions may differ between SBFD and non-SBFD.

[0510] In addition, increasing the PRACH power in SBFD will improve PRACH reception performance but may cause significant interference to adjacent UEs. Conversely, lowering the PRACH power in SBFD will reduce the amount of interference to adjacent UEs but will worsen PRACH reception performance. In this case, reception performance will be worse than that of non-SBFD because interference also occurs due to adjacent base stations or self-interference.

[0511] Considering these points, there may be a need to configure power control in SBFD and non-SBFD systems through different methods. Accordingly, when SBFD and non-SBFD systems are mixed, cases where different systems are used for Msg1 transmission and Msg3 transmission can be considered. In conventional standard specifications, power control calculations are performed by referencing the preambleReceivedTargetPower parameter in Msg1 transmission during Msg3 PUSCH transmission; therefore, if the systems in Msg1 and Msg3 transmission are different, unintended transmission power may be calculated at the terminal. To solve this problem, the present disclosure also describes a method for changing the power control in Msg3 transmission to match the power control intent in Msg1 transmission when the systems in Msg1 and Msg3 transmission are different. Depending on the RACH setting option for RO setting for PRACH transmission, the value of the preambleReceivedTargetPower parameter given to Msg1 that can be applied to Msg3 may vary. Considering this, we will explain how to set the power control of Msg 3.

[0512] <Msg1 전송에서 Msg3로의 전송 시스템 판단>

[0513] The following four cases can be considered.

[0514] Case 1) Msg1 transmission on RO in non-SBFD symbol, Msg3 PUSCH transmission in non-SBFD symbol

[0515] Case 2) Msg1 transmission in RO for SBFD symbols, Msg3 PUSCH transmission in non-SBFD symbols

[0516] Case 3) Transmission of Msg1 in RO at SBFD symbol, transmission of Msg3 PUSCH at SBFD symbol

[0517] Case 4) Msg1 transmission in RO in non-SBFD symbols, Msg3 PUSCH transmission in SBFD symbols.

[0518] A terminal that does not recognize SBFD may only correspond to Case 1. However, for an SBFD-aware terminal, if Msg1 is transmitted via an SBFD symbol as in Case 2 or Case 3, or if Msg1 is transmitted via a non-SBFD symbol as in Case 1 or Case 4, Msg3 can be transmitted using a symbol of the same type as the symbol type used to transmit Msg1 or a symbol of a different type.

[0519] Therefore, the base station may issue a separate instruction. For example, the above separate instruction may be transmitted via msg2 RAR. For example, it may be indicated via resource allocation within the PUSCH frequency resource allocation. If Msg3 PUSCH is transmitted via a non-SBFD symbol, the PUSCH frequency resource allocation is set based on the BWP (bandwidth part); if Msg3 PUSCH is transmitted via an SBFD symbol, the PUSCH frequency resource allocation is set based on the UL subband (this may specifically mean the UL usable PRB, which is a frequency resource where the UL BWP and the UL subband overlap).

[0520] The following table provides examples of Random Access Response Grant Content field sizes.

[0521] [Table 14]

[0522]

[0523] In the case of Msg 3 retransmission, frequency resource allocation is set through DCI format 0_0 scrambled with TC_RNTI.

[0524] Through the above instructions, the SBFD-aware terminal can determine whether to transmit Msg3 in SBFD / non-SBFD symbols. This applies to all cases 1 through 4. If cases 1 through 4 are explicitly indicated, the type of Msg3 may be additionally set via RAR or other instructions. However, in the case of cases 1 and 3, the symbol type of Msg3 may be transmitted using the same type as Msg1 without instructions via RAR.

[0525] When cases 1 to 4 are implicitly indicated, the TDMA of Msg3 can be set through the value of the PUSCH time resource allocation of RAR, and the terminal can implicitly perform the cases according to the set time resource and the slot type in the time resource. An SBFD-aware terminal can notify the base station that the terminal is an SBFD-aware terminal before transmitting Msg3 through early detection, etc.

[0526] If a base station sets an RO in an SBFD symbol and an SBFD-aware UE selects the RO in the SBFD symbol and transmits Msg1, and the base station detects a PRACH preamble in that RO, the terminal that transmitted the PRACH preamble may be considered to have SBFD-aware capability. (In cases such as Case 2 and Case 3, operation may be performed with such a PRACH resource setting.)

[0527] If the base station configures an RO distinct from the existing RO in a non-SBFD symbol, or directs a PRACH preamble for an SBFD-aware UE distinct from the PRACH preamble for the existing non-SBFD UE within the RO directed for the existing non-SBFD UE, and the SBFD-aware UE transmits Msg1 by selecting either the RO directed for the SBFD-aware UE in the non-SBFD symbol or the PRACH preamble distinguished for the SBFD-aware UE within the existing RO directed in the non-SBFD symbol, the base station may consider the terminal that transmitted the PRACH preamble to have SBFD awareness capability if it detects the PRACH preamble. (Such resource configuration may be required for Case 4.)

[0528] Through such resource configuration and resource selection methods, when Msg1 is transmitted to an SBFD-specific RO, the base station can naturally know that the terminal is an SBFD-aware terminal, and when the SBFD-aware terminal transmits to an SBFD-non-specific RO, additional information (e.g., transmission of PRACH to an additionally directed RO or transmission of PRACH through a distinguished PRACH preamble instruction) may be required to support early detection for the base station to know that the terminal is an SBFD-aware terminal.

[0529] In this case, the terminal can normally perform the operations of cases 1 through 4 through the RAR. However, if the SBFD-aware terminal does not notify the base station by any means that the terminal is an SBFD-aware terminal until the base station transmits the RAR, the base station cannot know whether the terminal can use the SBFD system. Therefore, the base station may determine that the terminal will operate in case 1 and may not issue a separate instruction to the terminal for using the SBFD system of Msg3.

[0530] <Msg1 PRACH 설정의 개수를 고려한 Msg3 전송 판단 시 고려사항>

[0531] Next, the number of Msg1 PRACH settings is a consideration. The question arises as to whether to provide separate PRACH setting instructions to the SBFD-aware terminal. If separate PRACH setting instructions are provided to the SBFD-aware terminal, the instructions may include Msg1 PRACH power control parameters. In this case, there will be a total of two PRACH power control parameters instructed to the terminal. For example, the terminal may use two different preambleReceivedTargetPowers in SBFD / non-SBFD systems, respectively.

[0532] Alternatively, even if the terminal does not receive a separate, independent PRACH setting instruction from the base station, it may use independent PRACH power control parameters through reinterpretation in two different systems based on a prior agreement. In this case as well, the terminal is expected to use two preambleReceivedTargetPowers in two different systems. Alternatively, the terminal may have received instructions for two Msg1-related parameters for preambleReceivedTargetPower, but may use only the parameter for the single type used in the Msg1 transmission for the Msg3 transmission. In this case, the terminal determines that it has received a single PRACH setting during the following operations and performs the operation.

[0533] The above points can be summarized as follows.

[0534] Option 1 with one separate RACH configuration

[0535] Alt 1: The SBFD-aware UE reinterprets PRACH power control parameter values ​​based on specific rules.

[0536] For example, one explicit parameter and one implicit parameter can be received. As a result, two values ​​exist.

[0537] For example, even if a single preambleReceivedTargetPower value is given, each value is applied through reinterpretation, so the preambleReceivedTargetPower value can be used according to each transmission symbol type when sending Msg3 PUSCH.

[0538] Alt 2: How to use a single PRACH power control parameter value.

[0539] This is a method of using a single PRACH power control parameter in common for both SBFD and non-SBFD systems.

[0540] Option 2 with two separate RACH configurations

[0541] In this Option 2, since two PRACH power setting parameters are set, the preambleReceivedTargetPower value can be used according to each transmission symbol type when transmitting Msg3 PUSCH.

[0542] <Msg3를 위한 receivedPreambleTargetPower와 deltaPreamble의 조정 방법>

[0543] By synthesizing the above cases and considerations, a method for changing the receivedPreambleTargetPower to be used for Msg1 and Msg3 can be devised based on the case where Msg1 is transmitted in the RO of a non-SBFD symbol and Msg3 PUSCH is transmitted in a non-SBFD symbol. Among the power control parameters of Msg3, the elements related to Msg1 are as follows.

[0544] [Equation 3]

[0545]

[0546] At this time, P O_PRE is provided by preambleReceivedTargetPower, and Δ PREAMBLE,Msg3 is provided by Msg3-DeltaPreamble or deltaPreamble.

[0547] Method 1. A method that uses the preambleReceivedTargetPower given in Msg3 as is, without additional parameters.

[0548] In this method, the preambleReceivedTargetPower given in Msg3 is used as is without additional parameters. However, there are two possibilities. The first method is for the terminal to expect the base station to provide a preambleReceivedTargetPower for each slot type (e.g., SBFD and HD, respectively), and to use the preambleReceivedTargetPower provided for Msg1 for the purpose of Msg3 transmission, which is the same as the type used for Msg3 transmission.

[0549] The second method is a method in which the terminal uses the preambleReceivedTargetPower of Msg1 as is in the transmission of Msg3, regardless of the slot type of Msg3, even if the base station has indicated the preambleReceivedTargetPower for each slot type (e.g., SBFD and HD, respectively).

[0550] In cases where the terminal uses the preambleReceivedTargetPower instructed by the base station as is without reinterpretation, as with the two methods mentioned above, there is no room for change regarding preamble_received_target_power, so the other parameter, Δ PREAMBLE,Msg3 You can pay attention to this.

[0551] Δ PREAMBLE,Msg3It can be adjusted within the range [-2, 0, ..., 12] by Msg3-DeltaPreamble or deltaPreamble. If this range is insufficient, a new range can be defined.

[0552] One advantage of Method 1 is that the power of Msg3 can be controlled using only currently available parameters without defining additional parameters.

[0553] Method 2. P through additional parameters O_PRE Adjusts.

[0554] In Method 2, P through additional parameters O_PRE Adjustments are performed. There are two possibilities regarding the terminal's use of preambleReceivedTargetPower. The first method is for the terminal to expect the base station to specify the respective preambleReceivedTargetPower for each slot type (e.g., SBFD and HD, respectively), and to use the preambleReceivedTargetPower specified for Msg1 for the purpose of Msg3 transmission, identical to the type used for Msg3 transmission. The second method is for the terminal to use the preambleReceivedTargetPower of Msg1 for Msg3 transmission as is, regardless of the slot type of Msg3, even if the base station has specified the respective preambleReceivedTargetPower for each slot type (e.g., SBFD and HD, respectively). Specifically, Method 2 involves P through the new parameter 'delta_type 1'. O_PRE The value of can be adjusted. The above delta_type 1 can be specified when the upper-level parameter preambleReceivedTargetPower is specified, or through upper-level signaling together with msg3-DeltaPreamble or deltaPreamble. The specific application method is as follows.

[0555] [Equation 4]

[0556]

[0557] If upper-layer signaling is not available, it operates using only the pre-defined preamble_received_target_power. The advantage of this method is that the power of Msg3 can be adjusted simply without modifying other parameters.

[0558] Method 3: Δ through additional parameters PREAMBLE,Msg3 Implement adjustments.

[0559] In this method, Δ through additional parameters PREAMBLE,Msg3 Adjustments are made. There are two possibilities regarding the terminal's use of preambleReceivedTargetPower. The first method is for the terminal to expect the base station to specify the respective preambleReceivedTargetPower for each slot type (e.g., SBFD and HD, respectively), and to use the preambleReceivedTargetPower specified for Msg1 for the purpose of Msg3 transmission, identical to the type used for Msg3 transmission. The second method is for the terminal to use the preambleReceivedTargetPower of Msg1 for Msg3 transmission as is, regardless of the slot type of Msg3, even if the base station has specified the respective preambleReceivedTargetPower for each slot type (e.g., SBFD and HD, respectively).

[0560] Specifically, Method 3 uses Δ through the new parameter 'delta_type 2'. PREAMBLE,Msg3The value of can be adjusted. The above delta_type 2 can be specified when the upper-level parameter preambleReceivedTargetPower is specified, or through upper-level signaling together with msg3-DeltaPreamble or deltaPreamble. The specific application method is as follows.

[0561] [Equation 5]

[0562]

[0563] The transmission power difference between msg 3 and PRACH can be adjusted according to the position of msg 3 using delta_preamble + delta_type 2. In this case, delta_type 2 can be Delta preamble-19. For example, Delta preamble-19 can have the following range: [-6, ... -2] × m (e.g., m = 2).

[0564] If upper-layer signaling is not available, it operates using only the pre-defined preamble_received_target_power. The advantage of this method is that the power of Msg3 can be adjusted simply without modifying other parameters.

[0565] Method 4: Each P O_PRE wa Δ PREAMBLE,Msg3 This is a method to maintain the value and execute msg 3 power control through additional parameters.

[0566] In this Method 4, through the new parameter 'delta_type 3', P O_NOMINAL,PUSCH,f,cThe value of (0) can be adjusted. There are two possibilities regarding the terminal's use of preambleReceivedTargetPower. The first method is for the terminal to expect the base station to specify the preambleReceivedTargetPower for each slot type (e.g., SBFD and HD, respectively), and to use the preambleReceivedTargetPower specified for Msg1 for the purpose of Msg3 transmission, which is the same as the type in Msg3 transmission. The second method is for the terminal to use the preambleReceivedTargetPower of Msg1 for Msg3 transmission as is, regardless of the slot type of Msg3, even if the base station specifies the preambleReceivedTargetPower for each slot type (e.g., SBFD and HD, respectively).

[0567] In Method 4, the above delta_type 3 may be indicated when the upper-level parameter preambleReceivedTargetPower is specified, or through upper-level signaling together with msg3-DeltaPreamble or deltaPreamble. The specific application method is as follows.

[0568] [Equation 6]

[0569]

[0570] <Tuning Method of deltaPreamble Considering Existing RRC Parameters and RACH Process>

[0571] As described above, as SBFD or other functions may be applied, additional RACH-Config or function combinations may be defined during the RACH process. In this case, since Msg3-DeltaPreamble or DeltaPreamble, which determines the power of msg3 PUSCH, is included in each IE, the terminal can adjust the power of msg3 PUSCH according to each function or other functions.

[0572] The biggest reason (necessity) for including additional parameters is that RACH-ConfigCommon is cell-specific information. The base station must provide information that can cover all supported terminals and must provide deltaPreamble for all cases for the terminals. Since there will be various cases within the base station (e.g., different operation cases depending on whether SBFD operation is performed in the msg1 and msg3 transmissions, respectively), if there are terminals that operated with SBFD during the msg3 transmission, the deltaPreamble value will differ depending on whether they operated with SBFD or non-SBFD during the msg1 transmission, and the base station must be able to cover these cases through a single RRC transmission containing cell-common information.

[0573] Additionally, if the base station allows the terminal to select the transmission type of msg3 (e.g., SBFD) via RAR (Random Access Response), the base station may need to transmit a deltaPreamble for each case because it does not know which type the terminal will transmit.

[0574] In this disclosure, SBFD is used as an example of a feature to explain how DeltaPreamble can be overridden according to the supported features of the terminal.

[0575] Although SBFD was cited as an example of the function, it can be extended to NES (network energy saving), SSFD, and full-duplex SBFD of the terminal. Furthermore, SBFD operation can be divided into i) cases where it is configured as a separate function from half-duplex operation and ii) cases where it is not configured as a separate function; this paper explains how to configure and operate the Msg3 transmission power-related parameters in each case.

[0576] When considering the transmission type for msg1 from the perspective of an SBFD-aware terminal, an SBFD operation or a non-SBFD operation can be performed through the measurement of RSRP (Reference Signal Received Power). At this time, the decision of the operation, such as the determination of the msg1 repetition number, can be made together with the decision of the function ( / RA resource). Therefore, from the perspective of the terminal, it may be necessary to decide whether to perform an SBFD operation or a non-SBFD operation (hereinafter, this may also be referred to as RO type selection) before or simultaneously with the decision of the function.

[0577] If the RO type selection is made prior to the function determination, the SBFD may not be set as a separate function. On the other hand, if the RO type selection is made together with the function determination, the SBFD may be set as a separate function. Considering these two cases (i.e., whether the SBFD is set as a separate function or not), the method of indicating the deltaPreamble is considered based on whether the SBFD operation is performed in each of the msg1 and msg3 transmissions. In addition, the method of indicating the deltaPreamble is considered based on the method of setting the SBFD RACH (e.g., Option 1: using a single RACH setting (legacy RACH setting), Option 2: using a separated RACH setting (using two separate RACH settings, such as a legacy RACH setting and an additional RACH setting)). In the following, the above Option 1 may be described as receiving / applying a single RACH setting or operating based on a single RACH setting, and the above Option 2 may be described as receiving / applying an individual RACH setting or operating based on an individual RACH setting.

[0578] Below, considering i) whether SBFD is configured as a separate function and ii) the RACH configuration method (using Option 1 or Option 2), the method of setting / instructing / applying parameters related to Msg3 transmission power is explained for each of the four cases.

[0579] The following methods may be included as sub-methods of Method 3 of the adjustment method of receivedPreambleTargetPower and deltaPreamble for Msg3.

[0580] 1. Method for configuring / applying deltaPreamble when SBFD is configured as a separate function from half-duplex operation and the terminal operates with a single RACH configuration (Option 1).

[0581] If SBFD is configured as a separate function, it can be configured relatively simply.

[0582] i) The featureCombinationPreambles IE cannot be applied to existing terminals (e.g., terminals of NR Rel-15, 16). Therefore, existing terminals can use the value of the Msg3-DeltaPreamble of the existing PUSCH-ConfigCommon IE for the deltaPreamble of the msg3 power control.

[0583] ii) For terminals in Rel-17, 18, Rel-19 and thereafter (e.g., Rel-20) that are non-aware of SBFD, or terminals that are aware of SBFD but do not perform SBFD operations in msg1 / 3 transmission (in both msg1 and msg3 transmissions, hereinafter the same), said terminals will not select the SBFD function in function selection because they do not support SBFD operations. In this case, for any function other than the SBFD function, the terminal may use the DeltaPreamble value of the featureCombinationPreambles IE of the corresponding function for msg3 power control.

[0584] iii) Among the SBFD-aware terminals of Rel-19 and thereafter (e.g., Rel-20), for terminals that perform SBFD operations in msg1 / 3 transmission, the terminals can select the SBFD function in function selection because they support SBFD operations. In this case, in the SBFD function, the terminal can use the DeltaPreamble value of the featureCombinationPreambles IE of the corresponding function for msg3 power control.

[0585] iv) Among Rel-19 and later SBFD-aware terminals, for terminals that perform SBFD operations in msg1 transmission but do not perform SBFD operations in msg3 transmission, said terminals can select the SBFD function in function selection because said terminals support SBFD operations. In this case, for the SBFD function, the terminal must refer to the DeltaPreamble value of the featureCombinationPreambles IE of the corresponding function. However, since said parameter is a DeltaPreamble for terminals that perform SBFD operations in both msg1 and msg3 transmissions, a new DeltaPreamble (e.g., this new DeltaPreamble may be called DeltaPreamble2) may be defined and instructed to said terminal for a terminal that performs SBFD operations in msg1 transmission but does not perform SBFD operations in msg3 transmission.

[0586] v) Among the SBFD-aware terminals of Rel-19 and thereafter, for terminals that perform non-SBFD operations in msg1 transmission but SBFD operations in msg3 transmission, the terminals may select the non-SBFD function in function selection because they support non-SBFD operations in msg1 transmission. In this case, for the non-SBFD function, the terminal must refer to the DeltaPreamble value of the featureCombinationPreambles IE of the corresponding function. However, since the parameter is a DeltaPreamble for the Rel-17 and 18 terminals and the SBFD-non-aware terminals of Rel-19 and thereafter, or for terminals that are SBFD-aware but do not perform SBFD operations in msg1 / 3 transmission, a new DeltaPreamble (e.g., DeltaPreamble2) may be defined and instructed to the terminal for a terminal that performs non-SBFD operations in msg1 transmission and SBFD operations in msg3 transmission.

[0587] FIG. 17 shows an example in which SBFD is configured as a separate feature from half-duplex operation, and deltaPreamble is configured for the case where the terminal receives a single RACH configuration (Option 1).

[0588] Referring to FIG. 17, the FeatureCombinationPreambleList may include a FeatureCombinationPreamble for non-SBFD functions and a FeatureCombinationPreamble for SBFD functions, and each FeatureCombinationPreamble may include a DeltaPreamble for Msg3 transmission by non-SBFD operation and a DeltaPreamble2 for Msg3 transmission by SBFD operation. In summary, a DeltaPreamble needs to be defined only when a msg3 of a different type from the function is defined for a given function. Therefore, only one additional DeltaPreamble parameter (DeltaPreamble2) needs to be defined.

[0589] However, if non-SBFD operation is performed during msg1 transmission but SBFD operation is performed during msg3 transmission, the base station needs to make an additional determination as to whether the terminal is SBFD or a terminal, and the terminal must provide information to the base station for the determination. To reduce the complexity of the operation, if the operation is not supported, it can operate as shown in FIG. 18.

[0590] FIG. 18 shows another example in which the SBFD is configured as a separate feature from the half-duplex operation, and the terminal receives a single RACH configuration (Option 1) and the deltaPreamble is configured.

[0591] Referring to FIG. 18, the FeatureCombinationPreambleList may include a FeatureCombinationPreamble for non-SBFD functions and a FeatureCombinationPreamble for SBFD functions. In this case, the FeatureCombinationPreamble for non-SBFD functions includes only a DeltaPreamble for Msg3 transmission by non-SBFD operation. On the other hand, the FeatureCombinationPreamble for SBFD functions may include a DeltaPreamble for Msg3 transmission by non-SBFD operation and a DeltaPreamble2 for Msg3 transmission by SBFD operation.

[0592] The DeltaPreamble2 parameter can be interpreted as an additional parameter that indicates when the operation type of the msg1 and msg3 transmissions differs (e.g., the msg1 transmission is performed on a non-SBFD resource and the msg3 transmission is performed on an SBFD resource). Therefore, when defining deltaPreamble2, instead of classifying based on the resource type (e.g., whether the msg3 transmission resource is a non-SBFD resource or an SBFD resource), it may be defined as a parameter that indicates when the operation type changes between the msg1 and msg3 transmissions.

[0593] 2. Method for configuring / applying deltaPreamble when SBFD is configured as a separate function from half-duplex operation and the terminal operates with a separate RACH configuration (Option 2).

[0594] When SBFD operates with a separate RACH configuration, it can be configured relatively simply. When operating with a separate RACH configuration, since the RACH configuration for SBFD is newly defined, Additional-RACH-Config IE can be newly defined for SBFD operation. When reusing reusable parameters without newly defining the RACH configuration itself and only instructing for essential additional parameters, it can operate as in the first operation above (in other words, the method of applying deltaPreamble for the case where SBFD is configured as a separate function from half-duplex operation and the terminal operates with a single RACH configuration).

[0595] i) Since featureCombinationPreambles IE and Additional RACH-Config IE cannot be applied to existing Rel-15 and 16 terminals, Rel-15 and 16 terminals can use the value of Msg3-DeltaPreamble of the existing PUSCH-ConfigCommon IE for the deltaPreamble of msg3 power control.

[0596] ii) For Rel-17, 18 terminals and Rel-19 and thereafter non-SBFD cognitive terminals, or SBFD cognitive terminals that do not perform SBFD operations in msg1 / 3 transmission, the terminals will naturally not select the SBFD function in function selection because they do not support SBFD operations. In this case, the terminal may use the DeltaPreamble value of the featureCombinationPreambles IE of the RACH-ConfigCommon IE (or another Additional RACH-Config IE) where the function exists in a non-SBFD specific RACH-ConfigCommon and any function other than the SBFD function for msg3 power control.

[0597] iii) Among Rel-19 and later SBFD-aware terminals, for terminals that perform SBFD operations in each of the msg1 / 3 transmissions, since the terminals support SBFD operations, they may select an SBFD function within an additional RACH-Config IE (or a RACH-Config) where an SBFD function exists in the function selection. In this case, the terminal may use the DeltaPreamble value of the featureCombinationPreambles IE of the corresponding function in the SBFD-specific RACH-ConfigCommon and SBFD function for msg3 power control.

[0598] iv) Among Rel-19 and later SBFD-aware terminals, for terminals that perform SBFD operations in msg1 transmission but do not perform SBFD operations in msg3 transmission, since said terminals support SBFD operations, they may select an SBFD function within an additional RACH-Config IE where an SBFD function exists in the function selection. In this case, the terminal must refer to the DeltaPreamble value of the featureCombinationPreambles IE of the SBFD-specific RACH-ConfigCommon and the corresponding function in the SBFD function. However, since said parameter is a DeltaPreamble for terminals that perform SBFD operations in both msg1 and msg3, a new DeltaPreamble (e.g., DeltaPreamble2) may be defined and instructed to the terminal for a terminal that performs SBFD operations in msg1 transmission but does not perform SBFD operations in msg3 transmission.

[0599] v) Among the SBFD-aware terminals of Rel-19 and thereafter, for terminals that operate non-SBFD in msg1 transmission but SBFD in msg3 transmission, the terminals may select the non-SBFD function in function selection because they support non-SBFD operation in msg1 transmission. In this case, the terminal must refer to the DeltaPreamble value of the featureCombinationPreambles IE within the additional RACH-Config IE where the corresponding function exists in the non-SBFD specific RACH-ConfigCommon and the non-SBFD function. However, since the parameter is a DeltaPreamble for the Rel-17, 18 terminals and the SBFD-non-aware terminals of Rel-19 and thereafter, or for terminals that are SBFD-aware but do not operate SBFD in msg1 / 3 transmission, a new DeltaPreamble (e.g., DeltaPreamble2) may be defined and instructed to the terminal for a terminal that operates non-SBFD in msg1 transmission and SBFD in msg3 transmission.

[0600] FIG. 19 illustrates a method for setting / applying deltaPreamble when SBFD is set as a separate function from half-duplex operation and the terminal operates with a separate RACH setting (Option 2).

[0601] Referring to FIG. 19, BWPUplinkCommon may include RACHConfigCommon (which may be referred to as legacy RACH config) and Additional RACH-ConfigList (which may be referred to as additional RACH config). The FeatureCombinationPreambles included in the RACHConfigCommon and Additional RACH-ConfigList may include a DeltaPreamble for Msg3 transmission by non-SBFD operation and a DeltaPreamble2 for Msg3 transmission by SBFD operation. Since DeltaPreamble only needs to be defined for each function when a different type of msg3 is defined for that function, only one additional DeltaPreamble parameter (DeltaPreamble2) needs to be defined.

[0602] However, if non-SBFD operation is performed during msg1 transmission but SBFD operation is performed during msg3 transmission, the base station needs to make an additional determination as to whether the terminal is SBFD or a terminal, and the terminal must provide information to the base station for the determination. To reduce the complexity of the operation or if the operation is not supported, it may operate as shown in FIG. 20.

[0603] FIG. 20 illustrates another method of setting / applying deltaPreamble for a case where SBFD is set as a separate function from half-duplex operation and the terminal operates with a separate RACH setting (Option 2).

[0604] Referring to FIG. 20, BWPUplinkCommon may include RACHConfigCommon (which may be referred to as legacy RACH config) and Additional RACH-ConfigList (which may be referred to as additional RACH config). FeatureCombinationPreambles included in RACHConfigCommon may include a DeltaPreamble for Msg3 transmission by non-SBFD operation, and FeatureCombinationPreambles included in Additional RACH-ConfigList may include a DeltaPreamble for Msg3 transmission by non-SBFD operation and a DeltaPreamble2 for Msg3 transmission by SBFD operation.

[0605] In this case, the DeltaPreamble2 parameter can be interpreted as an additional parameter specified as the operation type differs between the msg1 and msg3 transmissions. Therefore, when defining deltaPreamble2, instead of classifying it according to each resource type, it can be defined as a parameter that specifies the case where the operation types of the msg1 and msg3 transmissions are swapped.

[0606] 3. Method for configuring / applying deltaPreamble when SBFD is not configured as a separate function from half-duplex operation and the terminal operates with a single RACH configuration (Option 1).

[0607] If SBFD is not configured as a separate function, it can be configured as follows.

[0608] i) Since featureCombinationPreambles IE cannot be applied to existing Rel-15 and 16 terminals, Rel-15 and 16 terminals can use the value of Msg3-DeltaPreamble of the existing PUSCH-ConfigCommon IE for the deltaPreamble of msg3 power control.

[0609] ii) For Rel-17, 18 terminals and Rel-19 and later non-SBFD cognitive terminals, or SBFD cognitive terminals that do not perform SBFD operations in msg1 / 3 transmission, since SBFD operations are not classified as separate functions, SBFD operations and non-SBFD operations are not distinguished in function selection, and each terminal will select a corresponding function. In this case, the terminal may use the DeltaPreamble value of the featureCombinationPreambles IE of the corresponding function for msg3 power control.

[0610] iii) Among the SBFD-aware terminals of Rel-19 and thereafter, for terminals that operate SBFD in each of the msg1 / 3 transmissions, since SBFD operation is not classified as a separate function, SBFD operation and non-SBFD operation are not distinguished in function selection, and each terminal will select a corresponding function. In this case, the terminal may use the DeltaPreamble value of the featureCombinationPreambles IE of the corresponding function for msg3 transmission power control. However, since this value must be a separate value from the DeltaPreamble value selected by the Rel-17, 18 terminals and the SBFD-non-aware terminals of Rel-19 and thereafter, or by the SBFD-aware terminals that do not operate SBFD in msg1 / 3 transmissions, a new DeltaPreamble (e.g., DeltaPreamble2) may need to be defined.

[0611] iv) Among the SBFD-aware terminals of Rel-19 and thereafter, for terminals that perform SBFD operations in msg1 transmission but not in msg3 transmission, since SBFD operations are not classified as separate functions, SBFD operations and non-SBFD operations are not distinguished in function selection, and each terminal will select a corresponding function. In this case, the terminal must refer to the DeltaPreamble value of the featureCombinationPreambles IE of the corresponding function. However, since the parameter values ​​are DeltaPreambles for the terminals of Rel-17 and 18 and the non-SBFD-aware terminals of Rel-19 and thereafter, or terminals that are SBFD-aware but do not perform SBFD operations in msg1 / 3 transmission, or terminals that perform SBFD operations in both msg1 / 3, a new DeltaPreamble (e.g., DeltaPreamble3) may need to be defined and instructed to the terminal for a terminal that performs SBFD operations in msg1 transmission but not in msg3 transmission.

[0612] v) Among the SBFD-aware terminals of Rel-19 and thereafter, for terminals that perform non-SBFD operation in msg1 transmission but SBFD operation in msg3 transmission, since SBFD operation is not classified as a separate function, SBFD operation and non-SBFD operation are not distinguished in function selection, and each terminal will select the corresponding function. In this case, the terminal must refer to the DeltaPreamble value of the featureCombinationPreambles IE of the corresponding function. However, the parameter is a DeltaPreamble for the Rel-17 and 18 terminals and the Rel-19 and thereafter non-SBFD-aware terminals, or SBFD-aware terminals but terminals that do not perform SBFD operation in msg1 / 3 transmissions, or terminals that perform SBFD operation in both msg1 / 3, or terminals that perform SBFD operation in msg1 transmission but do not perform SBFD operation in msg3 transmission. Therefore, for a terminal that operates non-SBFD in msg1 transmission but operates SBFD in msg3 transmission, a new DeltaPreamble (e.g., DeltaPreamble4) may be defined and instructed to the terminal.

[0613] FIG. 21 illustrates a method for setting / applying deltaPreamble when SBFD is not set as a separate function from half-duplex operation and the terminal receives a single RACH setting (Option 1).

[0614] Referring to FIG. 21, FeatureCombinationPreambles included in RACHConfigCommon may include i) DeltaPreamble for a terminal that performs non-SBFD operation in msg1 transmission and non-SBFD operation in msg3 transmission, ii) DeltaPreamble2 for a terminal that performs SBFD operation in msg1 transmission and SBFD operation in msg3 transmission, iii) DeltaPreamble3 for a terminal that performs SBFD operation in msg1 transmission and non-SBFD operation in msg3 transmission, and iv) DeltaPreamble4 for a terminal that performs non-SBFD operation in msg1 transmission and SBFD operation in msg3 transmission.

[0615] In other words, since DeltaPreamble must be defined for each operation type of msg1 transmission and msg3 transmission, a total of three additional DeltaPreamble parameters (DeltaPreamble2, DeltaPreamble3, DeltaPreamble4) need to be defined in addition to DeltaPreamble.

[0616] However, if non-SBFD operation is performed during msg1 transmission but SBFD operation is performed during msg3 transmission, the base station needs to make an additional determination as to whether the terminal is SBFD or a terminal, and the terminal must provide information to the base station for the determination. To reduce the complexity of the operation or if such operation is not supported, it may operate as shown in FIG. 22.

[0617] FIG. 22 illustrates a different method of setting deltaPreamble when SBFD is not set as a separate function from half-duplex operation and the terminal receives a single RACH setting (Option 1).

[0618] Referring to FIG. 22, FeatureCombinationPreambles included in RACHConfigCommon may include i) DeltaPreamble for a terminal that performs non-SBFD operation in msg1 transmission and non-SBFD operation in msg3 transmission, ii) DeltaPreamble2 for a terminal that performs SBFD operation in msg1 transmission and SBFD operation in msg3 transmission, and iii) DeltaPreamble3 for a terminal that performs SBFD operation in msg1 transmission and non-SBFD operation in msg3 transmission.

[0619] According to the embodiment, the DeltaPreamble2 parameter may be interpreted as an additional parameter that is indicated as the operation types of msg1 and msg3 differ. Since it is expected that the preambleReceivedTargetPower parameter of msg1 will be indicated for each operation type, the classification of deltaPreamble may be used by distinguishing between the same or different operation types for msg1 and msg3 to reduce the complexity of the operation. For example, the existing DeltaPreamble may be used when both msg1 and msg3 perform SBFD operations or when both msg1 and msg3 perform non-SBFD operations. However, when msg1 performs SBFD operations and msg3 performs non-SBFD operations, or when msg1 performs non-SBFD operations and msg3 performs SBFD operations, the newly defined parameter DeltaPreamble2 may be used. Therefore, when defining deltaPreamble2, instead of classifying based on each resource type, it can be defined as a parameter that indicates when the operation types of msg1 and msg3 are changed.

[0620] FIG. 23 illustrates another method of setting / applying deltaPreamble when SBFD is not set as a separate function from half-duplex operation and the terminal receives a single RACH setting (Option 1).

[0621] Referring to FIG. 23, FeatureCombinationPreambles included in RACHConfigCommon may include i) DeltaPreamble for cases where the same resource type is used in the msg1 transmission and msg3 transmission, and ii) DeltaPreamble2 for cases where different resource types are used in the msg1 transmission and msg3 transmission.

[0622] Specifically, if SBFD operation is performed in the msg1 transmission and non-SBFD operation is performed in the msg3 transmission, or if non-SBFD operation is performed in the msg1 transmission and SBFD operation is performed in the msg3 transmission, the newly defined parameter DeltaPreamble2 can be used. Therefore, when defining deltaPreamble2, instead of classifying it according to each resource type, it can be defined as a parameter that indicates when the operation type changes between the msg1 and msg3 transmissions.

[0623] 4. Method for configuring / applying deltaPreamble when SBFD is not configured as a separate function from half-duplex operation and the terminal operates with individual RACH configuration (Option 2).

[0624] If SBFD is not configured as a separate function, it can be configured as follows, for example.

[0625] When operating with individual RACH settings, a new RACH setting can be defined for SBFD operation. Accordingly, Additional-RACH-Config IE can be newly defined for SBFD operation. If the RACH setting itself is not newly defined but reusable parameters are reused and only the essential additional parameters are instructed, it can operate as in the third operation (method of applying deltaPreamble for the case where SBFD is not set as a separate function from half-duplex operation and the terminal operates with a single RACH setting).

[0626] i) Since featureCombinationPreambles IE and Additional RACH-Config IE cannot be applied to existing Rel-15 and 16 terminals, Rel-15 and 16 terminals can use the value of Msg3-DeltaPreamble of the existing PUSCH-ConfigCommon IE for the deltaPreamble of msg3 power control.

[0627] ii) For Rel-17, 18 terminals and Rel-19 and thereafter SBFD non-cognitive terminals, or SBFD-cognitive terminals that do not perform SBFD operations in msg1 / 3 transmissions, since SBFD operations are not classified as separate functions, SBFD operations and non-SBFD operations are not distinguished in function selection, and each terminal will select a corresponding function. In this case, the terminal may use the DeltaPreamble value of the featureCombinationPreambles IE of the RACH-ConfigCommon IE (or another Additional RACH-Config IE) where the corresponding function exists in the non-SBFD specific RACH-ConfigCommon and the corresponding function for msg3 power control.

[0628] iii) Among Rel-19 and later SBFD-aware terminals, for terminals performing SBFD operations in msg1 / 3 transmission, since SBFD operations are not classified as separate functions, SBFD operations and non-SBFD operations are not distinguished in function selection, and each terminal will select a corresponding function. In this case, the terminal can use the DeltaPreamble value of the featureCombinationPreambles IE of the corresponding function in the SBFD-specific RACH-ConfigCommon and the corresponding function for msg3 power control.

[0629] iv) Among Rel-19 and later SBFD-aware terminals, for terminals that perform SBFD operations in msg1 transmission but not in msg3 transmission, since SBFD operations are not classified as separate functions, SBFD operations and non-SBFD operations are not distinguished, and each terminal will select a corresponding function. In this case, the terminal must refer to the DeltaPreamble value of the featureCombinationPreambles IE of the corresponding function in the SBFD-specific RACH-ConfigCommon and the corresponding function. However, since the parameter is a DeltaPreamble for terminals that perform SBFD operations in both msg1 and msg3, for terminals that perform SBFD operations in msg1 transmission but not in msg3 transmission, a new DeltaPreamble (e.g., DeltaPreamble2) may need to be defined and instructed to the terminal.

[0630] v) Among Rel-19 and later SBFD-aware terminals, for terminals that operate non-SBFD in msg1 transmission but SBFD in msg3 transmission, since SBFD operation is not classified as a separate function, the same function will be selected without distinguishing between SBFD operation and non-SBFD operation in function selection. In this case, the terminal will need to refer to the DeltaPreamble value of the featureCombinationPreambles IE within the additional RACH-Config IE existing in the corresponding function, and the non-SBFD specific RACH-ConfigCommon. However, since the parameter is a DeltaPreamble for the Rel-17, 18 terminals and Rel-19 and thereafter terminals that are not aware of SBFD or terminals that are aware of SBFD but do not perform SBFD operations in msg1 / 3 transmission, for terminals that perform non-SBFD operations in msg1 transmission and SBFD operations in msg3 transmission, a new DeltaPreamble (e.g., DeltaPreamble2) may be defined and instructed to the terminal.

[0631] The diagram for deltaPreamble in the aforementioned cases is shown in Fig. 24.

[0632] FIG. 24 illustrates a method for setting / applying deltaPreamble when SBFD is not set as a separate function from half-duplex operation and the terminal receives individual RACH settings (Option 2).

[0633] Referring to FIG. 24, BWPUplinkCommon may include RACHConfigCommon (which can be referred to as legacy RACH config) and Additional RACH-ConfigList (which can be referred to as additional RACH config). The FeatureCombinationPreambles included in the RACHConfigCommon include i) a DeltaPreamble for Msg3 transmission by non-SBFD operation and ii) a DeltaPreamble2 for Msg3 transmission by SBFD operation. The FeatureCombinationPreambles included in the Additional RACH-ConfigList include i) a DeltaPreamble for Msg3 transmission by SBFD operation and ii) a DeltaPreamble2 for Msg3 transmission by non-SBFD operation.

[0634] Since DeltaPreamble only needs to be defined for cases where a msg3 of a different type from the above function is defined for a function, only one additional DeltaPreamble parameter (DeltaPreamble2) needs to be defined.

[0635] However, if non-SBFD operation is performed during msg1 transmission but SBFD operation is performed during msg3 transmission, the base station needs to make an additional determination as to whether the terminal is SBFD or a terminal, and the terminal must provide information to the base station for the determination. To reduce the complexity of the operation or if such operation is not supported, the operation may be performed as shown in FIG. 25.

[0636] FIG. 25 illustrates a different method of setting / applying deltaPreamble when SBFD is not set as a separate function from half-duplex operation and the terminal receives individual RACH settings (Option 2).

[0637] Referring to FIG. 25, BWPUplinkCommon may include RACHConfigCommon (which may be referred to as legacy RACH config) and Additional RACH-ConfigList (which may be referred to as additional RACH config). The FeatureCombinationPreambles included in the RACHConfigCommon include a DeltaPreamble for Msg3 transmission by non-SBFD operation. The FeatureCombinationPreambles included in the Additional RACH-ConfigList include i) a DeltaPreamble for Msg3 transmission by SBFD operation, and ii) a DeltaPreamble2 for Msg3 transmission by non-SBFD operation.

[0638] For example, the parameters defined in RACH-ConfigCommon are as in FIG. 25, but since DeltaPreamble can be defined as optional, there may be no structural difference between RACH-ConfigCommon in SBFD operation and non-SBFD operation. Table 15 illustrates FeatureCombinationPreambles IE including DeltaPreamble2.

[0639] [Table 15]

[0640]

[0641] In Table 15, the DeltaPreamble2 parameter can be interpreted as an additional parameter that specifies when the operation types of msg1 and msg3 change. Therefore, when defining deltaPreamble2, instead of classifying it according to each resource type, it can be defined as a parameter that specifies when the operation types of msg1 and msg3 change.

[0642] 5. Method for setting / applying deltaPreamble for cases that can be commonly applied for convenience and simplification of operation.

[0643] In the application methods of deltaPreamble in the aforementioned methods 1 to 4, a condition arises that feature combination must be considered. However, since there is a parameter msg3-deltaPreamble that can be applied universally, there is also a method to apply deltaPreamble universally without considering all of the above situations.

[0644] This method is broadly divided into two types: i) a first method in which msg3-deltaPreambles are independently defined for terminals in Rel-17 and 18, terminals in Rel-19 and thereafter that are SBFD non-aware, terminals that are SBFD aware but do not perform SBFD operations during msg1 / 3 transmission, terminals that perform SBFD operations during msg1 / 3 transmission, terminals that perform SBFD operations during msg1 transmission but not during msg3 transmission, and terminals that perform non-SBFD operations during msg1 transmission but perform SBFD operations during msg3 transmission; and ii) a second method in which different msg3-deltaPreambles are applied depending on whether the types of operations in msg1 transmission and msg3 transmission are the same or different. Each method is explained with reference to Figures 26 and 27.

[0645] FIG. 26 illustrates a first method for defining independent parameters for each operation case of msg1 transmission and msg3 transmission.

[0646] Referring to FIG. 26, for each of the following cases of terminals, the msg3-DeltaPreamble can be directed: 1) terminals in Rel-17 and 18 and Rel-19 and thereafter that are non-SBFD conscious terminals or terminals that are SBFD conscious but do not perform SBFD operations in msg1 / 3 transmission; 2) terminals that perform SBFD operations in msg1 / 3 transmission; 3) terminals that perform SBFD operations in msg1 transmission but do not perform SBFD operations in msg3 transmission; and 4) terminals that perform non-SBFD operations in msg1 transmission but perform SBFD operations in msg3 transmission. In other words, the corresponding msg3-DeltaPreamble can be independently set / directed for each of the above four cases. For example, corresponding parameters may be specified for each case, such as msg3-DeltaPreamble (non-SBFD operation in msg1 transmission and non-SBFD operation in msg3 transmission), msg3-DeltaPreamble2 (SBFD operation in msg1 transmission and SBFD operation in msg3 transmission), msg3-DeltaPreamble3 (SBFD operation in msg1 transmission and non-SBFD operation in msg3 transmission), and msg3-DeltaPreamble4 (non-SBFD operation in msg1 transmission and SBFD operation in msg3 transmission). Based on cell-common ( / cell-specific) information, the terminal can control msg3 power by selecting one of the four parameters according to the way each terminal operates.

[0647] FIG. 27 illustrates a second method of applying different msg3-deltaPreambles for cases where the types of each operation are the same or different in the msg1 transmission and msg3 transmission operations.

[0648] Referring to Fig. 27, in the second method, for the simplification of instructions, detailed power control adjusts the msg3 power through preambleReceivedTargerPower, and for deltaPreamble, Msg3-DeltaPreamble is applied respectively depending on whether the operation methods of msg1 and msg3 are switching (in other words, whether the types of operation are different when msg1 and msg3 are operated). The terminal uses the Msg3-DeltaPreamble for msg3 power control based on pre-instructed parameter information when the type of the operation method of msg3 is the same or different from the operation method of msg1.

[0649] For example, a terminal that performs i) non-SBFD operation in msg1 transmission and non-SBFD operation in msg3 transmission, or ii) SBFD operation in msg1 transmission and SBFD operation in msg3 transmission, uses Msg3-DeltaPreamble, and a terminal that performs i) SBFD operation in msg1 transmission and non-SBFD operation in msg3 transmission, or ii) non-SBFD operation in msg1 transmission and SBFD operation in msg3 transmission, can control msg3 transmission power using Msg3-DeltaPreamble2.

[0650] The aforementioned first method has the advantage of allowing detailed control for each situation, while the present second method has the advantage of being easy to instruct (reducing signaling overhead).

[0651] FIG. 28 illustrates a method of operation of a terminal according to one embodiment of the present disclosure.

[0652] Referring to FIG. 28, the terminal receives random access channel (RACH) setting information from a base station including a first power offset and a second power offset, wherein each of the first power offset and the second power offset relates to the power offset between the transmission of message 3 (Msg3) and message 1 (Msg1) of the random access process (S281).

[0653] Here, the transmission of Msg1 may refer to a RACH preamble transmission. In response to the transmission of Msg1, the terminal may receive a random access response (Msg2) from the base station (network). The terminal may transmit Msg3 using the scheduled uplink grant of the random access response. In other words, the transmission of Msg3 may refer to a scheduled transmission transmitted through a physical uplink shared channel. In this sense, the transmission of Msg3 may be the first scheduled transmission of the terminal's random access process.

[0654] For example, the first power offset (e.g., the aforementioned DeltaPreamble or msg3-DeltaPreamble) and the second power offset (e.g., the aforementioned DeltaPreamble2 or msg3-DeltaPreamble2) can each be described as a power offset related to determining how much stronger (or weaker) the power is compared to the transmission of Msg1 (preamble) when the terminal transmits Msg3 (PUSCH) of the random access process, or a power-related parameter used to determine the transmission power of Msg3.

[0655] The terminal performs a random access process including the transmission of message 1 (Msg1) and message 3 (Msg3) to the base station, wherein the transmission power of Msg3 transmission performed in the same resource type as Msg1 transmission is determined based on a first power offset, and the transmission power of Msg3 transmission performed in a different resource type from Msg1 transmission is determined based on a second power offset (S282).

[0656] For example, the first power offset may be applied when the Msg1 transmission is performed in a non-SBFD (subband full duplex) resource and the Msg3 transmission is also performed in a non-SBFD resource. And, the second power offset may be applied when the Msg1 transmission is performed in a non-SBFD resource and the Msg3 transmission is performed in an SBFD resource, or when the Msg1 transmission is performed in an SBFD resource and the Msg3 transmission is performed in a non-SBFD resource.

[0657] For example, the first power offset may be applied when the Msg1 transmission is performed in an SBFD resource and the Msg3 transmission is also performed in an SBFD resource, and the second power offset may be applied when the Msg1 transmission is performed in a non-SBFD resource and the Msg3 transmission is performed in an SBFD resource, or when the Msg1 transmission is performed in an SBFD resource and the Msg3 transmission is performed in a non-SBFD resource.

[0658] According to an embodiment, for the terminal, i) the SBFD operation is not set as a feature separate from the half duplex operation, and ii) a separated RACH setting (the aforementioned Option 2) may be applied. In this case, the separated RACH setting may include a legacy RACH setting and an additional RACH setting.

[0659] In such cases, the RACH setting information may be an information element (IE) that associates a feature combination with a set of preambles (e.g., the aforementioned FeatureCombinationPreambles).

[0660] According to an embodiment, the RACH setting information may be included in an additional RACH setting (e.g., the aforementioned Additional RACH-ConfigList) of an individual RACH setting (Option 2).

[0661] At this time, legacy RACH configurations and additional RACH configurations may be provided by information elements or parameters with names different from those in this disclosure during the standardization process. For example, legacy RACH configurations may be provided by an upper-level (e.g., RRC (radio resource control) layer) information element / parameter named sbfd-RACH-SingleConfig, and additional RACH configurations may be provided by an upper-level information element / parameter named sbfd-RACH-DualConfig.

[0662] Examples in which the first power offset and the second power offset are set / indicated by specific RRC parameters / information elements have been described in FIGS. 17 to 27. The first power offset and the second power offset may be provided to the terminal based on at least one of the methods described in FIGS. 17 to 27.

[0663] Meanwhile, in the example of FIG. 28, SBFD resources and non-SBFD resources were exemplified as resource types for the transmission of Msg1 and Msg3, but this is not a limitation. For example, the method and apparatus according to the present disclosure may be applied even in cases where the resource types are different types of resources, such as SSFD resources and non-SSFD resources, NES resources and non-NES resources, resources for general terminals and resources for RedCap (reduced capability) terminals.

[0664] According to the present disclosure, when message 1 (Msg1) and message 3 (Msg3) are transmitted through different resource types (e.g., message 1 is transmitted through a non-SBFD resource, such as a UL resource, and message 3 is transmitted through an SBFD resource), message 3 can be transmitted with sufficient power to compensate for the increased level of interference in the SBFD resource by applying a separately defined second power offset. This can improve the random access success rate and reliability.

[0665] In addition, if the transmission resources of message 1 and message 3 are of the same resource type (for example, when message 1 and message 3 are both transmitted through a UL resource that is a non-SBFD resource), unnecessary power boosting can be prevented by using the first power offset.

[0666] In addition, by preventing the problem of excessive transmission power (over-powering) that may occur when applying a uniform offset without considering the characteristics (interference level) of each resource type, unnecessary interference to adjacent cells or other SBFD terminals can be minimized.

[0667] In addition, a failure to transmit Message 3 implies a random access re-transmission, which causes an initial connection delay. However, according to the method of the present disclosure, even if the resource type for transmitting Message 3 changes compared to the transmission of Message 1, the success rate of the random access can be increased by applying appropriate power, and as a result, the latency required for the terminal to connect to the network can be reduced.

[0668] Furthermore, in situations where different resource types are mixed, the method for setting / instructing parameters related to transmission power control during the random access process is clarified to prevent ambiguity between the network and the terminal.

[0669] The effects obtainable from the embodiments of the present disclosure are not limited to those mentioned above, and other unmentioned effects can be clearly derived and understood by a person skilled in the art to which the technical configuration of the present disclosure applies from the description of the embodiments of the present disclosure below. That is, unintended effects resulting from implementing the configuration described in the present disclosure can also be derived by a person skilled in the art from the embodiments of the present disclosure.

[0670] FIG. 29 illustrates a signaling process and operation method between a base station and a terminal according to one embodiment of the present disclosure.

[0671] Referring to FIG. 29, the base station transmits random access channel (RACH) setting information including a first power offset and a second power offset to the terminal (S291).

[0672] As described above, a first power offset and a second power offset may be set / instructed according to at least one of the methods of FIGS. 17 to 25, depending on i) whether the SBFD is set as a feature separate from the existing operation to the terminal and ii) whether a single RACH setting (Option 1) or an individual RACH setting (Option 2) is applied to the terminal. Alternatively, it is possible to set / instruct the power offsets independently according to the resource types of Msg1 transmission and Msg3 transmission, as in FIG. 26, or to set / instruct the first power offset and the second power offset according to whether resource type switching occurs in Msg1 transmission and Msg3 transmission, as in FIG. 27.

[0673] The base station receives a preamble (Msg1) from the terminal in the RO of the first resource type (S292).

[0674] The base station sends a random access response (Msg2) to the terminal (S293).

[0675] The terminal determines the transmission power of Msg3 PUSCH by applying a first power offset or a second power offset based on the second resource type to transmit Msg3 PUSCH (S294).

[0676] Here, the statement that the terminal is based on a second resource type to transmit Msg3 PUSCH may mean determining whether the second resource type to transmit Msg3 PUSCH is the same as or different from the first resource type used for Msg1 transmission. For example, the terminal may determine the transmission power based on a first power offset for Msg3 transmission performed at the same resource type as Msg1 transmission, and determine the transmission power based on a second power offset for Msg3 transmission performed at a different resource type from Msg1 transmission. This may also be expressed as using different power offsets depending on whether switching of the resource types used in Msg1 transmission and Msg3 transmission occurs, or whether switching of the operation types occurs in Msg1 transmission and Msg3 transmission.

[0677] According to an embodiment, the terminal may apply a first power offset or a second power offset depending on what the second resource type is to transmit Msg3 PUSCH (e.g., whether it is an SBFD resource or a non-SBFD resource), rather than whether switching of the resource type used in Msg1 transmission and Msg3 transmission (or switching of the operation type in Msg1 transmission and Msg3 transmission) occurs.

[0678] The terminal transmits Msg3 PUSCH to the base station with the transmission power determined above (S295).

[0679] <PRACH 설정 시나리오에의 각 방법 적용>

[0680] This paragraph explains how to apply the cases mentioned above according to the situation of each PRACH setting.

[0681] Option 1 with one separate RACH configuration.

[0682] Alt 1: The SBFD-aware UE reinterprets PRACH power control parameter values ​​based on specific rules.

[0683] Alt 1-1: When gNB indicates a single PRACH power control parameter in accordance with the non-SBFD symbol.

[0684] 1) Send Msg1 in the RO of a non-SBFD symbol, and send msg3 PUSCH in a non-SBFD symbol. In this case, the same preamble_received_target_power can be used for Msg1 and Msg3 without separate adjustment.

[0685] 2) Send Msg1 in the RO of the non-SBFD symbol, and send msg3 PUSCH in the SBFD symbol.

[0686] In this case, if it is an SBFD system, the terminal reinterprets the parameters specified by the base station in the transmission of Msg1 through a pre-defined operation with the base station. Assuming that the terminal used the parameters reinterpreted by the SBFD system in the transmission of Msg1, the value operated with the preamble_received_target_power used is P in Msg3. O_PRE It is used by substituting it into.

[0687] 3) Send Msg1 at the RO of the SBFD symbol, and send msg3 PUSCH at the non-SBFD symbol.

[0688] In this case, since the gNB is expected to have provided preamble_received_target_power tailored to non-SBFD symbols, the parameter is used in Msg3 transmission without separate adjustment. In other words, the same preamble_received_target_power can be used for Msg1 and Msg3 without any separate adjustment.

[0689] 4) Send Msg1 from RO of SBFD symbol, send msg3 PUSCH from SBFD symbol.

[0690] In this case, if it is an SBFD system, the terminal reinterprets the parameters specified by the base station based on a pre-defined operation with the base station during the transmission of Msg1. The terminal takes the parameters reinterpreted by the SBFD system and applies the value obtained by operating with the preamble_received_target_power used in the transmission of Msg1 to P of Msg3. O_PRE It is used by substituting it into.

[0691] Alt 1-2: When gNB indicates a single PRACH power control parameter in accordance with the SBFD symbol.

[0692] 1) Send Msg1 at the RO of the non-SBFD symbol, and send msg 3 PUSCH at the non-SBFD symbol.

[0693] In this case, if it is a non-SBFD system, the terminal reinterprets the parameters specified by the base station based on a pre-determined operation with the base station during the transmission of Msg1. Assuming that the terminal used the parameters reinterpreted by the non-SBFD system in the transmission of Msg1, the value operated with the preamble_received_target_power used is P of Msg3. O_PRE It is used by substituting it into.

[0694] 2) Send Msg1 in the RO of the non-SBFD symbol, and send msg3 PUSCH in the SBFD symbol.

[0695] In this case, since it is expected that the gNB provided preamble_received_target_power in accordance with the SBFD symbol, the parameter is used in the Msg3 transmission without separate adjustment. That is, the same preamble_received_target_power can be used for Msg1 and Msg3 without separate adjustment.

[0696] 3) Send Msg1 at the RO of the SBFD symbol, and send msg3 PUSCH at the non-SBFD symbol.

[0697] In this case, if it is a non-SBFD system, the terminal reinterprets the parameters specified by the base station based on a pre-determined operation with the base station during the transmission of Msg1. The terminal takes the parameters reinterpreted in the non-SBFD system and applies the value obtained by operating with the preamble_received_target_power used in the transmission of Msg1 to P of Msg3. O_PRE It is used by substituting it into.

[0698] 4) Send Msg1 from RO of SBFD symbol, send msg3 PUSCH from SBFD symbol.

[0699] In this case, the same preamble_received_target_power can be used for Msg1 and Msg3 without separate adjustment.

[0700] Alt 2: How to use a single PRACH power control parameter value.

[0701] Alt 2-1: Assume that the gNB specifies a single PRACH power control parameter as an arbitrary value. In this method, this refers to a case where the terminal does not know what type of PRACH power the gNB assumed and specified the power control parameter for, that is, a case where there is no information about it.

[0702] 1) Send Msg1 at the RO of the non-SBFD symbol, and send msg 3 PUSCH at the non-SBFD symbol.

[0703] In this case, the same preamble_received_targer_power is used for Msg1 and Msg3 without separate adjustment.

[0704] 2) Send Msg1 in the RO of the non-SBFD symbol, and send msg3 PUSCH in the SBFD symbol.

[0705] Method 1 Application: The target power value of PRACH can be adjusted according to the position of Msg3 by using the preambleReceivedTargetPower given in Msg3 as is, without additional parameters.

[0706] Application of Method 2: P through additional parameters O_PRE By performing adjustments, the target power value of PRACH can be adjusted according to the position of Msg3. For example, in this case, delta_type 1 may be biased toward a negative value.

[0707] Application of Method 3: Δ through additional parameters PREAMBLE,Msg3 By performing adjustments, the target power value of PRACH can be adjusted according to the position of Msg3. For example, in this case, delta_type 2 may be biased toward a negative value.

[0708] Application of Method 4: The target power value of PRACH can be comprehensively adjusted according to the position of Msg3 through additional parameters. In this case, delta_type3 can be set.

[0709] 3) Send Msg1 at the RO of the SBFD symbol, and send msg3 PUSCH at the non-SBFD symbol.

[0710] Method 1 Application: The target power value of PRACH can be adjusted according to the position of Msg3 by using the preambleReceivedTargetPower given in Msg3 as is, without additional parameters.

[0711] Applying Method 2: The target power value of PRACH can be adjusted according to the position of Msg3 using preamble_received_targe_power + delta_type 3. For example, delta_type 1 in this case can be biased toward a positive value.

[0712] Applying Method 3: The transmission power difference between msg 3 and PRACH can be adjusted according to the position of msg 3 using delta_preamble + delta_type 4. For example, delta_type 2 in this case can be biased toward a positive value.

[0713] Application of Method 4: The target power value of PRACH can be comprehensively adjusted according to the position of Msg3 through additional parameters. At this time, delta_type6 can be set.

[0714] 4) Send Msg1 from RO of SBFD symbol, send msg3 PUSCH from SBFD symbol.

[0715] In this case, the same preamble_received_targer_power is used for Msg1 and Msg3 without separate adjustment.

[0716] Alt 2-2: When gNB indicates a single PRACH power control parameter in accordance with the non-SBFD symbol.

[0717] 1) Send Msg1 at the RO of the non-SBFD symbol, and send msg 3 PUSCH at the non-SBFD symbol.

[0718] In this case, the same preamble_received_target_power is used for Msg1 and Msg3 without separate adjustment.

[0719] 2) Send Msg1 in the RO of the non-SBFD symbol, and send msg3 PUSCH in the SBFD symbol.

[0720] Method 1 Application: The target power value of PRACH can be adjusted according to the position of Msg3 by using the preambleReceivedTargetPower given in Msg3 as is, without additional parameters.

[0721] Application of Method 2: P through additional parameters O_PREBy performing adjustments, the target power value of PRACH can be adjusted according to the position of Msg3. For example, delta_type 1 in this case may be biased toward a negative value.

[0722] Application of Method 3: Δ through additional parameters PREAMBLE,Msg3 By performing adjustments, the target power value of PRACH can be adjusted according to the position of Msg3. For example, delta_type 2 in this case may be biased toward a negative value.

[0723] Application of Method 4: The target power value of PRACH can be comprehensively adjusted according to the position of Msg3 through additional parameters. At this time, delta_type3 can be set.

[0724] 3) Send Msg1 at the RO of the SBFD symbol, and send msg3 PUSCH at the non-SBFD symbol.

[0725] In this case, since the gNB is expected to have provided preamble_received_target_power tailored to non-SBFD symbols, the parameter is used in the Msg3 transmission without separate adjustment. That is, the same preamble_received_target_power is used for Msg1 and Msg3 without any adjustment.

[0726] 4) Send Msg1 from RO of SBFD symbol, send msg3 PUSCH from SBFD symbol.

[0727] Method 1 Application: The target power value of PRACH can be adjusted according to the position of Msg3 by using the preambleReceivedTargetPower given in Msg3 as is, without additional parameters.

[0728] Application of Method 2: P through additional parameters O_PREBy performing adjustments, the target power value of PRACH can be adjusted according to the position of Msg3. For example, delta_type 1 in this case may be biased toward a negative value.

[0729] Application of Method 3: Δ through additional parameters PREAMBLE,Msg3 By performing adjustments, the target power value of PRACH can be adjusted according to the position of Msg3. For example, delta_type 2 in this case may be biased toward a negative value.

[0730] Application of Method 4: The target power value of PRACH can be comprehensively adjusted according to the position of Msg3 through additional parameters. At this time, delta_type3 can be set.

[0731] Alt 2-3: When gNB indicates a single PRACH power control parameter in accordance with the SBFD symbol.

[0732] 1) Send Msg1 at the RO of the non-SBFD symbol, and send msg 3 PUSCH at the non-SBFD symbol.

[0733] Method 1 Application: The target power value of PRACH can be adjusted according to the position of Msg3 by using the preambleReceivedTargetPower given in Msg3 as is, without additional parameters.

[0734] Applying Method 2: The target power value of PRACH can be adjusted according to the position of Msg3 using preamble_received_targe_power + delta_type 3. For example, delta_type 1 in this case can be biased toward a positive value.

[0735] Applying Method 3: The transmission power difference between msg 3 and PRACH can be adjusted according to the position of msg 3 using delta_preamble + delta_type 4. For example, delta_type 2 in this case can be biased toward a positive value.

[0736] Application of Method 4: The target power value of PRACH can be comprehensively adjusted according to the position of Msg3 through additional parameters. At this time, delta_type3 can be set.

[0737] 2) Send Msg1 in the RO of the non-SBFD symbol, and send msg3 PUSCH in the SBFD symbol.

[0738] In this case, since it is expected that the gNB provided preamble_received_target_power in accordance with the SBFD symbol, the parameter is used in the transmission of Msg3 without separate adjustment. That is, the same preamble_received_target_power is used for Msg1 and Msg3 without separate adjustment.

[0739] 3) Send Msg1 at the RO of the SBFD symbol, and send msg3 PUSCH at the non-SBFD symbol.

[0740] Method 1 Application: The target power value of PRACH can be adjusted according to the position of Msg3 by using the preambleReceivedTargetPower given in Msg3 as is, without additional parameters.

[0741] Applying Method 2: The target power value of PRACH can be adjusted according to the position of Msg3 using preamble_received_targe_power + delta_type 3. For example, delta_type 1 in this case can be biased toward a positive value.

[0742] Applying Method 3: The transmission power difference between msg 3 and PRACH can be adjusted according to the position of msg 3 using delta_preamble + delta_type 4. For example, delta_type 2 in this case can be biased toward a positive value.

[0743] Application of Method 4: The target power value of PRACH can be comprehensively adjusted according to the position of Msg3 through additional parameters. At this time, delta_type3 can be set.

[0744] 4) Send Msg1 from RO of SBFD symbol, send msg3 PUSCH from SBFD symbol.

[0745] In this case, the same preamble_received_target_power is used for Msg1 and Msg3 without separate adjustment.

[0746] Option 2 with two separate RACH configurations.

[0747] In Option 2, since two PRACH power control parameters are set, each preamble_received_target_power value is used when transmitting Msg3 PUSCH. The terminal must be capable of receiving each power control parameter, and if different systems are used for Msg1 and Msg3, different power control parameter settings are instructed.

[0748] FIG. 30 illustrates a wireless device that can be applied to the present specification.

[0749] Referring to FIG. 30, the first wireless device (100) and the second wireless device (200) can transmit and receive wireless signals through various wireless access technologies (e.g., LTE, NR).

[0750] The first wireless device (100) includes at least one processor (102) and at least one memory (104), and may additionally include at least one transceiver (106) and / or at least one antenna (108). The at least one processor (102, hereinafter simply referred to as processor) controls at least one memory (104, hereinafter simply referred to as memory) and / or at least one transceiver (106, hereinafter simply referred to as transceiver or transceiver), and may be configured to implement the descriptions, functions, procedures, proposals, methods, and / or operation sequences disclosed in this document. For example, the processor (102) may process information within the memory (104) to generate a first information / signal, and then transmit a wireless signal containing the first information / signal through the transceiver (106). Additionally, the processor (102) may receive a wireless signal containing a second information / signal through a transceiver (106) and then store information obtained from signal processing of the second information / signal in a memory (104). The memory (104) may be connected to the processor (102) and may store various information related to the operation of the processor (102). For example, the memory (104) may store software code containing instructions for performing some or all of the processes controlled by the processor (102) or for performing the descriptions, functions, procedures, proposals, methods, and / or operation sequence diagrams disclosed in this document. Here, the processor (102) and the memory (104) may be part of a communication modem / circuit / chip designed to implement wireless communication technology (e.g., LTE, NR). The transceiver (106) may be connected to the processor (102) and may transmit and / or receive a wireless signal through one or more antennas (108). The transceiver (106) may include a transmitter and / or a receiver. The transceiver (106) may be used in combination with an RF (Radio Frequency) unit.In this specification, a wireless device may refer to a communication modem / circuit / chip.

[0751] The processor (102) receives random access channel (RACH) configuration information including a first power offset and a second power offset from a base station, and performs a random access process including the transmission of message 1 (Msg1) and message 3 (Msg3) to the base station. At this time, each of the first power offset and the second power offset is related to the power offset between the transmission of Msg3 and the transmission of Msg1, and the transmission power of Msg3 transmitted in the same resource type as the transmission of Msg1 is determined based on the first power offset, and the transmission power of Msg3 transmitted in a different resource type from the transmission of Msg1 is determined based on the second power offset. The specific operation has been described above with reference to FIGS. 17 to 29.

[0752] The second wireless device (200) includes at least one processor (202) and at least one memory (204), and may additionally include at least one transceiver (206) and / or at least one antenna (208). The processor (202) controls the memory (204) and / or transceiver (206) and may be configured to implement the descriptions, functions, procedures, proposals, methods and / or sequences of operation disclosed herein. For example, the processor (202) may process information within the memory (204) to generate a third information / signal and then transmit a wireless signal containing the third information / signal through the transceiver (206). Additionally, the processor (202) may receive a wireless signal containing a fourth information / signal through the transceiver (206) and then store information obtained from the signal processing of the fourth information / signal in the memory (204). Memory (204) may be connected to the processor (202) and may store various information related to the operation of the processor (202). For example, memory (204) may store software code containing instructions for performing some or all of the processes controlled by the processor (202) or for performing the descriptions, functions, procedures, proposals, methods, and / or operation sequences disclosed in this document. Here, the processor (202) and memory (204) may be part of a communication modem / circuit / chip designed to implement wireless communication technology (e.g., LTE, NR). A transceiver (206) may be connected to the processor (202) and may transmit and / or receive wireless signals through one or more antennas (208). The transceiver (206) may include a transmitter and / or receiver. The transceiver (206) may be interchangeable with an RF unit. In this specification, a wireless device may mean a communication modem / circuit / chip.

[0753] The processor (202) transmits random access channel (RACH) configuration information including a first power offset and a second power offset to the terminal, and performs a random access process including receiving message 1 (Msg1) and message 3 (Msg3) transmissions from the terminal. Each of the first power offset and the second power offset is related to the power offset between the transmission of Msg3 and the transmission of Msg1, and the transmission power of Msg3 transmission performed in the same resource type as the transmission of Msg1 is determined based on the first power offset, and the transmission power of Msg3 transmission performed in a different resource type from the transmission of Msg1 is determined based on the second power offset. The specific operation has been described above with reference to FIGS. 17 to 29.

[0754] Figure 31 illustrates another example of a wireless device.

[0755] According to FIG. 31, the wireless device may include at least one processor (102, 202), at least one memory (104, 204), at least one transceiver (106, 206), and one or more antennas (108, 208).

[0756] The difference between the example of the wireless device described in FIG. 30 and the example of the wireless device in FIG. 31 is that in FIG. 30, the processor (102, 202) and the memory (104, 204) are separated, whereas in the example of FIG. 31, the memory (104, 204) is included in the processor (102, 202). For example, the processor and the memory may form a single chipset.

[0757] Hereinafter, hardware elements of the wireless device (100, 200) will be described in more detail. Although not limited thereto, one or more protocol layers may be implemented by one or more processors (102, 202). For example, one or more processors (102, 202) may implement one or more layers (e.g., functional layers such as PHY, MAC, RLC, PDCP, RRC, SDAP). One or more processors (102, 202) may generate one or more Protocol Data Units (PDUs) and / or Service Data Units (SDUs) according to the descriptions, functions, procedures, proposals, methods, and / or flowcharts of operation disclosed in this document. One or more processors (102, 202) may generate messages, control information, data, or information according to the descriptions, functions, procedures, proposals, methods, and / or flowcharts of operation disclosed in this document. One or more processors (102, 202) may generate a signal (e.g., baseband signal) containing a PDU, SDU, message, control information, data, or information according to the functions, procedures, proposals, and / or methods disclosed in this document and provide it to one or more transceivers (106, 206). One or more processors (102, 202) may receive a signal (e.g., baseband signal) from one or more transceivers (106, 206) and may obtain a PDU, SDU, message, control information, data, or information according to the descriptions, functions, procedures, proposals, methods, and / or flowcharts disclosed in this document.

[0758] One or more processors (102, 202) may be referred to as a controller, microcontroller, microprocessor, or microcomputer. One or more processors (102, 202) may be implemented by hardware, firmware, software, or a combination thereof. For example, one or more Application Specific Integrated Circuits (ASICs), one or more Digital Signal Processors (DSPs), one or more Digital Signal Processing Devices (DSPDs), one or more Programmable Logic Devices (PLDs), or one or more Field Programmable Gate Arrays (FPGAs) may be included in one or more processors (102, 202). One or more processors (102, 202) may also be implemented as at least one computer-readable medium (CRM) containing instructions based on being executed by at least one processor.

[0759] For example, in at least one computer-readable medium (CRM) comprising instructions that are executed by at least one processor to perform operations, said operations include receiving random access channel (RACH) configuration information from a base station including a first power offset and a second power offset, and performing a random access process including transmitting message 1 (Msg1) and message 3 (Msg3) to said base station. In this case, the first power offset and the second power offset each relate to the power offset between the transmission of Msg3 and the transmission of Msg1, and the transmission power of Msg3 transmitted in the same resource type as the transmission of Msg1 is determined based on the first power offset, and the transmission power of Msg3 transmitted in a different resource type from the transmission of Msg1 is determined based on the second power offset. The specific operation has been described with reference to FIGS. 17 to 29.

[0760] The descriptions, functions, procedures, proposals, methods, and / or operation sequences disclosed in this document may be implemented using firmware or software, and the firmware or software may be implemented to include modules, procedures, functions, etc. Firmware or software configured to perform the descriptions, functions, procedures, proposals, methods, and / or operation sequences disclosed in this document may be included in one or more processors (102, 202) or stored in one or more memories (104, 204) and driven by one or more processors (102, 202). The descriptions, functions, procedures, proposals, methods, and / or operation sequences disclosed in this document may be implemented using firmware or software in the form of code, instructions, and / or sets of instructions.

[0761] One or more memories (104, 204) may be connected to one or more processors (102, 202) and may store various forms of data, signals, messages, information, programs, code, instructions, and / or commands. One or more memories (104, 204) may be composed of ROM, RAM, EPROM, flash memory, hard drive, registers, cache memory, computer read storage media, and / or combinations thereof. One or more memories (104, 204) may be located inside and / or outside of one or more processors (102, 202). Additionally, one or more memories (104, 204) may be connected to one or more processors (102, 202) through various technologies such as wired or wireless connections.

[0762] One or more transceivers (106, 206) may transmit user data, control information, wireless signals / channels, etc., as mentioned in the methods and / or operation flowcharts, etc., of this document to one or more other devices. One or more transceivers (106, 206) may receive user data, control information, wireless signals / channels, etc., as mentioned in the descriptions, functions, procedures, proposals, methods and / or operation flowcharts, etc., disclosed in this document from one or more other devices. For example, one or more transceivers (106, 206) may be connected to one or more processors (102, 202) and may transmit and receive wireless signals. For example, one or more processors (102, 202) may control one or more transceivers (106, 206) to transmit user data, control information, or wireless signals to one or more other devices. Additionally, one or more processors (102, 202) may control one or more transceivers (106, 206) to receive user data, control information, or wireless signals from one or more other devices. Additionally, one or more transceivers (106, 206) may be connected to one or more antennas (108, 208), and one or more transceivers (106, 206) may be configured to transmit and receive user data, control information, wireless signals / channels, etc., as described in the descriptions, functions, procedures, proposals, methods, and / or flowcharts of operation disclosed in this document through one or more antennas (108, 208). In this document, one or more antennas may be multiple physical antennas or multiple logical antennas (e.g., antenna ports). One or more transceivers (106, 206) can convert the received wireless signal / channel, etc. from an RF band signal to a baseband signal in order to process the received user data, control information, wireless signal / channel, etc. using one or more processors (102, 202).One or more transceivers (106, 206) can convert user data, control information, wireless signals / channels, etc. processed using one or more processors (102, 202) from baseband signals to RF band signals. To this end, one or more transceivers (106, 206) may include (analog) oscillators and / or filters.

[0763] FIG. 32 illustrates an example of a signal processing module structure. Here, signal processing may be performed in the processor (102, 202) of FIG. 30.

[0764] Referring to FIG. 32, a transmission device (e.g., a processor, a processor and memory, or a processor and a transceiver) within a terminal or base station may include a scrambler (301), a modulator (302), a layer mapper (303), an antenna port mapper (304), a resource block mapper (305), and a signal generator (306).

[0765] The transmission device can transmit one or more codewords. Each coded bit within a codeword is scrambled by a scrambler (301) and transmitted over a physical channel. A codeword may be referred to as a data sequence and may be equivalent to a transmission block, which is a data block provided by the MAC layer.

[0766] The scrambled bits are modulated into complex-valued modulation symbols by a modulator (302). The modulator (302) can modulate the scrambled bits according to a modulation scheme to arrange them into complex-valued modulation symbols representing positions on a signal constellation. There are no restrictions on the modulation scheme, and m-PSK (m-Phase Shift Keying) or m-QAM (m-Quadrature Amplitude Modulation), etc., may be used for modulating the encoded data. The modulator may be referred to as a modulation mapper.

[0767] The complex modulation symbols above can be mapped to one or more transmission layers by a layer mapper (303). The complex modulation symbols on each layer can be mapped by an antenna port mapper (304) for transmission on an antenna port.

[0768] The resource block mapper (305) can map complex modulation symbols for each antenna port to appropriate resource elements within a virtual resource block allocated for transmission. The resource block mapper can map the virtual resource block to a physical resource block according to an appropriate mapping scheme. The resource block mapper (305) can assign complex modulation symbols for each antenna port to appropriate subcarriers and multiplex them according to the user.

[0769] The signal generator (306) can generate a complex-valued time domain OFDM symbol signal by modulating a complex modulation symbol for each antenna port, for example, an antenna-specific symbol, using a specific modulation method, for example, OFDM (Orthogonal Frequency Division Multiplexing). The signal generator can perform an Inverse Fast Fourier Transform (IFFT) on the antenna-specific symbol, and a Cyclic Prefix (CP) can be inserted into the time domain symbol after the IFFT is performed. The OFDM symbol is transmitted to a receiving device through each transmitting antenna after undergoing digital-to-analog conversion, frequency uplink conversion, etc. The signal generator may include an IFFT module, a CP inserter, a Digital-to-Analog Converter (DAC), a frequency uplink converter, etc.

[0770] FIG. 33 illustrates another example of a signal processing module structure within a transmission device. Here, signal processing can be performed in a processor of a terminal / base station, such as the processor (102, 202) of FIG. 30.

[0771] Referring to FIG. 33, a transmission device (e.g., a processor, a processor and memory, or a processor and a transceiver) within a terminal or base station may include a scrambler (401), a modulator (402), a layer mapper (403), a precoder (404), a resource block mapper (405), and a signal generator (406).

[0772] For one codeword, the transmission device can scramble the coded bits within the codeword by the scrambler (401) and then transmit them through the physical channel.

[0773] The scrambled bits are modulated into complex modulation symbols by a modulator (402). The modulator may modulate the scrambled bits according to a predetermined modulation scheme to arrange them into complex modulation symbols representing positions on a signal constellation. There are no restrictions on the modulation scheme, and pi / 2-BPSK (pi / 2-Binary Phase Shift Keying), m-PSK (m-Phase Shift Keying), or m-QAM (m-Quadrature Amplitude Modulation), etc., may be used for modulating the encoded data.

[0774] The complex modulation symbol can be mapped to one or more transmission layers by the layer mapper (403).

[0775] Complex modulation symbols on each layer can be precoded by a precoder (404) for transmission on an antenna port. Here, the precoder may perform precoding after performing transform precoding on the complex modulation symbols. Alternatively, the precoder may perform precoding without performing transform precoding. The precoder (404) may process the complex modulation symbols in a MIMO manner according to multiple transmission antennas to output antenna-specific symbols and distribute the antenna-specific symbols to the corresponding resource block mapper (405). The output z of the precoder (404) can be obtained by multiplying the output y of the layer mapper (403) by an N-X-M precoding matrix W. Here, N is the number of antenna ports and M is the number of layers.

[0776] The resource block mapper (405) maps the demodulation modulation symbol for each antenna port to the appropriate resource element within the virtual resource block allocated for transmission.

[0777] The resource block mapper (405) can assign complex modulation symbols to appropriate subcarriers and multiplex them according to the user.

[0778] The signal generator (406) can generate a complex-valued time domain Orthogonal Frequency Division Multiplexing (OFDM) symbol signal by modulating a complex modulated symbol using a specific modulation method, such as OFDM. The signal generator (406) can perform an Inverse Fast Fourier Transform (IFFT) on an antenna-specific symbol, and a Cyclic Prefix (CP) can be inserted into the time domain symbol after the IFFT is performed. The OFDM symbol is transmitted to a receiving device through each transmitting antenna after undergoing digital-to-analog conversion, frequency uplink conversion, etc. The signal generator (406) may include an IFFT module, a CP inserter, a Digital-to-Analog Converter (DAC), a frequency uplink converter, etc.

[0779] The signal processing process of the receiving device may be configured as the inverse of the signal processing process of the transmitter. Specifically, the processor of the receiving device performs decoding and demodulation for a wireless signal received from the outside through the antenna port(s) of the transmitter and receiver. The receiving device may include multiple receiving antennas, and each signal received through the receiving antennas is restored to a baseband signal, then undergoes multiplexing and MIMO demodulation to be restored to the data sequence that the transmitting device originally intended to transmit. The receiving device (1820) may include a signal restorer for restoring the received signal to a baseband signal, a multiplexer for combining and multiplexing the received processed signals, and a channel demodulator for demodulating the multiplexed signal sequence into the corresponding codeword. The signal restorer, multiplexer, and channel demodulator may be configured as a single integrated module or as separate independent modules that perform their functions. More specifically, the signal restorer may include an analog-to-digital converter (ADC) that converts an analog signal into a digital signal, a CP remover that removes CP from the digital signal, an FFT module that applies a fast Fourier transform (FFT) to the signal from which CP has been removed to output a frequency domain symbol, and a resource element demapper / equalizer that restores the frequency domain symbol to an antenna-specific symbol. The antenna-specific symbol is restored to a transport layer by a multiplexer, and the transport layer is restored to a codeword that the transmitting device intended to transmit by a channel demodulator.

[0780] FIG. 34 illustrates an example of a wireless communication device according to an embodiment of the present disclosure.

[0781] Referring to FIG. 34, a wireless communication device, for example, a terminal, may include at least one of a processor (2310), such as a digital signal processor (DSP) or a microprocessor, a transceiver (2335), a power management module (2305), an antenna (2340), a battery (2355), a display (2315), a keypad (2320), a Global Positioning System (GPS) chip (2360), a sensor (2365), a memory (2330), a Subscriber Identification Module (SIM) card (2325), a speaker (2345), and a microphone (2350). The antenna and the processor may be multiple.

[0782] The processor (2310) can implement the functions, procedures, and methods described in this specification. The processor (2310) of FIG. 34 may be the processor (102, 202) of FIG. 30.

[0783] The memory (2330) is connected to the processor (2310) and stores information related to the operation of the processor. The memory may be located inside or outside the processor and may be connected to the processor through various technologies such as wired or wireless connections.

[0784] The user can input various types of information, such as phone numbers, using various techniques, such as pressing a button on the keypad (2320) or using a microphone (2350) to activate sound. The processor (2310) receives and processes the user's information and can perform appropriate functions, such as making a call to the input phone number. In some scenarios, data may be retrieved from a SIM card (2325) or memory (2330) to perform appropriate functions. In some scenarios, the processor (2310) can display various types of information and data on a display (2315) for the user's convenience.

[0785] A transceiver (2335) is connected to a processor (2310) to transmit and / or receive a wireless signal, such as a Radio Frequency (RF) signal. The processor may control the transceiver to initiate communication or to transmit a wireless signal containing various types of information or data, such as voice communication data. The transceiver includes a transmitter and a receiver for transmitting and receiving wireless signals. An antenna (2340) may facilitate the transmission and reception of wireless signals. In some embodiments, when the transceiver receives a wireless signal, it may forward and convert the signal to a baseband frequency for processing by the processor. The processed signal may be processed by various techniques, such as being converted into audible or readable information to be output through a speaker (2345).

[0786] Although not illustrated in FIG. 34, various components such as a camera and a USB (Universal Serial Bus) port may be additionally included in the terminal. For example, the camera may be connected to the processor (2310).

[0787] FIG. 34 is merely one example of an implementation of a terminal, and is not limited thereto. The terminal is not required to include all the elements of FIG. 34. For example, some components, such as a keypad (2320), a Global Positioning System (GPS) chip (2360), a sensor (2365), a SIM card (2325), etc., may not be essential and, in this case, may not be included in the terminal.

[0788] FIG. 35 illustrates a communication system (1) applicable to the present specification.

[0789] Referring to FIG. 35, the communication system (1) to which the present specification applies includes a wireless device, a base station, and a network. Here, the wireless device refers to a device that performs communication using wireless access technology (e.g., 5G NR (New RAT), LTE (Long Term Evolution)) and may be referred to as a communication / wireless / 5G device. Although not limited thereto, the wireless device may include a robot (100a), a vehicle (100b-1, 100b-2), an XR (eXtended Reality) device (100c), a hand-held device (100d), a home appliance (100e), an IoT (Internet of Thing) device (100f), and an AI device / server (400). For example, the vehicle may include a vehicle equipped with wireless communication capabilities, an autonomous vehicle, a vehicle capable of performing inter-vehicle communication, etc. Here, the vehicle may include an Unmanned Aerial Vehicle (UAV) (e.g., a drone). XR devices include AR (Augmented Reality) / VR (Virtual Reality) / MR (Mixed Reality) devices and can be implemented in the form of HMDs (Head-Mounted Devices), HUDs (Head-Up Displays) equipped in vehicles, televisions, smartphones, computers, wearable devices, home appliances, digital signage, vehicles, robots, etc. Portable devices may include smartphones, smartpads, wearable devices (e.g., smartwatches, smart glasses), computers (e.g., laptops, etc.). Home appliances may include TVs, refrigerators, washing machines, etc. IoT devices may include sensors, smart meters, etc. For example, base stations and networks may be implemented as wireless devices, and a specific wireless device (200a) may operate as a base station / network node to other wireless devices.

[0790] Wireless devices (100a to 100f) can be connected to a network (300) through a base station (200). Artificial Intelligence (AI) technology may be applied to the wireless devices (100a to 100f), and the wireless devices (100a to 100f) can be connected to an AI server (400) through the network (300). The network (300) can be configured using a 3G network, a 4G (e.g., LTE) network, or a 5G (e.g., NR) network. The wireless devices (100a to 100f) may communicate with each other through the base station (200) / network (300), but they may also communicate directly (e.g., sidelink communication) without going through the base station / network. For example, vehicles (100b-1, 100b-2) can communicate directly (e.g., V2V (Vehicle to Vehicle) / V2X (Vehicle to everything) communication). Also, IoT devices (e.g., sensors) can communicate directly with other IoT devices (e.g., sensors) or other wireless devices (100a to 100f).

[0791] Wireless communication / connection (150a, 150b, 150c) can be established between wireless devices (100a~100f) / base station (200) and base station (200) / base station (200). Here, wireless communication / connection can be achieved through various wireless access technologies (e.g., 5G NR), such as uplink / downlink communication (150a), sidelink communication (150b) (or D2D communication), and inter-base station communication (150c) (e.g., relay, IAB (Integrated Access Backhaul)). Through wireless communication / connection (150a, 150b, 150c), wireless devices and base stations / wireless devices, and base stations and base stations can transmit / receive wireless signals to / from each other. For example, wireless communication / connection (150a, 150b, 150c) can transmit / receive signals through various physical channels. To this end, based on various proposals of this specification, at least some of the following may be performed: various configuration information setting processes for transmitting / receiving wireless signals, various signal processing processes (e.g., channel encoding / decoding, modulation / demodulation, resource mapping / demapping, etc.), resource allocation processes, etc.

[0792] The claims described in this specification may be combined in various ways. For example, the technical features of the method claims in this specification may be combined to be implemented as a device, and the technical features of the device claims in this specification may be combined to be implemented as a method. Furthermore, the technical features of the method claims and the technical features of the device claims in this specification may be combined to be implemented as a device, and the technical features of the method claims and the technical features of the device claims in this specification may be combined to be implemented as a method.

Claims

1. Regarding the method, A terminal receives random access channel (RACH) configuration information including a first power offset and a second power offset from a base station, and The above terminal performs a random access process including the transmission of Message 1 (Msg1) and Message 3 (Msg3) to the base station, wherein Each of the above first power offset and the above second power offset is related to the power offset between the Msg3 transmission and the Msg1 transmission, and A method characterized in that the transmission power of Msg3, which is performed in the same resource type as the Msg1 transmission, is determined based on the first power offset, and the transmission power of Msg3, which is performed in a different resource type from the Msg1 transmission, is determined based on the second power offset.

2. In Paragraph 1, A method characterized in that the first power offset is applied when the Msg1 transmission is performed in a non-SBFD (subband full duplex) resource and the Msg3 transmission is also performed in a non-SBFD resource, and the second power offset is applied when the Msg1 transmission is performed in a non-SBFD resource and the Msg3 transmission is performed in an SBFD resource, or when the Msg1 transmission is performed in an SBFD resource and the Msg3 transmission is performed in a non-SBFD resource.

3. In Paragraph 1, A method characterized in that the first power offset is applied when the Msg1 transmission is performed in an SBFD resource and the Msg3 transmission is also performed in an SBFD resource, and the second power offset is applied when the Msg1 transmission is performed in a non-SBFD resource and the Msg3 transmission is performed in an SBFD resource, or when the Msg1 transmission is performed in an SBFD resource and the Msg3 transmission is performed in a non-SBFD resource.

4. A method according to claim 1, characterized in that the Msg1 transmission is a RACH preamble transmission.

5. A method according to claim 1, characterized in that the Msg3 transmission is transmitted through a physical uplink shared channel.

6. A method according to claim 1, characterized in that for the terminal, i) the SBFD operation is not set as a feature separate from the half duplex operation, and ii) a separate RACH setting is applied.

7. A method according to claim 6, wherein the individual RACH settings include a legacy RACH setting and an additional RACH setting.

8. A method according to claim 1, characterized in that the RACH setting information is an information element (IE) that associates a feature combination with a set of preambles.

9. A method according to claim 1, characterized in that the RACH setting information is included in an additional RACH setting of an individual RACH setting.

10. The terminal (user equipment: UE) is, At least one transmitter / receiver; At least one memory; and The above includes at least one transceiver and at least one processor connected to the above at least one memory, The above at least one memory includes instructions that are executed by the above at least one processor to perform operations, wherein The above operations are, Receive random access channel (RACH) configuration information including a first power offset and a second power offset from a base station, and A random access process including the transmission of Message 1 (Msg1) and Message 3 (Msg3) to the base station is performed, Each of the above first power offset and the above second power offset is related to the power offset between the Msg3 transmission and the Msg1 transmission, and A terminal characterized in that the transmission power of Msg3 transmission performed in the same resource type as the above Msg1 transmission is determined based on the first power offset, and the transmission power of Msg3 transmission performed in a different resource type from the above Msg1 transmission is determined based on the second power offset.

11. In Paragraph 10, A terminal characterized in that the first power offset is applied when the Msg1 transmission is performed in a non-SBFD (subband full duplex) resource and the Msg3 transmission is also performed in a non-SBFD resource, and the second power offset is applied when the Msg1 transmission is performed in a non-SBFD resource and the Msg3 transmission is performed in an SBFD resource, or when the Msg1 transmission is performed in an SBFD resource and the Msg3 transmission is performed in a non-SBFD resource.

12. In Paragraph 10, A terminal characterized in that the first power offset is applied when the Msg1 transmission is performed in an SBFD resource and the Msg3 transmission is also performed in an SBFD resource, and the second power offset is applied when the Msg1 transmission is performed in a non-SBFD resource and the Msg3 transmission is performed in an SBFD resource, or when the Msg1 transmission is performed in an SBFD resource and the Msg3 transmission is performed in a non-SBFD resource.

13. A terminal according to claim 10, characterized in that the Msg1 transmission is a RACH preamble transmission.

14. A terminal according to claim 10, characterized in that the Msg3 transmission is transmitted through a physical uplink shared channel.

15. A terminal according to claim 10, characterized in that i) the SBFD operation is not set as a feature separate from the half duplex operation, and ii) a separate RACH setting is applied.

16. A terminal according to claim 15, wherein the individual RACH settings include a legacy RACH setting and an additional RACH setting.

17. A terminal according to claim 10, characterized in that the RACH setting information is an information element (IE) that associates a feature combination with a set of preambles.

18. A terminal according to claim 10, characterized in that the RACH setting information is included in an additional RACH setting of an individual RACH setting.

19. The device is, At least one memory; and The above includes at least one processor operably coupled with at least one memory, The above at least one memory includes instructions that are executed by the above at least one processor to perform operations, wherein The above operations are, Receive random access channel (RACH) configuration information including a first power offset and a second power offset from a base station, and A random access process including the transmission of Message 1 (Msg1) and Message 3 (Msg3) to the base station is performed, Each of the above first power offset and the above second power offset is related to the power offset between the Msg3 transmission and the Msg1 transmission, and A device characterized in that the transmission power of Msg3 transmission performed in the same resource type as the Msg1 transmission is determined based on the first power offset, and the transmission power of Msg3 transmission performed in a different resource type from the Msg1 transmission is determined based on the second power offset.

20. At least one computer-readable medium (CRM) comprising instructions that cause operations to be performed based on execution by at least one processor, wherein the operations are, Receive random access channel (RACH) configuration information including a first power offset and a second power offset from a base station, and Performing a random access process including transmitting Message 1 (Msg1) and Message 3 (Msg3) to the base station, wherein Each of the above first power offset and the above second power offset is related to the power offset between the Msg3 transmission and the Msg1 transmission, and A CRM characterized in that the transmission power of Msg3 transmission performed in the same resource type as the Msg1 transmission is determined based on the first power offset, and the transmission power of Msg3 transmission performed in a different resource type from the Msg1 transmission is determined based on the second power offset.

21. Regarding the method, A base station transmits random access channel (RACH) configuration information including a first power offset and a second power offset to a terminal, and The base station performs a random access process including receiving message 1 (Msg1) transmission and message 3 (Msg3) transmission from the terminal, wherein Each of the above first power offset and the above second power offset is related to the power offset between the Msg3 transmission and the Msg1 transmission, and A method characterized in that the transmission power of Msg3, which is performed in the same resource type as the Msg1 transmission, is determined based on the first power offset, and the transmission power of Msg3, which is performed in a different resource type from the Msg1 transmission, is determined based on the second power offset.

22. A base station is, At least one transmitter / receiver; At least one memory; and The above includes at least one transceiver and at least one processor connected to the above at least one memory, The above at least one memory includes instructions that are executed by the above at least one processor to perform operations, wherein The above operations are, Transmitting random access channel (RACH) configuration information including a first power offset and a second power offset to a terminal, and A random access process including receiving the transmission of Message 1 (Msg1) and Message 3 (Msg3) from the terminal is performed, Each of the above first power offset and the above second power offset is related to the power offset between the Msg3 transmission and the Msg1 transmission, and A base station characterized in that the transmission power of Msg3 transmission performed in the same resource type as the Msg1 transmission is determined based on the first power offset, and the transmission power of Msg3 transmission performed in a different resource type from the Msg1 transmission is determined based on the second power offset.

Images