Method and device for sending or receiving data in a wireless communication system supporting half-duplex frequency division duplex

Abstract

The present disclosure discloses a method for sending or receiving data in a wireless communication system supporting half-duplex frequency division duplex and a device supporting the method. The method may include the following steps: receiving configuration information through higher layer signaling; receiving downlink control information (DCI), wherein (i) a first duration for transmitting first data in a first direction and (ii) a second duration for transmitting second data in a second direction opposite to the first direction are configured based on at least one of the configuration information and the DCI; and switching from the first duration to the second duration is performed based on the first direction and the second direction being opposite to each other, wherein the priority of the first data and the second data is determined based on a predefined rule, and a protection period required for switching is included in the duration for transmitting data with a lower priority between the first duration and the second duration.

Description

Technical Field

[0001] The present disclosure relates to a wireless communication system, and more particularly, to a method for transmitting or receiving data based on half-duplex frequency division duplex and a device supporting the method. Background Art

[0002] Mobile communication systems have been developed to provide voice services while ensuring user activity. However, in mobile communication systems, not only voice services but also data services have been expanded. Currently, there is a shortage of resources due to the explosive growth of business, and users need higher-speed services. Therefore, a more advanced mobile communication system is required.

[0003] The requirements for the next generation mobile communication system should be able to support the accommodation of explosive data services, the sharp increase in data rate per user, the significant increase in the number of connected devices, very low end-to-end delay and high energy efficiency. To this end, various technologies have been studied, including dual connectivity, massive multiple-input multiple-output (MIMO), in-band full-duplex, non-orthogonal multiple access (NOMA), ultra-wideband support, device networking, etc. Summary of the invention

[0004] Technical issues

[0005] The present disclosure proposes a method for transmitting or receiving data in a wireless communication system supporting half-duplex frequency division duplex (FDD).

[0006] Specifically, the present disclosure proposes a method for configuring a time slot format for half-duplex FDD operation, and configuring / defining a switching time for switching from downlink to uplink or from uplink to downlink.

[0007] Furthermore, the present disclosure proposes a method for configuring a guard period for switching from downlink to uplink or from uplink to downlink for half-duplex FDD operation.

[0008] Furthermore, the present disclosure proposes a method for preventing link direction conflicts in half-duplex FDD operation.

[0009] The technical objectives to be achieved in the present disclosure are not limited to the above-described technical objectives, and other technical objectives not described above can be clearly understood by ordinary technicians in the field to which the present disclosure belongs from the following description.

[0010] Technical Solution

[0011] According to an embodiment of the present disclosure, a method for sending and receiving data by a user equipment (UE) in a wireless communication system supporting half-duplex frequency division duplex may include: receiving configuration information through higher layer signaling; receiving downlink control information (DCI), wherein, based on the configuration information or at least one of the DCI, (i) a first duration for transmitting first data in a first direction, and (ii) a second duration for transmitting second data in a second direction opposite to the first direction are configured; and based on the first direction and the second direction being opposite to each other, switching from the first duration to the second duration is performed, wherein the priority of the first data and the second data can be determined based on a predefined rule, and a protection period required for the switching can be included in the duration for transmitting data with a lower priority within the first duration or the second duration.

[0012] In addition, in the method according to an embodiment of the present disclosure, the predefined rule may be related to the type of information used to schedule the second data, and it may be determined that the second data has a higher priority than the first data based on the scheduling of the second data by the DCI, and the protection period may be included in the first duration.

[0013] Furthermore, in the method according to the embodiment of the present disclosure, the predefined rule may be related to at least one type of the first data or the second data.

[0014] In addition, in the method according to an embodiment of the present disclosure, based on the second data being a physical random access channel (PRACH) preamble, the protection period may be included in the first duration, and the first data may not be received during the protection period included in the first duration.

[0015] In addition, in the method according to an embodiment of the present disclosure, based on the first data being a synchronization signal block (SSB) and the second data being the PRACH preamble, the protection period may be located after the last symbol of the SSB is received in the first duration.

[0016] In addition, in the method according to an embodiment of the present disclosure, based on the fact that the first data is the SSB, the protection period may be included in the second duration, and after the reception of the SSB is terminated, the second data may not be sent before the protection period included in the second duration.

[0017] Furthermore, in the method according to the embodiment of the present disclosure, the configuration information may include information related to the protection period.

[0018] In addition, in the method according to the embodiment of the present disclosure, based on the information related to the protection period, the protection period can be configured i) for each SCS or ii) for each frequency range.

[0019] In addition, in the method according to an embodiment of the present disclosure, a second value as a protection period corresponding to another SCS can be determined based on a first value as a protection period corresponding to a reference SCS, and the ratio of another SCS to the reference SCS can be equal to the ratio of the second value to the first value.

[0020] Furthermore, in the method according to the embodiment of the present disclosure, the protection period may include a switching time from the first duration to the second duration.

[0021] In addition, the method according to an embodiment of the present disclosure may further include sending capability information related to the switching time.

[0022] Furthermore, in the method according to an embodiment of the present disclosure, when the first direction is a downlink, the second direction may be an uplink, and when the first direction is the uplink, the second direction may be the downlink.

[0023] According to an embodiment of the present disclosure, a user equipment (UE) that sends and receives data in a wireless communication system that supports half-duplex frequency division duplex may include: one or more transceivers; one or more processors; and one or more memories, wherein the one or more memories store instructions for operations performed by the one or more processors and are connected to the one or more processors, wherein the operations may include: receiving configuration information through higher layer signaling; receiving downlink control information (DCI), wherein (i) a first duration for transmitting first data in a first direction, and (ii) a second duration for transmitting second data in a second direction opposite to the first direction are configured based on at least one of the configuration information or the DCI; and based on the first direction and the second direction being opposite to each other, performing switching from the first duration to the second duration, wherein the priority of the first data and the second data can be determined based on a predefined rule, and wherein a protection period required for the switching can be included in the duration for transmitting data with a lower priority in the first duration or the second duration.

[0024] In a device, comprising: one or more memories and one or more processors functionally connected to the one or more memories, the one or more processors can be configured to control the device to: receive configuration information through higher layer signaling; receive downlink control information (DCI), and configure (i) a first duration for transmitting first data in a first direction, and (ii) a second duration for transmitting second data in a second direction opposite to the first direction based on the configuration information or at least one of the DCI; and perform switching from the first duration to the second duration based on the first direction and the second direction being opposite to each other, wherein the priorities of the first data and the second data are determined based on a predefined rule, and a protection period required for the switching is included in the duration for transmitting data with a lower priority in the first duration or the second duration.

[0025] In one or more non-transitory computer-readable media storing one or more instructions, the one or more instructions executable by one or more processors may include instructions for instructing a user equipment (UE) to perform the following operations: receiving configuration information through higher layer signaling; receiving downlink control information (DCI), and wherein, based on the configuration information or at least one of the DCI, configuring (i) a first duration for transmitting first data in a first direction, and (ii) a second duration for transmitting second data in a second direction opposite to the first direction; and performing switching from the first duration to the second duration based on the first direction and the second direction being opposite to each other, wherein the priority of the first data and the second data can be determined based on a predefined rule, and a protection period required for the switching can be included in the duration for transmitting data with a lower priority in the first duration or the second duration.

[0026] According to an exemplary embodiment of the present disclosure, a method for sending and receiving data by a base station in a wireless communication system supporting half-duplex frequency division duplex may include: sending configuration information through higher layer signaling; and sending downlink control information (DCI), wherein (i) a first duration for transmitting first data in a first direction, and (ii) a second duration for transmitting second data in a second direction opposite to the first direction are configured based on the configuration information or at least one of the DCI; and based on the first direction and the second direction being opposite to each other, performing switching from the first duration to the second duration, wherein the priority of the first data and the second data can be determined based on a predefined rule, and the duration for transmitting data with a lower priority within the first duration or the second duration can include a protection period required for the switching.

[0027] According to an exemplary embodiment of the present disclosure, a base station for sending and receiving data in a wireless communication system supporting half-duplex frequency division duplex may include: one or more transceivers; one or more processors; and one or more memories, wherein the one or more memories store instructions for operations performed by the one or more processors and are connected to the one or more processors, wherein the operations may include: sending configuration information through higher layer signaling; and sending downlink control information (DCI), wherein (i) a first duration for transmitting first data in a first direction and (ii) a second duration for transmitting second data in a second direction opposite to the first direction are configured based on at least one of the configuration information or the DCI; and based on the first direction and the second direction being opposite to each other, performing switching from the first duration to the second duration, wherein the priority of the first data and the second data can be determined based on a predefined rule, and a protection period required for the switching can be included in the duration for transmitting data with a lower priority in the first duration or the second duration.

[0028] Beneficial Effects

[0029] According to an embodiment of the present disclosure, it is possible to transmit or receive data in a wireless communication system supporting half-duplex frequency division duplex (FDD).

[0030] Furthermore, according to an embodiment of the present disclosure, a time slot format can be configured for a half-duplex FDD operation, and a switching time for switching from a downlink to an uplink or from an uplink to a downlink can be configured.

[0031] Furthermore, according to an embodiment of the present disclosure, a guard period for switching from a downlink to an uplink or from an uplink to a downlink can be configured for a half-duplex FDD operation.

[0032] Furthermore, according to the embodiments of the present disclosure, it is possible to prevent link direction conflicts in a half-duplex FDD operation.

[0033] Effects that can be obtained from the present disclosure are not limited to the above-mentioned effects, and other effects that are not mentioned can be clearly understood from the following description by those skilled in the art to which the present disclosure pertains. BRIEF DESCRIPTION OF THE DRAWINGS

[0034] The accompanying drawings, which are included to provide a further understanding of the disclosure and are incorporated in and constitute a part of this disclosure, illustrate embodiments of the disclosure and together with the description serve to explain the principle of the disclosure.

[0035] Figure 1is a diagram illustrating an example of an overall system structure of a NR to which the method proposed in the present disclosure can be applied.

[0036] Figure 2 The diagram illustrates the relationship between an uplink frame and a downlink frame in a wireless communication system to which the method proposed in the present disclosure can be applied.

[0037] Figure 3 An example of a frame structure in an NR system is illustrated.

[0038] Figure 4 An example of a resource grid supported by a wireless communication system to which the method proposed in the present disclosure can be applied is illustrated.

[0039] Figure 5 An example of a resource grid for each antenna port and parameter set to which the method proposed in the present disclosure can be applied is illustrated.

[0040] Figure 6 The diagram illustrates physical channels and general signal transmission in a 3GPP system.

[0041] Figure 7 An example of a signaling flow chart between a UE and a BS to which the methods and / or embodiments proposed in the present disclosure can be applied is illustrated.

[0042] Figure 8 An example of an operation flow chart of a UE that performs transmission or reception of data to which the methods and / or embodiments proposed in the present disclosure may be applied is illustrated.

[0043] Fig. 9 A communication system (1) applied to the present disclosure is illustrated.

[0044] Fig.10 A wireless device to which the present disclosure may be applied is illustrated.

[0045] Fig.11 The signal processing circuit for transmitting the signal is shown.

[0046] Fig.12 Another example of a wireless device to which the present disclosure is applied is illustrated.

[0047] Fig.13 A portable device to which the present disclosure is applied is illustrated. DETAILED DESCRIPTION

[0048] Reference will now be made in detail to embodiments of the present disclosure, examples of which are illustrated in the accompanying drawings. Figure 1The detailed description disclosed above is intended to describe exemplary embodiments of the present disclosure, rather than to describe the only embodiment for performing the present disclosure. The following detailed description includes details to provide a complete understanding of the present disclosure. However, those skilled in the art will appreciate that the present disclosure may be performed without the details.

[0049] In some cases, in order to prevent the concepts of the present disclosure from being unclear, known structures and devices may be omitted or illustrated in the form of block diagrams based on the core functions of each structure and device.

[0050] In the following, downlink (DL) refers to communication from a base station to a terminal, and uplink (UL) refers to communication from a terminal to a base station. In the downlink, the transmitter may be part of a base station, and the receiver may be part of a terminal. In the uplink, the transmitter may be part of a terminal, and the receiver may be part of a base station. The base station may be expressed as a first communication device, and the terminal may be expressed as a second communication device. The following terms may be used instead of a base station (BS), including: fixed station, Node B (Node B), evolved Node B (eNB), next generation Node B (gNB), base transceiver system (BTS), access point (AP), network (5G network), AI system, roadside unit (RSU), vehicle, robot, unmanned aerial vehicle (UAV), AR (augmented reality) device, VR (virtual reality) device, and the like. In addition, the terminal may be fixed or mobile and may be replaced by the following terms, including: user equipment (UE), mobile station (MS), user terminal (UT), mobile subscriber station (MSS), subscriber station (SS), advanced mobile station (AMS), wireless terminal (WT), machine type communication (MTC) device, machine-to-machine (M2M) device and device-to-device (D2D) device, vehicle, robot, AI module, unmanned aerial vehicle (UAV), AR (augmented reality) device, VR (virtual reality) device, etc.

[0051] The following techniques may be used in various radio access systems including CDMA, FDMA, TDMA, OFDMA, SC-FDMA, etc. CDMA may be implemented as a radio technology such as Universal Terrestrial Radio Access (UTRA) or CDMA2000. TDMA may be implemented as a radio technology such as Global System for Mobile Communications (GSM) / General Packet Radio Service (GPRS) / Enhanced Data Rate for GSM Evolution (EDGE). OFDMA may be implemented as a radio technology such as Institute of Electrical and Electronics Engineers (IEEE) 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, Evolved UTRA (E-UTRA), etc. UTRA is part of Universal Mobile Telecommunications System (UMTS). The 3rd Generation Partnership Project (3GPP) Long Term Evolution (LTE) is part of Evolved UMTS (E-UMTS) using E-UTRA, and Advanced LTE (A) / LTE-A pro is an evolved version of 3GPP LTE. 3GPP NR (New Radio or New Radio Access Technology) is an evolved version of 3GPP LTE / LTE-A / LTE-A pro.

[0052] For the sake of clarity of description, the technical spirit of the present disclosure is described based on a 3GPP communication system (e.g., LTE-A or NR), but the technical spirit of the present disclosure is not limited thereto. LTE refers to the technology after 3GPP TS 36.xxx version 8. In detail, the LTE technology after 3GPP TS 36.xxx version 10 is called LTE-A, and the LTE technology after 3GPP TS 36.xxx version 13 is called LTE-A pro. 3GPP NR refers to the technology after TS 38.xxx version 15. LTE / NR can be referred to as a 3GPP system. "xxx" refers to the detailed number of the standard document. LTE / NR can be collectively referred to as a 3GPP system. Matters disclosed in the standard documents opened in the present disclosure can be cited for the background technology, terms, abbreviations, etc. used to describe the present disclosure. For example, the following documents can be referenced.

[0053] 3GPP LTE

[0054] -36.211: Physical channels and modulation

[0055] -36.212: Multiplexing and channel coding

[0056] -36.213: Physical layer procedures

[0057] -36.300: General description

[0058] -36.331: Radio Resource Control (RRC)

[0059] 3GPP NR

[0060] -38.211: Physical channels and modulation

[0061] -38.212: Multiplexing and channel coding

[0062] -38.213: Physical layer procedures for control

[0063] -38.214: Physical layer procedures for data

[0064] -38.300: NR and NG-RAN general description

[0065] -38.331: Radio Resource Control (RRC) protocol specification

[0066] As more and more communication devices require greater communication capacity, there is a need for improved mobile broadband communications compared to existing radio access technologies (RATs). In addition, large-scale machine type communications (MTC), which provide various services anytime and anywhere by connecting many devices and objects, is one of the main issues to be considered in next-generation communications. In addition, the design of communication systems considering services / UEs that are sensitive to reliability and latency is being discussed. The introduction of next-generation radio access technologies considering enhanced mobile broadband communications (eMBB), massive MTC (mMTC), and ultra-reliable low-latency communications (URLLC) is discussed, and in this disclosure, for convenience, the technology is referred to as a new RAT. NR is an expression representing an example of a 5G radio access technology (RAT).

[0067] The three main demand areas of 5G include: (1) enhanced mobile broadband (eMBB), (2) massive machine type communication (mMTC), and (3) ultra-reliable low-latency communication (URLLC).

[0068] Some use cases may require optimization of multiple areas, while others may focus on just one key performance indicator (KPI). 5G supports a variety of use cases in a flexible and reliable manner.

[0069] eMBB goes far beyond basic mobile Internet access and covers a large number of two-way tasks, media and entertainment applications in the cloud or augmented reality. Data is one of the main drivers of 5G, and dedicated voice services may not appear in the 5G era for the first time. In 5G, it is expected that voice will be processed as an application using a data connection simply provided by the communication system. The main reasons for the increase in traffic include the increase in content size and the increase in the number of applications that require high data transfer rates. As more and more devices are connected to the Internet, streaming services (audio and video), conversational video and mobile Internet connections will be more widely used. So many applications require always-on connections to push real-time information and notifications to users. Cloud storage and applications have suddenly increased in mobile communication platforms, and this can be applied to both business and entertainment. In addition, cloud storage is a special use case that drives the growth of uplink data transfer rates. 5G is also used for remote services in the cloud. When using tactile interfaces, lower end-to-end latency is required to maintain an excellent user experience. Entertainment, for example, cloud gaming and video streaming are other key elements that increase the demand for mobile broadband capabilities. Entertainment is essential in smartphones and tablets anywhere in high mobility environments including trains, vehicles and airplanes. Another use case is augmented reality and information search for entertainment. In this case, augmented reality requires extremely low latency and instant data volume.

[0070] Furthermore, one of the most anticipated 5G use cases involves a capability that smoothly connects embedded sensors in all areas, namely mMTC. By 2020, it is expected that the potential number of Internet of Things (IoT) devices will reach 20.4 billion. Industrial IoT is one of the areas where 5G will play a major role, enabling smart cities, asset tracking, smart utilities, agriculture, and security infrastructure.

[0071] URLLC includes a new service that will transform industries through remote control of critical infrastructure and ultra-high reliability / low availability latency links, such as autonomous vehicles. The level of reliability and latency is critical for smart grid control, industrial automation, robotics, drone control and regulation.

[0072] Describe multiple use cases in more detail.

[0073] 5G can complement fiber to the home (FTTH) and cable-based broadband (or DOCSIS) as a means of delivering streams rated from gigabits per second to hundreds of megabits per second. Such fast speeds are also necessary for delivering television with a resolution of 4K or higher (6K, 8K or higher), in addition to virtual reality and augmented reality. Virtual reality (VR) and augmented reality (AR) applications include immersive sports gaming. Specific applications may require special network configurations. For example, in the case of VR gaming, in order for gaming companies to minimize latency, it may be necessary to integrate the core server with the network operator's edge network server.

[0074] Along with the numerous use cases for automotive mobile communications, cars are expected to be an important and new driver of 5G. For example, the entertainment of passengers requires both high-capacity and high-mobility mobile broadband. The reason for this is that users in the future will continue to expect high-quality connections regardless of their location and speed. Another example of use in the automotive field is an augmented reality dashboard. The augmented reality dashboard overlays and displays information on what the driver sees through the front window, identifies objects in the dark, and informs the driver of the distance and movement of the object. In the future, wireless modules will enable communication between cars, information exchange between cars and supporting infrastructure, and information exchange between cars and other connected devices (e.g., those accompanying pedestrians). Safety systems guide the course of action available so that drivers can drive more safely, reducing the risk of accidents. The next step will be remotely controlled or autonomous vehicles. This requires very reliable and very fast communication between different autonomous vehicles and between cars and infrastructure. In the future, autonomous vehicles may perform all driving activities, and the driver will focus on things outside of traffic that the car itself cannot recognize. The technical requirements of autonomous vehicles require ultra-low latency and ultra-high-speed reliability, which increases traffic safety to a level that humans cannot achieve.

[0075] The smart cities and smart homes mentioned in the smart society will be embedded as high-density radio sensor networks. Distributed networks of smart sensors will identify the cost of cities or homes and the status of energy-saving maintenance. Similar configurations can be performed for each home. All temperature sensors, window and heating controllers, burglar alarms and household appliances are wirelessly connected. Many of these sensors are usually low data transmission rate, low power consumption and low cost. However, for example, a specific type of surveillance equipment may require real-time high-definition video.

[0076] The consumption and distribution of energy, including heat or gas, is highly decentralized and therefore requires automated control of a distributed sensor network. Smart grids collect information and interconnect these sensors using digital information and communication technologies so that the sensors act based on the information. This information can include the behavior of suppliers and consumers, and thus smart grids can improve the distribution of fuels such as electricity in an efficient, reliable, economical, sustainable and automated manner. Smart grids can be considered as another sensor network with small latency.

[0077] The health sector has many applications that benefit from mobile communications. Communication systems can support telemedicine, which provides clinical treatment in distant locations. This helps reduce the barrier of distance and can improve access to discontinuous medical services in remote agricultural areas. Furthermore, this can be used to save lives during critical treatments and emergencies. Radio sensor networks based on mobile communications can provide remote monitoring and sensors for parameters such as heart rate and blood pressure.

[0078] Radio and mobile communications are becoming increasingly important in industrial applications. Cabling requires high installation and maintenance costs. Therefore, the possibility of replacing cables by reconfigurable radio links is an attractive opportunity in many industrial fields. However, in order to realize this possibility, radio connections are required to operate with latency, reliability and capacity similar to cables, and management is simplified. Low latency and low error probability are new requirements for connecting 5G.

[0079] Logistics and freight tracking are important use cases for mobile communications, which enable tracking of inventory and packages anywhere using location-based information systems. Logistics and freight tracking use cases typically require lower data speeds, but require wide areas and reliable location information.

[0080] In the new RAT system including NR, an OFDM transmission scheme or a transmission scheme similar thereto is used. The new RAT system may follow OFDM parameters different from those of LTE. Alternatively, the new RAT system may follow the parameter set of conventional LTE / LTE-A as is or have a larger system bandwidth (e.g., 100 MHz). Alternatively, one cell may support multiple parameter sets. In other words, UEs operating with different parameter sets may coexist in one cell.

[0081] A parameter set corresponds to one subcarrier spacing in the frequency domain. Different parameter sets can be defined by scaling the reference subcarrier spacing to an integer N.

[0082] Definition of terms

[0083] eLTE eNB: eLTE eNB is the evolution of eNB that supports connectivity to EPC and NGC.

[0084] gNB: A node that supports NR and connectivity to NGC.

[0085] New RAN: A radio access network that supports NR or E-UTRA or interfaces with NGC.

[0086] Network slicing: Network slicing refers to a network customized by an operator to provide optimized solutions for specific market scenarios with specific requirements within an end-to-end scope.

[0087] Network Function: A network function is a logical node in a network architecture that has a well-defined external interface and a well-defined functional behavior.

[0088] NG-C: The control plane interface used over the NG2 reference point between the New RAN and NGC.

[0089] NG-U: User plane interface used over the NG3 reference point between the New RAN and NGC.

[0090] Non-Standalone NR: A deployment configuration where the gNB requires an LTE eNB as an anchor for control plane connectivity to the EPC, or requires an eLTE eNB as an anchor for control plane connectivity to the NGC.

[0091] Non-Standalone E-UTRA: A deployment configuration where the eLTE eNB requires the gNB as the anchor for control plane connectivity to the NGC.

[0092] User plane gateway: the termination point of the NG-U interface.

[0093] System Overview

[0094] Figure 1 An example of the overall structure of an NR system to which the method proposed in the present disclosure can be applied is illustrated.

[0095] refer to Figure 1 NG-RAN is composed of gNB, which provides NG-RA user plane (new AS sublayer / PDCP / RLC / MAC / PHY) and control plane (RRC) protocol ends for user equipment (UE).

[0096] The gNBs are interconnected via the Xn interface.

[0097] The gNB is also connected to the NGC via the NG interface.

[0098] More specifically, the gNB is connected to the Access and Mobility Management Function (AMF) via the N2 interface and to the User Plane Function (UPF) via the N3 interface.

[0099] New RAT (NR) parameter set and frame structure

[0100] In NR systems, multiple parameter sets can be supported. The parameter set can be defined by subcarrier spacing and CP (cyclic prefix) overhead. The spacing between multiple subcarriers can be derived by scaling the basic subcarrier spacing to an integer N (or μ). In addition, although it is assumed that very low subcarrier spacing is not used at very high subcarrier frequencies, the parameter set to be used can be selected independently of the frequency band.

[0101] In addition, in the NR system, multiple frame structures based on multiple parameter sets can be supported.

[0102] Hereinafter, an Orthogonal Frequency Division Multiplexing (OFDM) parameter set and a frame structure that can be considered in the NR system will be described.

[0103] Multiple OFDM parameter sets supported in the NR system can be defined as shown in Table 1.

[0104] [Table 1]

[0105] μ <![CDATA[△f=2 μ ·15[kHz]]]> Cyclic prefix 0 15 Normal 1 30 Normal 2 60 Normal, extended 3 120 Normal 4 240 Normal

[0106] NR supports multiple parameter sets (or subcarrier spacing (SCS)) to support various 5G services. For example, when the SCS is 15kHz, it supports wide areas in the traditional cellular band; when the SCS is 30kHz / 60kHz, it supports dense cities, lower latency and wider carrier bandwidth; and when the SCS is 60kHz or higher, it supports bandwidth greater than 24.25GHz to overcome phase noise.

[0107] The NR band is defined as two types of frequency ranges (FR1 and FR2). FR1 and FR2 can be configured as shown in the following Table 2. In addition, FR2 may mean millimeter wave (mmW).

[0108] [Table 2]

[0109] Frequency range specification Corresponding frequency range Subcarrier spacing FR1 410MHz–7125MHz 15, 30, 60kHz FR2 24250MHz–52600MHz 60, 120, 240kHz

[0110] Regarding the frame structure in the NR system, the size of each field in the time domain is expressed as T s =1 / (△f max ·N f ) time unit. In this case, △f max =480·10 3 And N f=4096. DL and UL transmissions are configured with T f =(△f max N f / 100)·T s = A portion of a radio frame of 10 ms. A radio frame consists of ten subframes, each with T sf =(△f max N f / 1000)·T s = a portion of 1 ms. In this case, there may be a UL frame set and a DL frame set.

[0111] Figure 2 The diagram illustrates a relationship between an uplink frame and a downlink frame in a wireless communication system to which the method proposed in the present disclosure is applicable.

[0112] like Figure 2 As illustrated in FIG. 1 , an uplink frame number i for transmission from a user equipment (UE) should start T before the start of the corresponding downlink frame at the corresponding UE. TA =N TA T s .

[0113] Regarding parameter set μ, the slots are in ascending order within a subframe. Numbered and in ascending order within a radio frame A time slot consists of Consecutive OFDM symbols, and Determined by the parameter set and time slot configuration used. Time slot in a subframe The beginning of the OFDM symbol in the same subframe The start of is aligned in time.

[0114] Not all UEs are capable of transmitting and receiving at the same time, and this means that not all OFDM symbols in a downlink time slot or an uplink time slot may be used.

[0115] Table 3 shows the number of OFDM symbols per time slot in a normal CP Number of slots per radio frame and the number of time slots per subframe Table 4 shows the number of OFDM symbols per slot in the extended CP, the number of slots per radio frame, and the number of slots per subframe.

[0116] [Table 3]

[0117]

[0118] [Table 4]

[0119]

[0120] Figure 3 An example of a frame structure in an NR system is illustrated. Figure 3 It is only for the convenience of explanation and does not limit the scope of the present disclosure.

[0121] In Table 4, in the case of μ=2, that is, as an example of a subcarrier spacing (SCS) of 60 kHz, referring to Table 3, one subframe (or frame) may include four time slots, and Figure 3 One subframe = {1, 2, 4} slots as shown in , for example, the number of slots that can be included in one subframe is defined in Table 3.

[0122] Furthermore, a mini-slot may consist of 2, 4, or 7 symbols, or may consist of more or fewer symbols.

[0123] Regarding the physical resources in the NR system, we can consider antenna ports, resource grids, resource elements, resource blocks, carrier parts, etc.

[0124] In the following, the above-mentioned physical resources that can be considered in the NR system are described in more detail.

[0125] First, with respect to antenna ports, the antenna ports are defined so that the channel on which the symbol of the antenna port can be transmitted can be inferred from the channel on which another symbol on the same antenna port is transmitted. When the large-scale properties of the channel on which the symbol on one antenna port is transmitted can be inferred from the channel on which the symbol on another antenna port is transmitted, the two antenna ports can be regarded as a quasi-co-located or quasi-co-located (QC / QCL) relationship. In this case, the large-scale properties include at least one of the following: delay spread, Doppler spread, frequency shift, average received power, and receive timing.

[0126] Figure 4 An example of a resource grid supported in a wireless communication system to which the method proposed in the present disclosure is applicable is illustrated.

[0127] refer to Figure 4 , the resource grid is composed of subcarriers, each subframe consists of 14·2 μ OFDM symbols, but the present disclosure is not limited thereto.

[0128] In NR systems, the transmitted signal is described by one or more resource grids. subcarriers and OFDM symbols, where Indicates the maximum transmission bandwidth and can change not only between parameter sets, but also between uplink and downlink.

[0129] In this case, if Figure 5 As illustrated in , each parameter set μ and antenna port p can configure a resource grid.

[0130] Figure 5 An example of a resource grid for each antenna port and parameter set to which the method proposed in the present disclosure is applicable is illustrated.

[0131] Each element of the resource grid for a parameter set μ and an antenna port p is called a resource element and is referenced by an index Unique identifier, where is an index in the frequency domain, and The index pair (k, l) is used to reference the resource element in the time slot, where

[0132] Resource elements of parameter set μ and antenna port p Corresponds to complex value If there is no risk of aliasing, or when no particular antenna port or parameter set is specified, then the indices p and μ may be dropped, and as a result, the complex value may be or

[0133] In addition, a physical resource block is defined as consecutive subcarriers.

[0134] Point A is used as a common reference point for the resource block grid and can be obtained as follows.

[0135] - offsetToPointA for PCell downlink represents the frequency offset between point A and the lowest subcarrier of the lowest resource block, which overlaps the SS / PBCH block used by the UE for initial cell selection, and is expressed in units of resource blocks, where the subcarrier spacing for FR1 is assumed to be 15 kHz and the subcarrier spacing for FR2 is assumed to be 60 kHz;

[0136] -absoluteFrequencyPointA represents the frequency position of point A, expressed as an absolute radio frequency channel number (ARFCN).

[0137] Common resource blocks are numbered from 0 upwards in the frequency domain for a subcarrier spacing configuration of μ.

[0138] The center of subcarrier 0 of common resource block 0 for subcarrier spacing configuration μ coincides with "point A". The common resource block number in the frequency domain can be given by the following equation 1 and resource elements (k, l) for subcarrier spacing configuration μ.

[0139] [Equation 1]

[0140]

[0141] Here, k can be defined relative to point A, so that k=0 corresponds to a subcarrier centered at point A. Physical resource blocks are defined within bandwidth parts (BWPs) and are spaced from 0 to Number, where i is the number of the BWP. The physical resource blocks in BWP i n PRB and Common Resource Block n The relationship between CRBs can be given by the following Equation 2.

[0142] [Equation 2]

[0143]

[0144] Here, It can be a common resource block where the BWP starts relative to common resource block 0.

[0145] Bandwidth Part (BWP)

[0146] The NR system can support up to 400MHz per carrier. If a UE operating in a wideband CC operates while turning on the radio frequency (RF) module continuously for all CCs, the UE battery consumption may increase. Alternatively, when considering several use cases operating in one wideband CC (e.g., eMBB, URLLC, mMTC, V2X, etc.), different parameter sets (e.g., subcarrier spacing) may be supported for each frequency band in the corresponding CC. Alternatively, the maximum bandwidth capability for each UE may vary. By consideration, the BS can instruct the UE to operate only in part of the bandwidth instead of the entire bandwidth of the wideband CC and the part of the bandwidth is called a bandwidth part (BWP). In the frequency domain, a BWP is a subset of contiguous common resource blocks defined for a parameter set μi within a bandwidth part i on a CC, and a parameter set (e.g., subcarrier spacing, CP length, slot / microslot duration) may be configured.

[0147] Meanwhile, the BS may configure one or more BWPs within one CC configured to the UE. Alternatively, when the UEs are concentrated on a specific BWP, some UEs may be configured to other BWPs for load balancing. Alternatively, considering frequency domain inter-cell interference elimination between adjacent cells, part of the spectrum in the middle of the entire bandwidth may be excluded and BWPs on both sides may be configured even in the same time slot. That is, the BS may configure at least one DL / UL BWP to the UE associated with the wideband CC and may activate at least one DL / UL BWP among (one or more) DL / UL BWPs configured at a specific time point (L1 signaling as a physical layer control signal and MAC control element (CE) as a MAC layer control signal), instruct (through L1 signaling, MAC CE or RRC signaling) to switch at least one DL / UL BWP to another configured DL / UL BWP, or configure a timer value to allow the UE to switch to the determined DL / UL BWP when the timer expires. The activated DL / UL BWP is particularly referred to as an active DL / UL BWP. In the case where the UE is in the initial access procedure or before the UE's RRC connection is established, the UE may not receive the configuration of the DL / UL BWP. In this case, the DL / UL BWP assumed by the UE is called the initial active DL / UL BWP.

[0148] Physical channels and general signal transmission

[0149] Figure 6 The figure illustrates physical channels and general signal transmission used in the 3GPP system. In a wireless communication system, a UE receives information from an eNB through a downlink (DL), and the UE transmits information from the eNB through an uplink (UL). The information transmitted and received by the eNB and the UE includes data and various control information, and there are various physical channels according to the type / purpose of the information transmitted and received by the eNB and the UE.

[0150] When the UE is powered on or newly enters a cell, the UE performs an initial cell search operation (S601), such as synchronization with an eNB. To this end, the UE may receive a primary synchronization signal (PSS) and (a secondary synchronization signal (SSS)) from the eNB, synchronize with the eNB, and acquire information such as a cell ID. Thereafter, the UE may receive a physical broadcast channel (PBCH) from the eNB and acquire intra-cell broadcast information. At the same time, the UE receives a downlink reference signal (DL RS) in the initial cell search step to check the downlink channel status.

[0151] The UE that has completed the initial cell search acquires more specific system information by receiving a physical downlink control channel (PDCCH) and a physical downlink shared channel (PDSCH) according to information loaded on the PDCCH (S602).

[0152] Meanwhile, when there is no radio resource for first accessing the eNB or for signal transmission, the UE may perform a random access procedure (RACH) to the eNB (S603 to S606). To this end, the UE may send a specific sequence to the preamble through the physical random access channel (PRACH) (S603 and S605), and receive a response message (random access response (RAR) message) for the preamble through the PDCCH and the corresponding PDSCH. In the case of a contention-based RACH, a contention resolution procedure (S606) may be additionally performed.

[0153] Then, the UE performing the above process may perform PDCCH / PDSCH reception (S607) and physical uplink shared channel (PUSCH) / physical uplink control channel (PUCCH) transmission (S608) as a general uplink / downlink signal transmission process. In particular, the UE may receive downlink control information (DCI) through the PDCCH. Here, the DCI may include control information such as resource allocation information for the UE, and the format may be applied differently depending on the purpose of use.

[0154] Specifically, the UE monitors a set of PDCCH candidates in the monitoring opportunities configured in one or more control element sets (CORESETs) on the serving cell according to the search space configuration. The set of PDCCH candidates to be monitored by the UE can be defined in terms of a search space set, and the search space set can be a common search space set or a UE-specific search space set. A CORESET consists of a set of (physical) resource blocks with a duration of 1 to 3 OFDM symbols. The network can configure the UE to have multiple CORESETs. The UE monitors PDCCH candidates in one or more search space sets. Here, monitoring means attempting to decode (one or more) PDCCH candidates in the search space. When the UE successfully decodes one of the PDCCH candidates in the search space, the UE determines that a PDCCH is detected in the PDCCH candidate, and performs PDSCH reception or PUSCH transmission based on the DCI within the detected PDCCH.

[0155] PDCCH can be used to schedule DL transmission on PDSCH and UL transmission on PUSCH. Here, the DCI on PDCCH includes downlink assignment and uplink grant, the downlink assignment includes at least modulation and coding format and resource allocation information related to PDSCH, and the uplink grant includes modulation and coding format and resource allocation information related to PUSCH. The format of DCI changes according to the purpose of use of DCI. For example, in the NR system, DCI format 00 and DCI format 01 are used to schedule PUSCH in a cell, and DCI format 10 and DCI format 11 are used to schedule PDSCH in a cell. DCI format 20 can be CRC-scrambled by SFI-RNTI and is used to announce the time slot format.

[0156] The description (e.g., 3GPP system, frame structure, physical channel, and general signal transmission) may be applied / used in conjunction with the method and / or embodiment proposed in the present disclosure, or may be supplemented to clarify the technical features of the method proposed in the present disclosure. In the present disclosure, " / " may mean including all contents distinguished by / (and) or only including some distinguished contents (or).

[0157] Furthermore, in the present disclosure, for the convenience of description, the following terms may be expressed using abbreviations.

[0158] -UE: User Equipment

[0159] -redcap UE: Reduced capacity UE

[0160] -SSB: Synchronization Signal Block

[0161] -BW: Bandwidth

[0162] -BWP: Bandwidth Part

[0163] -SCS: Subcarrier Spacing

[0164] -TB: Transfer Block

[0165] -TDRA: Time Domain Resource Allocation

[0166] -RO: RACH timing

[0167] -MG: Measuring gap

[0168] -DL: Downlink

[0169] -UL: Uplink

[0170] -Rx: Receive

[0171] -Tx: Transmission

[0172] -FR: Frequency range

[0173] -PDCCH: Physical Downlink Control Channel

[0174] -PDSCH: Physical Downlink Shared Channel

[0175] -PUCCH: Physical Uplink Control Channel

[0176] -PUSCH: Physical Uplink Shared Channel

[0177] -RNTI: Radio Network Temporary Identifier

[0178] -RRC: Radio Resource Control

[0179] -MAC-CE: Media Access Control-Control Element

[0180] -DCI: Downlink Control Information

[0181] -FDD: Frequency Division Duplex

[0182] -SI-RNTI: System Information Radio-Network Temporary Identifier

[0183] -CRC: Cyclic Redundancy Check

[0184] -SIB: System Information Block

[0185] -SIB1: SIB1 = Remaining Minimum System Information (RMSI) for NR devices. Broadcasts the information required for cell access by NR devices.

[0186] - CORESET (Control Resource Set): Time / frequency resources where the NR UE attempts candidate PDCCH decoding

[0187] -CORESET#0: CORESET of Type0-PDCCH CSS set for NR devices

[0188] -MO: PDCCH monitoring opportunity for Type0-PDCCH CSS set

[0189] - SIB1-R: (Additional) SIB1 for NR devices with reduced capabilities. SIB1-R may be limited to the case where SIB1 is generated as a separate TB and sent to a separate PDSCH.

[0190] -CORESET#0-R: CORESET#0 for NR devices with reduced capabilities

[0191] -Type0-PDCCH-R CSS set: Search space set where the UE monitors the set of PDCCH candidates for DCI format scrambled by SI-RNTI CRC

[0192] -MO-R: PDCCH monitoring opportunity for Type0-PDCCH-R CSS set

[0193] -RSA (Standalone Redcap): Only supports Redcap devices or cells served by Redcap.

[0194] In addition to the above-mentioned key use cases of 5G (e.g., mMTC, eMBB, and URLLC), the importance / interest of use cases such as a use case combining mMTC and eMBB or a use case combining mMTC and URLLC is increasing. In order to effectively support the use cases, a method for designing a UE suitable for the use case is considered in terms of device cost, power consumption, form factor, etc.

[0195] In this disclosure, a normal (NR) UE that supports at least one key use case of 5G will be denoted as an “NR UE” or an “NR device.” The NR UE may have all 5G key capabilities (e.g., peak data rate, user experienced data rate, latency, mobility, connection density, energy efficiency, spectrum efficiency, and area traffic efficiency).

[0196] In contrast, a UE that intentionally reduces some capabilities in order to achieve device cost reduction, power consumption savings, and compact form factor will be referred to as a (NR) reduced capability UE / reduced capability device, or abbreviated and referred to as a (NR) "redcap UE" or "redcap device". A redcap UE may be designed with the intent of spanning use case areas of mMTC and eMBB or mMTC and URLLC.

[0197] In addition, in this disclosure, for ease of description, the 5G use case areas across mMTC and eMBB or mMTC and URLLC will be referred to as “redcap use cases” for convenience.

[0198] As an example of a redcap use case, consider the connected industry sector. Sensors and actuators can be connected to the 5G network and the core. Large-scale industrial wireless sensor network (IWSN) use cases and requirements can be included. In addition to the very demanding URLLC, relatively low-end services that require compact device form factors with a battery life of several years can also be provided. The requirements of the services are higher than low power wide area (LPWA) (i.e., LTE-M / NB-IOT), but lower than URLLC and eMBB. For example, devices supporting this environment may include pressure sensors, humidity sensors, thermometers, motion sensors, accelerometers, actuators, etc.

[0199] As another example of a redcap use case, in the case of smart cities, the smart city vertical monitors and controls city resources more efficiently and covers data collection and processing for providing services to city residents. In particular, the deployment of surveillance cameras is an essential part of smart cities, and even in factories and industries.

[0200] As yet another example of redcap use cases, wearable use cases may include smart clocks, rings, smart health (eHealth) related devices, and medical monitoring devices.

[0201] Low-power wireless area (LPWA) UEs (e.g., LTE-M, NB-IoT, etc.) cannot support redcap use cases in terms of bit rate, latency, etc. On the contrary, NR UEs can functionally support redcap use cases, but may be inefficient in terms of UE manufacturing cost, form factor, battery life, etc. Supporting redcap use case areas in 5G networks through redcap UEs with characteristics such as low cost, low power, compact form factor (i.e., small size of the device), etc., can achieve the effect of saving UE manufacturing and maintenance costs.

[0202] Redcap use cases have significantly different requirements in terms of UE complexity, target bit rate, latency, power consumption, etc. In this disclosure, the requirements that a redcap UE should meet will be referred to as "redcap requirements". Redcap requirements can be classified into common requirements that can generally be applied to all redcap use cases, and use case specific requirements that only apply to some use cases.

[0203] For example, the generic redcap requirements can be summarized as follows.

[0204] - Equipment complexity / cost: The key motivation for the new equipment types is to reduce equipment cost and complexity by comparing with high-end eMBB and URLLC equipment of Rel-15 / Rel-16. This is particularly relevant to industrial sensors.

[0205] - Device size: The requirement for most use cases is for the device design to have a compact form factor as a standard.

[0206] -Deployment scenarios: The system should support all FR1 / FR2 bands for FDD and TDD.

[0207] For example, the use case specific redcap requirements can be summarized as follows.

[0208] <Use Case 1: Industrial Wireless Sensors>

[0209] -Reference bit rate: <2Mbps (UL traffic is potentially heavy (heavy traffic))

[0210] - End-to-end latency: <100ms; ~5 to 10ms for safety-related sensors

[0211] -Battery: at least several years

[0212] -Communication service availability: 99.99%

[0213] - Fixed <Use Case 2: Video Surveillance>

[0214] -Reference bitrate: <2 to 4Mbps for economy video; ~7.5 to 25Mbps for high-end video (UL heavy traffic)

[0215] - Latency: <500ms

[0216] - Reliability: 99% - 99.9%.

[0217] <Use Case 3: Wearable Devices>

[0218] - Reference bit rate: 10 to 50 Mbps in downlink and >= 5 Mbps in uplink for smart wearable applications

[0219] - Peak bit rate: 150Mbps in downlink, 50Mbps in uplink

[0220] -Battery: several days (up to 1 to 2 weeks).

[0221] Table 5 illustrates illustrative common requirements and usage-specific requirements for the three representative redcap use cases described above.

[0222] [Table 5]

[0223]

[0224] The redcap requirement can be met by (a combination of) various features provided by the UE and BS. The following are examples of features and sub-features supported by the UE / BS to meet the redcap requirement.

[0225] In terms of complexity reduction of redcap UE, redcap UE may have the following features: i) reduction in the number of UE Rx / Tx antennas, ii) reduction in UE bandwidth, iii) support for half-duplex FDD, iv) released UE processing time, and v) relaxed UE processing capability. In addition, in terms of power saving, i) PDCCH monitoring may be reduced due to the limitation of a smaller number of blind decodings (BD) and control channel elements (CCEs), ii) extended DRX for RRC inactivity and / or idle may be applied, or iii) radio resource management (RRM) for fixed devices may be relaxed. In addition, coverage recovery / enhancement may be provided as a feature.

[0226] Among the features of redcap UE, half-duplex FDD is traditionally a method used in low-cost / low-complexity UEs. In the case of a full-duplex FDD UE that supports both transmission and reception, a duplexer should be used to eliminate the effect exerted on the reception signal by interference generated from the transmission signal, and half-duplex FDD operation limits the simultaneous transmission / reception capability, and a duplexer for interference elimination is replaced with a low-cost radio frequency (RF) switch to reduce UE cost.

[0227] In the present disclosure, a half-duplex FDD operation may be defined in LTE. In the half-duplex FDD operation, the UE may not perform transmission and reception at the same time, but there is no limitation in full-duplex FDD.

[0228] Furthermore, in LTE, two types (eg, Type A and Type B) of half-duplex FDD operations are defined as follows.

[0229] In case of Type A half-duplex FDD operation, the UE generates a guard period as follows.

[0230] - The last part of a downlink subframe immediately preceding an uplink subframe is not received from the same UE.

[0231] In case of Type B half-duplex FDD operation, the UE generates a guard period called a half-duplex protection subframe respectively as follows.

[0232] - not receiving a downlink subframe immediately preceding an uplink subframe from the same UE, and

[0233] - A downlink subframe immediately following an uplink subframe is not received from the same UE.

[0234] During the guard period, neither DL transmission nor UL transmission occurs. The guard period may also be replaced by a term called guard time.

[0235] Hereinafter, the present disclosure proposes methods and / or embodiments for supporting half-duplex FDD operation. Specifically, Proposal 1 proposes a method for configuring a time slot format for half-duplex FDD operation, and configuring / defining a switching time for switching from downlink to uplink or from uplink to downlink, and a method for configuring a guard period. Proposal 2 proposes a method for preventing link direction conflicts in half-duplex FDD operation.

[0236] <Proposal 1>

[0237] The slot format indicates how to use each symbol in a slot. Multiple slot formats can be predefined, and a specific slot format can be indicated / configured by a slot format index. In NR, each slot format can be composed of at least one of a DL symbol, a UL symbol, or a flexible symbol. For example, there may be i) a slot format consisting of only DL symbols, ii) a slot format consisting of only UL symbols, or iii) a slot format consisting of only flexible symbols. As another example, there may be i) a slot format consisting of (one or more) DL symbols and (one or more) flexible symbols, ii) a slot format consisting of (one or more) UL symbols and (one or more) flexible symbols, or iii) a slot format consisting of (one or more) DL symbols and (one or more) UL symbols. As another example, there may be a slot format including all (one or more) DL symbols, (one or more) UL symbols, and (one or more) flexible symbols.

[0238] For half-duplex FDD operation, the BS may semi-statically configure the UL carrier by (i) a slot format consisting of only UL symbols or a combination of UL symbols and flexible symbols, and (ii) a DL carrier by a slot format consisting of only DL symbols or a combination of DL symbols and flexible symbols through common or dedicated RRC signaling. The method for semi-statically configuring the slot format through common or dedicated RRC signaling may be similar to the existing method for configuring the TDD slot format through the RRC parameter "tdd-UL-DL-ConfigurationCommon" or "tdd-UL-DL-Configuration Common Dedicated".

[0239] Alternatively, for half-duplex FDD operation, the BS may construct both the UL carrier and the DL carrier by flexible symbols. For example, by a simple method for semi-statically constructing all slot formats by flexible symbols, when a common or dedicated RRC parameter for separate slot format configuration is not defined / indicated for each of the DL carrier or the UL carrier, the UE may consider that all slot formats of the carrier are constructed by flexible symbols.

[0240] Based on the above method, the time slot format of the DL carrier and the UL carrier can be semi-statically configured. Based on the time slot format configuration, the BS can basically support half-duplex FDD operation by ensuring that the half-duplex FDD UE does not need to transmit and receive both at the same time through semi-static and / or dynamic scheduling via RRC and / or DCI signaling.

[0241] <Method 1>

[0242] In order to support half-duplex FDD operation, the time required to switch A to B can be predefined. In the following, for ease of description, the operation of switching A to B will be represented as "A to B switching". The data / signal transfer direction in A and the data / signal transfer direction in B can be opposite directions to each other. For example, when A is a downlink, B is an uplink, which can be represented as "DL to UL switching". Alternatively, when A is an uplink, B is a downlink, which can be represented as "UL to DL switching". The time required to switch A to B will be represented as "A to B switching". In the following, downlink (DL) means communication from a BS to a UE, and uplink (UL) means communication from a UE to a BS. In addition, with respect to the UE, DL RX means the operation of receiving a DL channel / signal from a BS, and UL TX means the operation of sending a UL channel / signal to the BS.

[0243] The DL to UL switching time required for a UE supporting half-duplex FDD (e.g., T DU ) may be predefined and the UE may not expect to perform DL Rx or UL Tx operations within the corresponding time.

[0244] For example, the DL to UL switching time T DU It may be included in the DL symbol / slot before UL Tx, and the UE may not expect DL Rx within the corresponding time. That is, the UE may not receive DL Rx within the corresponding time. The BS may not perform DL transmission within the corresponding time.

[0245] For example, the DL to UL switching time T DU may be included in the UL symbol / time slot after the DL Tx, and the UE may not expect UL Tx at the corresponding time. That is, in the case of paired spectrum operation, a UE that may not perform full-duplex FDD communication may not expect a UL Tx after the end of the last received DL symbol earlier than T DU That is, the UE may not transmit UL within the corresponding time. The BS may not expect to receive UL Tx from the UE within the corresponding time.

[0246] Similarly, the UL to DL switching time required for a half-duplex FDD UE (eg, TUD ) may be predefined and the UE may not expect to perform DL Rx or UL Tx operations within the corresponding time.

[0247] For example, the UL to DL switching time T UD It may be included in the UL symbol / time slot before DL Rx, and the UE may not expect UL Tx in the corresponding time. That is, the UE may not send UL in the corresponding time. The BS may not expect to receive UL Tx from the UE in the corresponding time.

[0248] For example, the UL to DL switching time T UD may be included in the DL symbol / slot after the UL Tx, and the UE may not expect DL Rx at the corresponding time. That is, in the case of paired spectrum operation, a UE that may not perform full-duplex FDD communication may not expect a DL Rx earlier than T after the end of the last transmitted UL symbol. UD The transmission is performed in the DL.

[0249] Alternatively, as far as the UE is concerned, when T DU and T UD Equal or similar to each other (T DU ≈T UD ), you can define a representative value (for example, T SW ), and T SW Can be replaced by T DU 、T UD .

[0250] Switching time T value (for example, T SW ,T DU ,T UD ) can be defined as the time unit T defined as follows C . T C =1 / (Δf max ·N f ) and, here, Δf max =480.103Hz and N f =4096. That is, T DU ,T UD and T SW Can be defined as N DU T C ,N UD T C and N SW T C .

[0251] As in the above example, instead of predefining the DL to UL switching time or the UL to DL switching time as a fixed value, the switching time supported by the UE may be reported to the BS in the form of UE capabilities (or capability information). For example, the UE may report the N value (i.e., N DU ,N UD or N SW Alternatively, a set of multiple N values ​​may be predefined (e.g., in a table form), and the UE may report to the BS specific (one or more) N values ​​supported in the set of N values. In this case, the UE reports the minimum switching time value to report to the BS all values ​​equal to or greater than the minimum switching time value.

[0252] The BS may configure the switching time to the UE via RRC parameters based on the UE capabilities reported by the UE. In this case, when there are no parameters (or when the parameters are not indicated / configured), the UE may assume a default switching time.

[0253] For example, the UE may assume the maximum N value among a plurality of predefined N values ​​as the default switching time. The reason for assuming the maximum N value as the default switching time is that all UEs operating in half-duplex FDD operate by assuming the same N value to avoid overly complex BS scheduling when UEs supporting different switching times coexist.

[0254] As another example, the N value that the UE reports can support may be assumed as the default switching time. Alternatively, when the number of N values ​​that the UE reports can support is multiple, the minimum N value among the N values ​​may be assumed as the default switching time.

[0255] A plurality of sets of N values ​​may be distinguished by the switching time supported by the UE. For example, when two sets of N values ​​are predefined, the N value that can be supported by a low-cost / low-complexity UE (e.g., a redcap UE) may be equal to or greater than the N value supported by a high-cost / high-complexity UE (e.g., a NR UE), and the high-cost / high-complexity UE may support both sets of N values ​​as reported by capability information.

[0256] For example, when configuring N DU and N UDWhen the switching time for capability 1 and the switching time for capability 2 are set to values, each of the switching time for capability 1 and the switching time for capability 2 may be defined in two table forms. A high-cost / high-complexity UE may support both capability 1 and capability 2, while a low-cost / low-complexity UE may report to the BS through capability information that only capability 1 is supported. A high-cost / high-complexity UE may expect the switching time to be configured by a value in Tables 6 and 7 through higher layer signaling. On the contrary, a low-cost / low-complexity UE may expect the switching time to be configured by only the value in Table 6 through higher layer signaling. That is, a low-cost / low-complexity UE may not expect the switching time to be configured by the value in Table 7.

[0257] Table 6 illustrates the switching time N for capability 1 DU and N UD Example of value.

[0258] [Table 6]

[0259] Switching time FR1 FR2 <![CDATA[N DU ]]> 25600*2 13792*2 <![CDATA[N UD ]]> 25600*2 13792*2

[0260] Table 7 illustrates the switching time N for capability 2 DU and N UD Example of value.

[0261] [Table 7]

[0262] Switching time FR1 FR2 <![CDATA[N DU ]]> 25600 13792 <![CDATA[N UD ]]> 25600 13792

[0263] Tables 6 and 7 are merely examples for convenience of description and do not limit the technical scope of the present disclosure. In the above Table 7, these values ​​are merely examples of values ​​mainly required for RF circuit switching, which correspond to 25600*1 / (480E3*4096)*1E6=13us in FR1 (e.g., 410MHz to 7125MHz) and 13792*1 / (480E3*4096)*1E6=7us in FR2 (e.g., 24250MHz to 52600MHz).

[0264] Through the above method 1, in NR, the switching time required for A to B switching to support half-duplex FDD operation can be configured, and the minimum time required for A to B switching can be ensured.

[0265] <Method 2>

[0266] Method 2 proposes a method for defining / configuring a guard period to support half-duplex FDD operation in NR. During the guard period, neither DL transmission nor UL transmission occurs. The guard period can also be replaced by the term guard time. The switching time of the above method 1 can be included in the guard period.

[0267] The guard period may be defined as a unit of a symbol or a time slot, and the UE may report information about the guard period to the BS as a capability information form. The guard period defined as a unit of a symbol may be defined as (one or more) guard symbols, and expressed as the number of OFDM symbols used as the guard period (e.g., G_sym). The guard period defined as a unit of a time slot may be defined as a guard time slot, and expressed as the number of time slots used as the guard period (e.g., G_slot).

[0268] The guard period for Type A half-duplex FDD operation may be defined as G_sym, A guard symbol.

[0269] Example 1-1) For Type A half-duplex FDD operation, the guard period may be generated by the UE as follows.

[0270] - Immediately before the UL timeslot, no G_sym,A DL symbol(s) are received from the same UE.

[0271] Example 1-1 may be a case where a guard period is ensured by defining (one or more) guard symbols only for the case of DL to UL switching, and in the case of UL to DL switching, the BS ensures the guard period by timing advance (TA) configuration. This scheme may be an appropriate method in the case where the required guard period is small (i.e., such as a case of type A).

[0272] Example 1-2) For Type A half-duplex FDD operation, the guard period may be generated by the UE as follows.

[0273] - immediately before the UL timeslot, no G_sym,A1DL symbol(s) are received from the same UE, and

[0274] - Immediately after the UL timeslot, no G_sym,A2DL symbol(s) are received from the same UE.

[0275] Example 1-2 is a case where a guard period is configured for both DL to UL switching and UL to DL switching. For example, Example 1-2 may be a case where it is difficult for the BS to ensure sufficient time for switching with the TA because the required guard period (or switching time) is not small.

[0276] In the case of type B half-duplex FDD operation, since a single oscillator is used for low cost / low complexity, additional time is required for the frequency re-tuning operation, so a guard period value greater than type A may generally be required. Therefore, the guard period may be defined as G_sym,B (>G_sym,A) guard symbols or as G_slot guard slots. G_sym,B may have a larger value than G_sym,A.

[0277] Example 2-1) For Type B half-duplex FDD operation, each guard period referred to as a half-duplex guard slot may be generated by the UE as follows.

[0278] - a G_slot,B1 DL timeslot is not received from the same UE immediately before the UL timeslot, and

[0279] - Immediately after a UL timeslot, no G_slot,B2 DL timeslot is received from the same UE.

[0280] Example 2-1 may be a case where a required guard period is large in case of Type B, and thus the guard period is defined as a unit of a slot and is configured for both DL to UL and UL to DL.

[0281] Example 2-2) For Type B half-duplex FDD operation, each guard period, referred to as a half-duplex guard symbol, may be generated by the UE as follows.

[0282] - immediately before the UL timeslot, no G_sym,B1DL symbol(s) are received from the same UE, and

[0283] - Immediately after the UL timeslot, no G_sym,B2DL symbol(s) are received from the same UE.

[0284] Example 2-2, which is a case where a guard period is configured for both DL to UL switching and UL to DL switching, is a case where the type B guard period is not defined as a unit of a slot but as a plurality of symbols. For example, Example 2-2 may be a case where it is difficult for the BS to secure sufficient time for switching with the TA because the required guard period (or switching time) is not small.

[0285] The guard period may be defined without distinguishing the type of half-duplex FDD, the guard period (or switching time) information required for each type of UE may be delivered to the BS as a capability report form, and the BS may also configure (one or more) guard symbols by referring to the corresponding information.

[0286] Example 3) For half-duplex FDD operation, each guard period referred to as half-duplex guard symbol(s) may be generated by the UE as follows.

[0287] - immediately before the UL timeslot, no G_sym,1DL symbol(s) are received from the same UE, and

[0288] - Immediately after the UL timeslot, no G_sym,2DL symbol(s) are received from the same UE.

[0289] In the above example, a G value (e.g., G_sym, G_slot, G_sym,A, or G_sym,B) may be defined for each frequency range. Since the performance and cost of the components used may be different for each frequency range, the resulting circuit switching, RF retuning time, etc. may also be different. For example, the G value may be configured / defined by distinguishing between FR1 (e.g., 410 MHz to 7125 MHz) and FR2 (e.g., 24250 MHz to 52600 MHz).

[0290] Alternatively, a G value (e.g., G_sym, G_slot, G_sym,A, or G_sym,B) may be defined for each subcarrier spacing (SCS). The reason for defining a G value for each SCS is that when the guard period has a predetermined value TG (in us) in time, the guard period is configured to be minimum to minimize resource waste compared to defining the guard symbol(s) by defining the guard symbol(s) as the minimum number of OFDM symbols having a duration equal to or greater than TG based on a specific SCS1 and simply scaling the SCS2 (>SCS1) to the SCS2 / SCS1 value.

[0291] Alternatively, the G value (e.g., G_sym, G_slot, G_sym,A, or G_sym,B) can be configured / defined by simply scaling the guard symbol / slot of each SCS by the SCS ratio. For example, when defining the guard symbol / slot for a particular SCS (e.g., SCS1), the (one or more) guard symbol / slots can be defined / configured by simply scaling SCS2 (>SCS1) to the SCS2 / SCS1 value based on the defined guard symbol / slot.

[0292] When the guard symbol / time slot of each SCS is simply scaled and applied at the SCS ratio as described above, it may be necessary to define an SCS value that becomes a reference for defining the guard symbol / time slot, i.e., a reference SCS.

[0293] For example, from the perspective of signaling overhead, the reference SCS may be defined as the lowest SCS for data transmission in the corresponding frequency range or band without a separate signaling parameter. As a specific example, as in Table 2 above, since 15, 30, and 60 KHz are supported in FR1, and 60, 120, and 240 KHz are supported in FR2, 15 KHz may be defined as the reference SC in FR1, and 60 KHz may be defined as the reference SCS for the guard symbol / time slot configuration in FR2.

[0294] As another example, a UE configured to monitor DCI format 2_0 in FDD may be configured with a reference SCS for the time slot format for each UL / DL by a higher layer. In this case, the BS does not define a separate parameter by considering the signaling overhead (or when there is no separate parameter), and the UE may assume the reference SCS for the protection symbol / time slot / subframe as the reference SCS for the time slot format. That is, the SCS associated with DCI format 2_0 may be assumed to be the reference SCS. DCI format 2_0 may be CRC-scrambled by SFI-RNTI and used to announce the time slot format.

[0295] In this case, when the reference SCS of A and the reference SCS of B are different in the A to B switching operation (for example, when the reference SCS of UL and the reference SCS of DL are different), the guard period can be defined based on the reference SCS of A. When A is the source carrier and B is the destination carrier in the A to B switching, the guard period can be defined / configured based on the reference SCS of the source carrier. Alternatively, the guard period can be defined based on the reference SCS of the carrier to which the guard period belongs. That is, when the guard period belongs to A in the A to B switching, the guard period can be defined based on carrier A, and when the guard period belongs to B, the guard period can be defined based on carrier B. Alternatively, as in the above examples 1-1 / 1-2 / 2-1 / 2-2 / 3, when all guard symbols / slots belong to DL and are generated in the form of no RX or discrete reception (DRX), the guard period can be defined based on the reference SCS of the DL carrier.

[0296] For example, in the case where the UE is not configured to monitor DCI format 2_0 in FDD, the reference SCS for the guard period (e.g., guard symbol / time slot / subframe) may be configured through higher layer signaling. The reference SCS may be configured for each of UL and DL. The reference SCS for DL ​​(e.g., μ DL,g ) can be a value of SCS equal to or less than any active / configured DL BWP. In this case, it is possible to DL DL BWP Each guard symbol / time slot / subframe defined based on the reference SCS is applied during each symbol / time slot / subframe. In addition, the reference SCS for UL (e.g., μ UL,g ) can be a value of SCS equal to or less than any active / configured UL BWP. In this case, it is possible to UL UL BWP Each guard symbol / time slot / subframe defined based on the reference SCS is applied during each symbol / time slot / subframe. Alternatively, the reference SCS can also be configured as a single value for DL ​​and UL (e.g., μ XL,g ). In this case, the reference SCS may be a value equal to or less than the SCS of any activated / configured DL or UL BWP, and may be a value equal to or less than the SCS of any activated / configured DL or UL BWP, respectively. DL DL BWP or with activated / configured SCSμ UL UL BWP or Each guard / symbol / time slot subframe defined based on the reference SCS is applied during each symbol / time slot / subframe.

[0297] The number of symbols / time slots / subframes in the guard period may be configured based on the method and / or embodiments proposed in the above method 2.

[0298] <Method 3>

[0299] At the same time, flexible symbols / slots may also be defined as included in the guard period to support half-duplex FDD operation in NR. In the current NR, a UE that is not configured to monitor DCI format 2_0 may perform DL reception and UL transmission indicated by DCI or higher layer configuration in a flexible symbol / slot configured by higher layer signaling, and when the flexible symbol / slot is included in the guard period, the UE may not expect to perform DL Rx or UL Tx operations.

[0300] In the above-mentioned method 1, a method for defining A to B switching time to support half-duplex FDD is proposed, and when the method of configuring flexible symbols / slots as guard periods for method 3 is applied to method 1, the switching time can be defined as in the following example.

[0301] For example, the DL to UL switching time T DU may be included in the UL or flexible symbol / slot after DL Rx, and the UE may not expect UL Tx or flexible operation at the corresponding time. That is, in the case of paired spectrum operation, a UE that may not perform full-duplex FDD communication may not expect to receive a UL Tx or flexible operation earlier than T after the end of the last received DL symbol. DU The transmission is performed in the UL or flexible symbols / slots.

[0302] For example, the UL to DL switching time T UDmay be included in the DL or flexible symbol / slot after the UL Tx, and the UE may not expect DL Rx or flexible operation at the corresponding time. That is, in the case of paired spectrum operation, a UE that may not perform full-duplex FDD communication may not expect to receive a DL Rx or flexible operation earlier than T after the end of the last received UL symbol. UD Reception is performed in DL or flexible symbols / slots.

[0303] In the case of the extended CP, since the OFDM symbol length, the number of symbols in a slot, etc. may be different compared to the normal CP, a separate guard period definition may be required, and the same method as the method for assuming the normal CP (e.g., method 2, method 3, etc.) may be applied. In this case, since there may be no difference in the case of a guard slot in which the guard period is defined as a unit of a slot, the extended CP may be defined separately only for (one or more) guard symbols for defining the guard period as a unit of a symbol.

[0304] Alternatively, a separate configuration, capability, etc. is not defined for the extended CP, but the protection period of the extended CP may be determined based on the protection period defined based on the normal CP. For example, an OFDM symbol of the extended CP that is completely or partially overlapped with an OFDM symbol of the normal CP defined as a protection symbol may be defined as a protection symbol with the extended CP. That is, when one of the overlapped normal CP symbols is a protection symbol, the UE may determine the extended CP symbol as a protection symbol.

[0305] <Proposal 2>

[0306] The BS can support half-duplex FDD operation by scheduling using the method of the above-mentioned proposal 1, but when it is difficult for the BS to accurately predict the UL transmission of the UE or difficult to actually avoid the conflict with the resources periodically configured in advance for a specific purpose, a method for avoiding link direction conflicts may be required for synchronous half-duplex FDD operation between the BS and the UE. Proposal 2 of the present disclosure proposes a method for preventing link direction conflicts in half-duplex FDD operation.

[0307] As described above, for ease of description, switching A to B in half-duplex FDD operation will be represented as "A to B switching". For example, switching from downlink to uplink can be represented by "DL to UL switching", and switching from uplink to downlink can be represented by "UL to DL switching".

[0308] The A to B handover may be (i) indicated by DCI or (ii) indicated by higher layer signaling (e.g., RRC and MAC-CE). Indicating the A to B handover by DCI may be interpreted as indicating the scheduling of B by DCI, and as allocating resources to B by DCI. Indicating the A to B handover by higher layer signaling may mean indicating the A to B handover based on other information / signals in addition to the DCI. Indicating the A to B handover by higher layer signaling may be interpreted as indicating the scheduling of B by higher layer signaling, and also as allocating resources to B by higher layer signaling.

[0309] Link direction conflict refers to a conflict that may occur in DL to UL switching or UL to DL switching in half-duplex FDD operation. This may refer to a situation where the time domain resources associated with the DL carrier and the time domain resources associated with the UL carrier overlap each other. Therefore, Proposal 2 proposes a method for preventing / avoiding conflict and / or an operation method of UE / BS in the case of conflict.

[0310] Furthermore, the UE of Proposal 2 may correspond to a redcap UE.

[0311] <Method 1>

[0312] In half-duplex FDD operation, the position of the guard period and / or the operation of the UE and the BS may be configured / indicated according to the signal or information of which layer the A to B switching occurs based on. In other words, the position of the guard period and / or the operation of the UE and the BS may be configured / indicated according to the A to B switching i) by B occurring based on DCI scheduling (i.e., a dynamic scheme), or ii) by B occurring based on signaling other than DCI (e.g., a higher layer signaling) scheduling (i.e., a configured scheme).

[0313] When DL to UL switching occurs for UL Tx indicated by DCI in half-duplex FDD operation (i.e., when UL transmission is scheduled by DCI), the UE may not expect DL Rx during the guard period before the UL slot / symbol. This can also be interpreted as the UE dropping DL Rx during the guard period. In this case, the guard period may exist before the UL interval in the time domain. In other words, the guard period may be included in the DL interval in the time domain, and the UE may not expect DL Rx during the guard period.

[0314] Alternatively, when uplink to downlink switching (UL to DL switching) occurs by DL Rx indicated by DCI in half-duplex FDD operation (ie, when DL transmission is scheduled by DCI), the UE may not expect UL Tx during the guard period before the DL slot / symbol. This can also be interpreted as the UE dropping UL Tx during the guard period. In this case, the guard period may exist before the DL interval in the time domain. In other words, the guard period may be included in the UL interval in the time domain, and the UE may not expect UL Tx during the guard period. When the guard period occupies a portion or some symbols of the corresponding slot, all corresponding slots may be dropped, or only the portion / (one or more) symbols overlapping with the guard period in the corresponding slot may be dropped.

[0315] When DL to UL switching occurs for UL Tx configured by higher layer signaling after DL Rx indicated by DCI in half-duplex FDD operation, the UE may not expect UL Tx during the guard period after the DL slot / symbol. This can be interpreted as the UE discarding UL Tx during the guard period. In this case, the guard period may exist before the DL interval in the time domain. In other words, the guard period may be included in the UL interval in the time domain, and the UE may not perform transmission in the UL during the guard period. Alternatively, when the guard period occupies a portion of the corresponding slot or some symbols included in the UL interval, the UE may i) discard all corresponding slots or ii) discard only the portion / (one or more) symbols overlapping with the guard period in the corresponding slot. Discarding only the overlapping portion / (one or more) symbols may be limited to partial UL transmissions (e.g., SRS transmissions).

[0316] When UL to DL switching occurs for DL ​​Rx configured by higher layer signaling after UL Tx indicated by DCI in half-duplex FDD operation, the UE may not expect DL Rx during the guard period after the UL Tx slot / symbol. This can be interpreted as the UE dropping DL Rx during the guard period. In this case, the guard period may exist after the UL interval in the time domain. In other words, the guard period may be included in the DL interval in the time domain, and the UE may not expect DL Rx during the guard period. The BS may not send DL Rx to the UE during the guard period after the UL Tx slot / symbol.

[0317] According to method 1 of the above-mentioned proposal 2, when the scheduling schemes of A and B are different in the A to B switching, that is, when one is scheduled based on DCI and the other is scheduled based on signaling other than DCI (e.g., higher layer signaling), the protection period can be included in the duration configured based on the higher layer signaling by prioritizing the scheduling scheme based on DCI scheduling.

[0318] <Method 2>

[0319] In half-duplex FDD operation, the location of the guard period and / or the operations of the UE and BS may be configured / indicated according to the type / content of information / signal in A and / or B in A to B switching.

[0320] First embodiment

[0321] The first embodiment is an example of a case where information / signal transmitted in UL is a PRACH preamble in DL-to-UL switching or UL-to-DL switching.

[0322] The random access procedure is used for various purposes. For example, the random access procedure can be used for initial network access, handover, and UE-triggered UL data transmission. The UE can obtain UL synchronization and UL transmission resources through the random access procedure. The random access procedure is divided into a contention-based random access procedure and a contention-free random access procedure.

[0323] The UE may send the random access preamble as a message 1 (Msg1) of a random access procedure through the PRACH. The random access preamble sent through the PRACH may be referred to as a PRACH preamble.

[0324] Random access preamble sequences with two different lengths are supported: the long sequence length 839 is applied to subcarrier spacings of 1.25 kHz and 5 kHz, and the short sequence length 139 is applied to subcarrier spacings of 15, 30, 60, and 120 kHz.

[0325] Multiple RACH preamble formats are defined with one or more RACH OFDM symbols and different cyclic prefixes (and / or guard times). The RACH configuration of a cell is included in the system information of the cell and provided to the UE. The RACH configuration includes information about the subcarrier spacing of the PRACH, available preambles, preamble formats, etc. The RACH configuration includes association information between SSBs and RACH (time-frequency) resources. The UE sends a random access preamble in the RACH time-frequency resources associated with the detected or selected SSB.

[0326] The threshold of the SSB for RACH resource association may be configured by the network, and the transmission or retransmission of the RACH preamble is performed based on the SSB, where the reference signal received power (RSRP) measured based on the SSB meets the threshold. For example, the UE may select one SSB among the SSBs whose RSRP meets the threshold, and send or retransmit the RACH preamble based on the RACH resource associated with the selected SSB.

[0327] When DL to UL switching occurs in the middle of DL Rx in half-duplex FDD operation to transmit a PRACH preamble, it may be defined that the UE does not expect DL Rx during a guard period before a valid RACH opportunity (hereinafter referred to as RO) at which transmission of the PRACH preamble is valid. This may also be interpreted as the UE dropping DL Rx during the guard period. In this case, the guard period may be located before the valid RO in the time domain. In other words, the guard period may be included in the DL interval of the time domain, and the UE may not expect DL Rx during the guard period.

[0328] This example may mean that when a dynamically scheduled DL (e.g., a DL scheduled by DCI) is switched to a valid RO for transmission of a PRACH preamble, the valid RO takes precedence over the dynamic DL. In addition, this example may mean that when a semi-statically configured DL (e.g., a DL configured by higher layer signaling) is switched to a valid RO for transmission of a PRACH preamble, the valid RO takes precedence over the semi-statically configured DL.

[0329] That is, for the conflict situation where the dynamically scheduled DL transmission overlaps with the valid RO, the valid RO may take precedence over the dynamic DL. Similarly, for the conflict situation where the semi-statically configured DL transmission overlaps with the valid RO, the valid RO may take precedence over the semi-static DL. However, in the above two cases, unlike the TDD case, before the effective RO, for the HD-FDD operation in the FDD band, the Rx to Tx (i.e., DL to UL) switching time should be considered. That is, the UE may not expect to receive in the DL later than the Rx to Tx switching time before the effective RO starts. Similarly, for the HD-FDD operation in the FDD band after the effective RO, the TX to RX switching time may be considered. That is, the UE may not expect to receive in the DL earlier than the TX to RX switching time before the effective RO ends. The effective RO in the present disclosure may or may not include N_gap symbols before the effective RO. Here, N_gap (i.e., N gap ) can be defined as shown in Table 8 below.

[0330] Table 8 illustrates N for different leading SCSμ gap Example of value.

[0331] [Table 8]

[0332] Leading SCS <![CDATA[N gap ]]> 1.25kHz or 5kHz 0 15kHz or 30kHz or 60kHz or 120kHz 2

[0333] The operation of the first embodiment according to the above-mentioned Proposal 2 may be defined as in Table 9.

[0334] [Table 9]

[0335]

[0336] In Table 9, N_GP symbols represent a value defined as a symbol unit in order to provide a switching time. For example, N_GP symbols may be defined as a symbol unit for each SCS based on the method of the above-mentioned proposal 1. As an example, N_GP=1 symbol may be defined for all SCSs, or N_GP may be configured as 1, 2, and 4 for 15kHz, 30kHz, and 60kHz SCSs, respectively. N_GP may be defined as a unit of time T_c, similar to the switching time in the above-mentioned proposal 1.

[0337] As another example, when DL Rx is an operation indicated by DCI (i.e., scheduled by DCI), the RO that exists after the guard period from the last DL symbol may be defined as a valid RO capable of transmitting the PRACH preamble. That is, in half-duplex FDD operation, in the RO that starts before the time point that separates the last DL symbol of DL Rx indicated by DCI by the guard period, PRACH preamble transmission may not be expected. In other words, in the valid RO after the time point that is at least spaced apart from the last symbol of DL Rx by the guard period, the UE may transmit the PRACH preamble. This may mean that DL Rx dynamically scheduled by DCI takes precedence over the PRACH preamble.

[0338] As another example, when DL to UL switching occurs for PRACH preamble transmission from SSB Rx through RO in half-duplex operation, PRACH preamble transmission may be allowed in RO starting after the guard period from the last symbol of SSB transmission. That is, a valid RO may satisfy this condition.

[0339] Alternatively, when UL to DL switching occurs for SSB Rx after PRACH preamble transmission through RO, if SSB exists before the guard period from the last symbol of RO, PRACH preamble transmission may not be expected in the corresponding RO. That is, the valid RO may not satisfy this condition. In other words, PRACH preamble transmission may be allowed in the RO that ends before the guard period from the first symbol of SSB transmission. That is, the valid RO may satisfy this condition. In addition, if PRACH preamble exists during the guard period before the SSB transmission symbol, PRACH preamble transmission may not be expected in the corresponding PO.

[0340] The valid RO may be defined as in Table 10 based on the above example.

[0341] [Table 10]

[0342]

[0343] In Table 10, N_gap may be defined as in Table 8 above.

[0344] Second embodiment

[0345] The second embodiment is an example of a case where the information received in the DL in a DL to UL switching or a UL to DL switching is a synchronization signal block (SSB). The UE can perform cell search, system information acquisition, beam alignment for initial access, DL measurement, etc. based on the SSB. The SSB is mixed with the SS / synchronization signal / physical broadcast channel (PBCH) block. The SSB consists of a primary synchronization signal (PSS), a secondary synchronization signal (SSS), and a physical broadcast channel (PBCH). The SSB consists of four consecutive OFDM symbols, and PSS, PBCH, SSS / PBCH, or PBCH is sent for each OFDM symbol. Each of the PSS and SSS can be composed of one OFDM symbol and 127 subcarriers, and the PBCH consists of 3 OFDM symbols and 576 subcarriers.

[0346] When DL to UL switching occurs for UL Tx after SSB Rx in half-duplex FDD operation, the UE may not expect UL Tx during the guard period after the last symbol of the SSB transmission. This can be interpreted as the UE discarding UL Tx during the guard period. In this case, the guard period may be located after the last symbol of the SSB transmission in the time domain. In this case, part or all of the guard period may overlap with the UL interval, and the UE may not perform transmission in the UL during the guard period. When the guard period occupies a part or some symbols of the corresponding time slot, all corresponding UL time slots may be discarded, or only the part / (one or more) symbols overlapping with the guard period in the corresponding time slot may be discarded. Discarding only the overlapping part / (one or more) symbols may be limited to partial UL transmissions (e.g., SRS transmissions).

[0347] When UL to DL switching occurs for SSB Rx after UL Tx in half-duplex FDD operation, the UE may not expect UL Tx during the guard period before the start symbol of the SSB transmission. This can be interpreted as the UE dropping UL Tx during the guard period. In this case, part or all of the guard period may overlap with the UL interval in the time domain, and the UE may not perform transmission in the UL during the guard period. When the guard period occupies a part or some symbols of the corresponding time slot, all corresponding UL time slots may be dropped, or only part / (one or more) symbols overlapping with the guard period in the corresponding time slot may be dropped. The operation of dropping only the overlapping part / (one or more) symbols may be limited to partial UL transmissions (e.g., SRS transmissions).

[0348] For collision situations where a dynamically scheduled UL transmission (e.g., a UL transmission scheduled by DCI) overlaps with an SSB, the SSB may take precedence over the dynamic UL. Similarly, for collision situations where a semi-statically configured UL transmission (e.g., a UL transmission configured by higher layer signaling) overlaps with an SSB, the SSB may take precedence over the semi-static UL. However, in both of the above cases, unlike the TDD case, for HD-FDD operation in the FDD band after the SSB symbol set, the RX to TX (i.e., DL to UL) switching time should be considered. That is, the UE may not expect to send an SSB in the UL earlier than the Rx to Tx switching time after the end of the last received DL symbol. Similarly, for HD-FDD operation in the FDD band after the SSB symbol set, the TX to RX switching time may be considered. That is, the UE may not expect to send an SSB in the UL later than the TX to RX switching time after the start of the first received DL symbol.

[0349] For the conflicting case of semi-statically configured UL transmission and SSB overlap, the semi-statically configured UL transmission includes a valid PUSCH opportunity, which includes a valid RO and a 2-step RACH. For both cases, unlike TDD, the RX to TX (or TX to RX) switching time should be described for HD-FDD operation of the FDD band after (or before) the SSB symbol set. The valid RO in the present disclosure may or may not include N_gap symbols before the valid RO. Here, N_gap can be defined as in Table 8 above.

[0350] Based on the above example, the valid PUSCH opportunities may be defined as in Table 11.

[0351] [Table 11]

[0352]

[0353]

[0354] At the same time, the UE can receive SSBs for measurement before, after or during UL transmission. In an SSB burst set, up to L SSBs can be sent, and the number / position of the SSBs actually sent can vary for each BS / cell. The number / position of the SSBs actually sent can be used for rate matching and measurement, and information about the SSBs actually sent can be provided to the UE. For SSB reception for measurement, the BS can configure an SSB-based RRM measurement timing configuration (SMTC) window, and configure all or some SSBs within the corresponding window to be received for measurement. In this case, the duration of receiving the SSB for measurement can be defined, and the UE can assume that UL Tx is not expected during the corresponding interval or that no request for UL transmission is received from the BS. In half-duplex FDD operation, the SSB reception interval for measurement can be defined as an interval consisting of an SSB transmission symbol and an interval including a protection period before, after, or before and after the SSB transmission symbol. This method can be applied only to situations where timing synchronization between serving cells is guaranteed. In addition, it can be assumed that the measurement gap (MG) is configured for intra-frequency / inter-frequency measurement and the UE does not expect DL Rx and / or UL Tx during the corresponding interval. When considering UL to DL switching, DL to UL switching, and the guard period required in the switching in half-duplex FDD operation, the SSB reception interval within the MG can be defined as the interval from {MG start + guard period} to {MG end - guard period}.

[0355] In half-duplex FDD operation, when the guard period is large, the number of SSBs received in the MG is significantly reduced, which may affect the measurement performance. In order to solve the measurement performance degradation problem that may occur when the guard period is large, a new MG value including the guard period is defined for use by the UE (configured by higher layers) in half-duplex FDD operation.

[0356] <Method 3>

[0357] When a conflict occurs between DL and UL, the priority may be determined based on the transmission type of DL and UL. For example, the transmission type of DL may be a mapping type of PDSCH, and the transmission type of UL may be a mapping type of PUSCH. This may mean that the transmission type of DL and UL is determined by the DMRS position within each (mini) slot / subframe.

[0358] For example, when the DMRS for PUSCH transmission is sent to the first symbol of the UL slot after DL to UL switching (e.g., PUSCH mapping type B), the UE may not expect DL Rx during the guard period before the UL slot / symbol. That is, UL transmission may be prioritized over DL transmission. In this case, the guard period may be included in the DL duration, and the UE may drop DL Rx during the guard period.

[0359] The above method 2 can be applied only to the case where both A and B are configured by higher layer signaling or both A and B are dynamically scheduled by DCI in A to B switching. When the schemes for configuring or scheduling A and B are different (for example, when A is configured by higher layer signaling and B is dynamically scheduled by DCI), the UE can operate according to the method 1 / method 2 of the above proposal 2.

[0360] <Method 4>

[0361] When DL to UL switching occurs, the position of the guard time / guard period can be fixed to the last part (symbol, guard time) of the DL slot (LTE method) or fixed to the first part (symbol, guard time) of the UL slot (NR method). Alternatively, the BS can select one of the two methods. The position information of the guard time / guard period can be sent as system information or indicated by UE-specific RRC signaling.

[0362] The BS configuration described in the above method 4 can be applied only to the case where both A and B are configured by higher layer signaling or both A and B are dynamically scheduled by DCI. When the schemes for configuring or scheduling A and B are different (for example, when A is configured by higher layer signaling and B is dynamically scheduled by DCI), the UE can operate according to the method 1 / method 2 of the above proposal 2.

[0363] A method for configuring a guard period to support half-duplex FDD operation is described based on the method and / or embodiment of the above-mentioned Proposal 1 / Proposal 2. In order to efficiently use resources in half-duplex FDD operation, data or control information can be sent by rate matching around the guard period. Puncturing can be considered as an alternative to rate matching, and when assuming the same amount of transmission information and guard period, there is an advantage of being able to receive transmission data with a lower SNR than puncturing at rate matching.

[0364] Rate matching around the guard period may be limited to cases where the guard period is understood identically between the UE and the BS. For example, the UE may perform PDSCH reception or PUSCH transmission by assuming rate matching only when the guard period is predefined as a specific value or configured by a higher layer configuration. When there is no misunderstanding of the guard period between the BS and the UE, the BS may not send separate rate matching information through the DCI. In this case, the UE may receive the PDSCH or send a rate-matched PUSCH by using the time domain resource allocation (TDRA) information received through the DCI and the pre-acquired guard period information.

[0365] Alternatively, the BS may configure through a higher layer whether to apply rate matching in a time slot where a guard period exists. A common or dedicated RRC parameter may be defined for this purpose. In addition, a rate matching indication flag may be added to dynamically select whether to apply rate matching in a time slot where a guard period exists. For example, when the value of the corresponding flag is 1, the UE may perform DL Rx operation by assuming rate matching in a time slot where a guard period exists, and when the value of the corresponding flag is 0, the UE may perform DL Rx operation by assuming puncturing (the opposite operation is also possible).

[0366] Figure 7 An example of a signaling flow chart between a user equipment (UE) and a BS to which the method proposed in the present disclosure (eg, Proposal 1 / Proposal 2, etc.) can be applied is illustrated. Figure 7 In the example, it is assumed that the UE operates via a half-duplex FDD scheme. Figure 7 The UE can correspond to the "redcap UE". Figure 7 It is only for the convenience of description and does not limit the scope of the present disclosure. In addition, it can be omitted according to the situation and / or configuration Figure 7 Some of the steps shown in .

[0367] The UE may send UE capability information to the BS. That is, the BS may receive UE capability information from the UE (S710). The UE capability information may include at least one of the capability information of the switching time or the capability information of the protection period described in Proposal 1 / Proposal 2. The BS may perform scheduling of the UE based on the UE capability information.

[0368] The UE may receive configuration information from the BS. That is, the BS may send configuration information to the UE (S720). The configuration information may include at least one of information on a switching time or information on a guard period determined by UE capability information reported by the UE.

[0369] For example, as described in method 2 of the above-mentioned proposal 1, the information about the guard period may include the number of symbols or the number of time slots constituting the guard period. The information about the guard period may be configured for each SCS or for each frequency range.

[0370] Data transmission and reception between the UE and the BS may be performed based on the configuration information (S730). Since the UE operates according to half-duplex FDD, DL and UL are not performed simultaneously in the same duration. In addition, data transmission and reception may be performed by avoiding collision between DL and UL based on the method of the above-mentioned proposal 2.

[0371] Figure 8 An example of an operation flow chart of a user equipment (UE) sending or receiving data to which the method proposed in the present disclosure (eg, Proposal 1 / Proposal 2, etc.) can be applied is illustrated. Figure 8 In the example, it is assumed that the UE operates via a half-duplex FDD scheme. Figure 8 The UE can correspond to the "redcap UE". Figure 8 It is only for the convenience of description and does not limit the scope of the present disclosure. In addition, it can be omitted according to the situation and / or configuration Figure 8 Some of the steps shown in .

[0372] The UE may receive configuration information (S810). That is, the BS may send configuration information to the UE. The configuration information may be received through higher layer signaling (e.g., RRC, MAC-CE, etc.). The configuration information may include information related to a protection period for preventing conflicts / overlaps that may occur during DL to UL switching or UL to DL switching in half-duplex FDD operation. The protection period for DL ​​to UL switching or UL to DL switching may be configured based on the information related to the protection period. The protection period may be configured i) for each SCS, or ii) for each frequency range.

[0373] As a specific example, a protection period corresponding to each SCS may be configured / indicated. Alternatively, based on a first value as a protection period corresponding to a reference SCS, a second value as a protection period corresponding to another SCS is determined, and a ratio of the reference SCS to the other SCS may be equal to a ratio of the first value to the second value.

[0374] For example, the UE ( Figures 9 to 13 The operation of the reference numeral 100 / 200 in FIG. 100 may be performed by the following description. Figures 9 to 13 For example, refer to Fig.10, the one or more processors 102 may control the one or more transceivers 106 and / or the one or more memories 104 to send configuration information, and the one or more transceivers 106 may receive the configuration information.

[0375] The UE may receive downlink control information (DCI) (S820). That is, the BS may send the DCI to the UE. The DCI may be received through a control channel (e.g., PDCCH). For example, the DCI may include scheduling information for a data channel (e.g., PDSCH, PUSCH). In addition, when the DCI is DCI format 2_0, the time slot format may also be indicated based on the DCI.

[0376] Based on at least one of the configuration information or the DCI, (i) a first duration for transmitting the first data in a first direction, and (ii) a second duration for transmitting the second data in a second direction opposite to the first direction may be configured. For example, when the first direction is a downlink, the second direction may be an uplink. That is, the first duration for the first data (e.g., PDSCH) to be transmitted to the downlink and the second duration for the second data (e.g., PUSCH) to be transmitted to the uplink may be configured. As another example, when the first direction is an uplink, the second direction may be a downlink. That is, the first duration for the first data (e.g., PUSCH) to be transmitted to the uplink and the second duration for the second data (e.g., PDSCH) to be transmitted to the downlink may be configured.

[0377] For example, the UE ( Figures 9 to 13 The operation of the reference numeral 100 / 200 in FIG. 100 / 200 may be described as follows Figures 9 to 13 For example, refer to Fig.10 , the one or more processors 102 may control the one or more transceivers 106 and / or the one or more memories 104 to receive the DCI, and the one or more transceivers 106 may receive the DCI.

[0378] The UE may perform switching from the first duration to the second duration based on the first direction and the second direction being opposite to each other. For example, the UE may perform switching from the first duration to the second duration based on the first direction being a downlink and the second direction being an uplink. As another example, the UE may perform switching from a first duration for sending an uplink to a second duration for receiving a downlink based on the first direction being an uplink and the second direction being a downlink.

[0379] The protection period required for the switch may be included in the duration of the data with lower priority being passed between the first duration or the second duration. This may mean that the duration of the data with lower priority between the first duration or the second duration overlaps part or all of the protection period. The protection period may include the switching time from the first duration to the second duration.

[0380] Priorities of the first data and the second data may be determined based on a predefined rule.

[0381] For example, the predefined rule may be related to the type of information used to schedule the second data. As a specific example, it may be determined based on the second data scheduled by the DCI that the second data has a higher priority than the first data. In this case, the guard period may be included in the first duration.

[0382] As another example, the predefined rule may be associated with at least one type of the first data or the second data. As a specific example, the guard period may be included in the first duration based on the second data being a PRACH preamble. In this case, the UE may not receive the first data during the guard period included in the first duration. As another example, based on the first data being an SSB and the second data being a PRACH preamble, the guard period may be located after the last symbol of the SSB received in the first duration.

[0383] For example, the guard period may be included in the second duration based on the first data being the SSB. In this case, the UE may not send the second data before the guard period included in the second duration after terminating reception of the SSB.

[0384] For example, the UE ( Figures 9 to 13 The operation of the reference numeral 100 / 200 in FIG. 100 / 200 may be described as follows Figures 9 to 13 For example, refer to Fig.10 , the one or more processors 102 may control the one or more transceivers 106 and / or the one or more memories 104 to perform the switching.

[0385] The UE may send data or receive data in the second direction in a second duration after the switching.

[0386] Despite Figure 8 Although not shown in the figure, the UE may send capability information. That is, the BS may receive capability information from the UE. The capability information may include at least one of the capability information related to the switching time or the capability information related to the protection period described in Proposal 1 / Proposal 2. The BS may perform scheduling of the UE based on the capability information.

[0387] As described above, BS / UE signaling and operations (e.g., Proposals 1 / 2, Figure 7 / 8, etc.) can be provided by the device described below (e.g., Figures 9 to 13 For example, the BS may correspond to a first wireless device, and the UE may correspond to a second wireless device, and in some cases, the opposite situation may also be considered.

[0388] For example, BS / UE signaling and operations (e.g., Proposal 1 / 2 / Figure 7 / 8 etc.) can be Figures 9 to 13 One or more processors (e.g., reference numerals 102 and 202) in the UE, and BS / UE signaling and operations (e.g., Proposals 1 / 2, Figure 7 / 8, etc.) can be used to drive Figures 9 to 13 The commands / programs (eg, instructions and executable codes) of at least one processor (eg, 102 and 202) are stored in one or more memories (eg, reference numerals 104 and 204).

[0389] Communication system applied to the present disclosure

[0390] The various descriptions, functions, processes, proposals, methods and / or operational flowcharts of the present disclosure described in this document may be applied to, but not limited to, various fields requiring wireless communication / connection between devices (e.g., 5G).

[0391] Hereinafter, it will be described in more detail with reference to the accompanying drawings. In the following drawings / descriptions, unless otherwise specified, the same reference numerals may represent the same or corresponding hardware blocks, software blocks or functional blocks.

[0392] Fig. 9 The diagram shows a communication system (1) applied to the present disclosure.

[0393] refer to Fig. 9, the communication system applied to the present disclosure includes a wireless device, a base station (BS) and a network. In this article, a wireless device refers to a device that uses a radio access technology (RAT) (e.g., 5G new RAT (NR)) or a long-term evolution (LTE) to perform communication, and may be referred to as a communication / radio / 5G device. The wireless device may include, but is not limited to, a robot 100a, a vehicle 100b-1 and 100b-2, an extended reality (XR) device 100c, a handheld device 100d, a home appliance 100e, an Internet of Things (IoT) device 100f, and an artificial intelligence (AI) device / server 400. For example, a vehicle may include a vehicle with a wireless communication function, an autonomous driving vehicle, and a vehicle capable of communicating between vehicles. In this article, a vehicle may include an unmanned aerial vehicle (UAV) (e.g., a drone). XR devices may include augmented reality (AR) / virtual reality (VR) / mixed reality (MR) devices, and may be implemented in the form of a head-mounted device (HMD), a head-up display (HUD) installed in a vehicle, a television, a smartphone, a computer, a wearable device, a home appliance device, a digital signage, a vehicle, a robot, etc. Handheld devices may include smart phones, smart boards, wearable devices (e.g., smart watches or smart glasses), and computers (e.g., laptops). Home appliances may include televisions, refrigerators, and washing machines. IoT devices may include sensors and smart meters. For example, the BS and the network may be implemented as wireless devices, and a specific wireless device 200a may operate as a BS / network node relative to other wireless devices.

[0394] The wireless devices 100a to 100f may be connected to the network 300 through the BS 200. AI technology may be applied to the wireless devices 100a to 100f, and the wireless devices 100a to 100f may be connected to the AI ​​server 400 via the network 300. The network 300 may be configured using a 3G network, a 4G (e.g., LTE) network, or a 5G (e.g., NR) network. Although the wireless devices 100a to 100f may communicate with each other through the BS 200 / network 300, the wireless devices 100a to 100f may perform direct communication (e.g., side link communication) with each other without going through the BS / network. For example, the vehicles 100b-1 and 100b-2 may perform direct communication (e.g., vehicle-to-vehicle (V2V) / vehicle-to-everything (V2X) communication). An IoT device (e.g., a sensor) may perform direct communication with other IoT devices (e.g., a sensor) or other wireless devices 100a to 100f.

[0395] Wireless communication / connection 150a, 150b or 150c can be established between wireless devices 100a to 100f / BS 200 or BS 200 / BS 200. In this article, wireless communication / connection can be established through various RATs (e.g., 5G NR) such as uplink / downlink communication 150a, sidelink communication 150b (or D2D communication) or inter-BS communication (e.g., relay, integrated access backhaul (IAB)). The wireless device and the BS / wireless device can send / receive radio signals to each other through wireless communication / connection 150a and 150b. For example, wireless communication / connection 150a and 150b can send / receive signals through various physical channels. To this end, various configuration information configuration processes for sending / receiving radio signals, various signal processing processes (e.g., channel coding / decoding, modulation / demodulation and resource mapping / demapping) and at least a part of the resource allocation process can be performed based on various suggestions of the present disclosure.

[0396] Apparatus suitable for the present disclosure

[0397] Fig.10 The diagram illustrates a wireless device suitable for use with the present disclosure.

[0398] refer to Fig.10 , the first wireless device 100 and the second wireless device 200 can transmit radio signals through various RATs (e.g., LTE and NR). In this document, {the first wireless device 100 and the second wireless device 200} may correspond to Fig. 9 {wireless device 100x and BS200} and / or {wireless device 100x and wireless device 100x}.

[0399] The first wireless device 100 may include one or more processors 102 and one or more memories 104, and may further include one or more transceivers 106 and / or one or more antennas 108. The processor(s) 102 may control the memory(s) 104 and / or the transceiver(s) 106, and may be configured to implement the descriptions, functions, processes, proposals, methods, and / or operational flow charts disclosed in this document. For example, the processor(s) 102 may process the information in the memory(s) 104 to generate first information / signals, and then transmit a radio signal including the first information / signals through the transceiver(s) 106. The processor(s) 102 may receive a radio signal including second information / signals through the transceiver 106, and then store information obtained by processing the second information / signals in the memory(s) 104. The memory(s) 104 may be connected to the processor(s) 102 and may store various information related to the operation of the processor(s) 102. For example, (one or more) memories 104 may store software code including commands for executing some or all of the processes controlled by (one or more) processors 102, or for executing the descriptions, functions, processes, suggestions, methods, and / or operational flow charts disclosed in this document. In this document, (one or more) processors 102 and (one or more) memories 104 may be part of a communication modem / circuit / chip designed to implement a RAT (e.g., LTE or NR). (One or more) transceivers 106 may be connected to (one or more) processors 102 and send and / or receive radio signals through one or more antennas 108. Each of (one or more) transceivers 106 may include a transmitter and / or a receiver. (One or more) transceivers 106 may be used interchangeably with (one or more) radio frequency (RF) units. In the present disclosure, a wireless device may represent a communication modem / circuit / chip.

[0400] The second wireless device 200 may include at least one processor 202 and at least one memory 204, and further include at least one transceiver 206 and / or one or more antennas 208. The (one or more) processors 202 may control the (one or more) memories 204 and / or the (one or more) transceivers 206, and may be configured to implement the descriptions, functions, processes, proposals, methods and / or operational flow charts disclosed in this document. For example, the (one or more) processors 202 may process the information in the (one or more) memories 204 to generate third information / signals, and then transmit a radio signal including the third information / signals through the (one or more) transceivers 206. The (one or more) processors 202 may receive a radio signal including fourth information / signals through the (one or more) transceivers 206, and then store the information obtained by processing the fourth information / signals in the (one or more) memories 204. The (one or more) memories 204 may be connected to the (one or more) processors 202, and may store various information related to the operation of the (one or more) processors 202. For example, the memory (s) 204 may store software code including commands for executing some or all of the processes controlled by the processor (s) 202 or for executing the instructions, functions, processes, suggestions, methods, and / or operational flow charts disclosed in this document. In this document, the processor (s) 202 and the memory (s) 204 may be part of a communication modem / circuit / chip designed to implement a RAT (e.g., LTE or NR). The transceiver (s) 206 may be connected to the processor (s) 202 and transmit and / or receive radio signals via one or more antennas 208. Each of the transceivers (s) 206 may include a transmitter and / or a receiver. The transceiver (s) 206 may be used interchangeably with the RF unit (s). In this disclosure, a wireless device may represent a communication modem / circuit / chip.

[0401] In the following, the hardware elements of the wireless devices 100 and 200 will be described in more detail. One or more protocol layers may be implemented by, but not limited to, one or more processors 102 and 202. For example, one or more processors 102 and 202 may implement one or more layers (e.g., functional layers such as PHY, MAC, RLC, PDCP, RRC, and SDAP). One or more processors 102 and 202 may generate one or more protocol data units (PDUs) and / or one or more service data units (SDUs) according to the descriptions, functions, processes, proposals, methods, and / or operational flowcharts disclosed in this document. One or more processors 102 and 202 may generate messages, control information, data, or information according to the descriptions, functions, processes, proposals, methods, and / or operational flowcharts disclosed in this document. The one or more processors 102 and 202 may generate a signal (e.g., a baseband signal) including a PDU, SDU, message, control information, data, or information according to the description, functions, procedures, proposals, methods, and / or operational flowcharts disclosed in this document, and provide the generated signal to the one or more transceivers 106 and 206. The one or more processors 102 and 202 may receive a signal (e.g., a baseband signal) from the one or more transceivers 106 and 206 and obtain the PDU, SDU, message, control information, data, or information according to the description, functions, procedures, proposals, methods, and / or operational flowcharts disclosed in this document.

[0402] One or more processors 102 and 202 may be referred to as controllers, microcontrollers, microprocessors, or microcomputers. One or more processors 102 and 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 and 202. Firmware or software may be used to implement the description, function, process, proposal, method, and / or operational flowchart disclosed in this document, and the firmware or software may be configured to include modules, processes, or functions. Firmware or software configured to execute the description, function, process, proposal, method, and / or operational flowchart disclosed in this document may be included in one or more processors 102 and 202, or may be stored in one or more memories 104 and 204 so as to be driven by one or more processors 102 and 202. Firmware or software in the form of code, command, and command set may be used to implement the description, function, process, proposal, method, and / or operational flowchart disclosed in this document.

[0403] One or more memories 104 and 204 may be connected to one or more processors 102 and 202 and store various types of data, signals, messages, information, programs, codes, instructions, and / or commands. One or more memories 104 and 204 may be composed of read-only memory (ROM), random access memory (RAM), electrically erasable programmable read-only memory (EPROM), flash memory, hard disk drive, register, cache memory, computer-readable storage medium, and / or a combination thereof. One or more memories 104 and 204 may be located inside and / or outside of one or more processors 102 and 202. One or more memories 104 and 204 may be connected to one or more processors 102 and 202 via various technologies such as wired or wireless connections.

[0404] One or more transceivers 106 and 206 can send user data, control information and / or radio signals / channels mentioned in the method and / or operation flow chart of this document to one or more other devices. One or more transceivers 106 and 206 can receive user data, control information and / or radio signals / channels mentioned in the description, function, process, proposal, method and / or operation flow chart disclosed in this document from one or more other devices. For example, one or more transceivers 106 and 206 can be connected to one or more processors 102 and 202 and send and receive radio signals. For example, one or more processors 102 and 202 can perform control so that one or more transceivers 106 and 206 can send user data, control information or radio signals to one or more other devices. One or more processors 102 and 202 can perform control so that one or more transceivers 106 and 206 can receive user data, control information or radio signals from one or more other devices. One or more transceivers 106 and 206 may be connected to one or more antennas 108 and 208, and one or more transceivers 106 and 206 may be configured to send and receive user data, control information and / or radio signals / channels mentioned in the description, functions, processes, proposals, methods and / or operation flow charts disclosed in this document through one or more antennas 108 and 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 and 206 may convert received radio signals / channels, etc. from RF band signals to baseband signals, so as to facilitate processing of received user data, control information, radio signals / channels, etc. using one or more processors 102 and 202. One or more transceivers 106 and 206 may convert user data, control information, radio signals / channels, etc. processed using one or more processors 102 and 202 from baseband signals to RF band signals. To this end, one or more transceivers 106 and 206 may include (analog) oscillators and / or filters.

[0405] Examples of signal processing circuits to which the present disclosure is applied

[0406] Fig.11 The diagram shows the signal processing circuit used to transmit the signal.

[0407] refer to Fig.11 , the signal processing circuit 1000 may include a scrambler 1010 , a modulator 1020 , a layer mapper 1030 , a precoder 1040 , a resource mapper 1050 , and a signal generator 1060 . Fig.11 The operations / functions can be performed by but not limited to Fig.10 The processors 102 and 202 and / or the transceivers 106 and 206 are executed. Fig.11The hardware components can be Fig.10 For example, blocks 1010 to 1060 may be implemented by processors 102 and 202 and / or transceivers 106 and 206. Fig.10 In addition, blocks 1010 to 1050 may be implemented by processors 102 and 202. Fig.10 102 and 202, and block 1060 may be implemented by Fig.10 The transceivers 106 and 206 are implemented.

[0408] Codewords can be passed Fig.11 The signal processing circuit 1000 is converted into a radio signal. In this article, a codeword is a coded bit sequence of an information block. An information block may include a transport block (e.g., UL-SCH transport block, DL-SCH transport block). The radio signal may be transmitted through various physical channels (e.g., PUSCH and PDSCH).

[0409] Specifically, the codeword can be converted into a scrambled bit sequence by the scrambler 1010. A scrambling sequence for scrambling can be generated based on an initialization value, and the initialization value can include the ID information of the wireless device. The scrambled bit sequence can be modulated into a modulation symbol sequence by the modulator 1020. The modulation scheme may include pi / 2-binary phase shift keying (pi / 2-BPSK), m-phase shift keying (m-PSK), and m-quadrature amplitude modulation (m-QAM). The complex modulation symbol sequence can be mapped to one or more transmission layers by the layer mapper 1030. The modulation symbol of each transmission layer can be mapped (precoded) to the corresponding antenna port by the precoder 1040. The output z of the precoder 1040 can be obtained by multiplying the output y of the layer mapper 1030 by the N*M precoding matrix W. In this article, N is the number of antenna ports and M is the number of transmission layers. The precoder 1040 can perform precoding after performing transform precoding (e.g., DFT) on the complex modulation symbol. Alternatively, the precoder 1040 may perform precoding without performing transform precoding.

[0410] The resource mapper 1050 may map the modulation symbols of each antenna port to time-frequency resources. The time-frequency resources may include multiple symbols in the time domain (e.g., CP-OFDMA symbols and DFT-s-OFDMA symbols) and multiple subcarriers in the frequency domain. The signal generator 1060 may generate a radio signal from the mapped modulation symbols and may send the generated radio signal to other devices through each antenna. For this purpose, the signal generator 1060 may include an inverse fast Fourier transform (IFFT) module, a cyclic prefix (CP) inserter, a digital-to-analog converter (DAC), and a frequency up-converter.

[0411] The signal processing for the signal received in the wireless device can be performed in Fig.11 The signal processing processes 1010 to 1060 are configured in the opposite manner. For example, a wireless device (e.g., Fig.10 100 and 200) can receive a radio signal from the outside through an antenna port / transceiver. The received radio signal can be converted into a baseband signal by a signal restorer. To this end, the signal restorer may include a frequency downlink converter, an analog-to-digital converter (ADC), a CP remover, and a fast Fourier transform (FFT) module. Next, the baseband signal can be restored to a codeword through a resource demapping process, a post-coding process, a demodulation processor, and a descrambling process. The codeword can be restored to the original information block by decoding. Therefore, a signal processing circuit (not shown) for receiving a signal may include a signal restorer, a resource demapper, a post-encoder, a demodulator, a descrambler, and a decoder.

[0412] Examples of wireless devices applicable to the present disclosure

[0413] Fig.12 Another example of a wireless device applicable to the present disclosure is shown. The wireless device can be implemented in various forms according to the use case / service (see Fig. 9 ).

[0414] refer to Fig.12 , the wireless devices 100 and 200 may correspond to Fig.10 The wireless devices 100 and 200 may be composed of various elements, components, units / parts and / or modules. For example, each of the wireless devices 100 and 200 may include a communication unit 110, a control unit 120, a memory unit 130 and an additional component 140. The communication unit may include a communication circuit 112 and (one or more) transceivers 114. For example, the communication circuit 112 may include Fig.10 One or more processors 102 and 202 and / or one or more memories 104 and 204 in. For example, (one or more) transceivers 114 may include Fig.10 The control unit 120 is electrically connected to the communication unit 110, the memory 130, and the additional components 140, and controls the overall operation of the wireless device. For example, the control unit 120 can control the electrical / mechanical operation of the wireless device based on the program / code / command / information stored in the memory unit 130. The control unit 120 can send the information stored in the memory unit 130 to the outside (e.g., other communication devices) through the wireless / wired interface via the communication unit 110 or store the information received from the outside (e.g., other communication devices) through the wireless / wired interface in the memory unit 130 via the communication unit 110.

[0415] The additional component 140 may be configured differently depending on the type of wireless device. For example, the additional component 140 may include at least one of a power unit / battery, an input / output (I / O) unit, a drive unit, and a computing unit. The wireless device may be, but is not limited to, a robot ( Fig. 9 100a), vehicles ( Fig. 9 100b-1 and 100b-2), XR devices ( Fig. 9 100c), handheld devices ( Fig. 9 100d), household appliances ( Fig. 9 100e), IoT devices ( Fig. 9 100f), digital broadcasting terminals, holographic equipment, public safety equipment, MTC equipment, medical equipment, fintech equipment (or financial equipment), security equipment, climate / environmental equipment, AI servers / equipment ( Fig. 9 400), BS( Fig. 9 200), network nodes, etc. Depending on the use case / service, the wireless device can be used in a mobile or fixed location.

[0416] exist Fig.12 In the wireless devices 100 and 200, the entirety of the various elements, components, units / parts and / or modules in the wireless devices 100 and 100 may be connected to each other through a wired interface, or at least a portion thereof may be wirelessly connected through the communication unit 110. For example, in each of the wireless devices 100 and 100, the control unit 120 and the communication unit 110 may be connected by wire, and the control unit 120 and the first unit (e.g., 130 and 140) may be wirelessly connected through the communication unit 110. Each element, component, unit / part and / or module within the wireless devices 100 and 200 may further include one or more elements. For example, the control unit 120 may be composed of a set of one or more processors. For example, the control unit 120 may be composed of a set of a communication control processor, an application processor, an electronic control unit (ECU), a graphics processing unit and a memory control processor. As another example, the memory 130 may be composed of a random access memory (RAM), a dynamic RAM (DRAM), a read-only memory (ROM), a flash memory, a volatile memory, a non-volatile memory and / or a combination thereof.

[0417] Examples of portable devices applicable to the present disclosure

[0418] Fig.13The portable device applied to the present disclosure is shown. The portable device may include a smart phone, a smart board, a wearable device (e.g., a smart watch or smart glasses) or a portable computer (e.g., a notebook). The portable device may be referred to as a mobile station (MS), a user terminal (UT), a mobile subscriber station (MSS), a subscriber station (SS), an advanced mobile station (AMS) or a wireless terminal (WT).

[0419] refer to Fig.13 , the portable device 100 may include an antenna unit 108, a communication unit 110, a control unit 120, a memory unit 130, a power supply unit 140a, an interface unit 140b, and an I / O unit 140c. The antenna unit 108 may be configured as a part of the communication unit 110. Blocks 110 to 130 / 140a to 140c correspond to Fig.12 Frame 110 to 130 / 140.

[0420] The communication unit 110 may send signals (e.g., data and control signals) to other wireless devices or eNBs and receive signals (e.g., data and control signals) from other wireless devices or BSs. The control unit 120 may perform various operations by controlling the constituent elements of the portable device 100. The control unit 120 may include an application processor (AP). The memory unit 130 may store data / parameters / programs / codes / commands required to drive the portable device 100. The memory unit 130 may store input / output data / information. The power supply unit 140a may supply power to the portable device 100 and include a wired / wireless charging circuit, a battery, etc. The interface unit 140b may support the connection of the portable device 100 to other external devices. The interface unit 140b may include various ports (e.g., audio I / O ports and video I / O ports) for connecting to external devices. The I / O unit 140c may input or output video information / signals, audio information / signals, data and / or information input by a user. The I / O unit 140c may include a camera, a microphone, a user input unit, a display unit 140d, a speaker, and / or a haptic module.

[0421] As an example, in the case of data communication, the I / O unit 140c can acquire information / signals (e.g., touch, text, voice, image, or video) input by the user and can store the acquired information / signals in the memory unit 130. The communication unit 110 can convert the information / signals stored in the memory into radio signals and directly send the converted radio signals to other wireless devices or to the BS. The communication unit 110 can receive radio signals from other wireless devices or BSs and then restore the received radio signals to the original information / signals. The restored information / signals can be stored in the memory unit 130 and can be output as various types (e.g., text, voice, image, video, or tactile) through the I / O unit 140c.

[0422] Here, in this case, in addition to LTE, NR and 6G, the wireless communication technology implemented in the wireless device 100, 200 of the present disclosure may also include a narrowband Internet of Things for low-energy communication. In this case, for example, the NB-IoT technology may be an example of a low-power wide area network (LPWAN) technology, and may be implemented by standards such as LTE Cat NB1 and / or LTE CatNB2, and the present disclosure is not limited to the above names. Additionally or alternatively, the wireless communication technology implemented in the wireless device (100, 200) of the present disclosure may perform communication based on LTE-M technology. In this case, for example, the LTE-M technology may be an example of an LPWAN technology, and may be referred to as various names, such as enhanced machine type communication (eMTC). For example, the LTE-M technology may be implemented by at least any one of various standards (such as 1) LTE CAT 0, 2) LTE Cat M1, 3) LTE Cat M2, 4) LTE non-BL (non-bandwidth limited), 5) LTE-MTC, 6) LTE machine type communication, and / or 7) LTE M), and the present disclosure is not limited to the above names. Additionally or alternatively, the wireless communication technology implemented in the wireless device (100, 200) of the present disclosure may include at least any one of ZigBee, Bluetooth, and a low power wide area network (LPWAN) considering low energy communication, and the present disclosure is not limited to the above names. For example, ZigBee technology can generate a personal area network (PAN) related to small / low power digital communication based on various standards such as IEEE 802.15.4, and can be referred to as various names.

[0423] The above-mentioned embodiments are realized by combining the components and features of the present disclosure in a predetermined manner. Unless otherwise specified, each component or feature should be considered selectively. Each component or feature can be implemented without being combined with another component or feature. In addition, some components and / or features are combined with each other and can realize the embodiments of the present disclosure. The order of operations described in the embodiments of the present disclosure can be changed. Some components or features of an embodiment can be included in another embodiment, or can be replaced by corresponding components or features of another embodiment. It is obvious that some claims citing specific claims can be combined with other claims of claims other than citing specific claims to constitute embodiments, or new claims can be added by amendment after submitting the application.

[0424] The embodiments of the present disclosure may be implemented by various means, for example, hardware, firmware, software, or a combination thereof. When the embodiments are implemented by hardware, an embodiment of the present disclosure may be implemented by one or more application specific integrated circuits (ASICs), digital signal processors (DSPs), digital signal processing devices (DSPDs), programmable logic devices (PLDs), field programmable gate arrays (FPGAs), processors, controllers, microcontrollers, microprocessors, etc.

[0425] When the embodiment is implemented by firmware or software, an embodiment of the present disclosure may be implemented by a module, process, function, etc. that performs the above functions or operations. The software code may be stored in a memory and may be driven by a processor. The memory is provided inside or outside the processor and may exchange data with the processor in various well-known ways.

[0426] It is obvious to those skilled in the art that the present disclosure may be embodied in other specific forms without departing from the essential features of the present disclosure. Therefore, the foregoing detailed description should not be interpreted as limiting in all aspects, but should be considered as illustrative. The scope of the present disclosure should be determined by the reasonable interpretation of the attached claims, and all modifications within the equivalent scope of the present disclosure are included within the scope of the present disclosure.

[0427] [Industrial Availability]

[0428] Although the method of sending and receiving data in a wireless communication system supporting half-duplex FDD of the present disclosure has been described in conjunction with examples applied to 3GPP LTE / LTE-A systems and 5G systems (new RAT systems), the method is also applicable to various other wireless communication systems.

Claims

1. A method for receiving a synchronization signal block (SSB) by a user equipment in a wireless communication system supporting half-duplex frequency division duplex (FDD), the method comprising: receiving configuration information from a base station via higher layer signaling; as well as receiving the SSB from the base station based on the configuration information, wherein uplink transmission of at least one symbol included in a minimum time from transmission (Tx) to reception (Rx) for the user equipment before the first symbol of the SSB is not performed, and Therein, uplink transmission of at least one symbol within a minimum time from reception (Rx) to transmission (Tx) for the user equipment after the last symbol of the SSB is not performed.

2. The method according to claim 1, wherein: The uplink transmission is a transmission of at least one of a physical uplink shared channel (PUSCH), a physical uplink control channel (PUCCH) and / or a sounding reference signal (SRS).

3. The method according to claim 1, wherein: The SSB includes a primary synchronization signal (PSS), a secondary synchronization signal (SSS) and a physical broadcast channel (PBCH).

4. The method according to claim 1, wherein: The user equipment is a half-duplex user equipment.

5. The method according to claim 4, wherein: The half-duplex user equipment is a user equipment that cannot transmit and receive at the same time.

6. A user equipment, the user equipment being configured to receive a synchronization signal block (SSB) in a wireless communication system supporting half-duplex frequency division duplex (FDD), the user equipment comprising: at least one transceiver; at least one processor; as well as at least one memory operably connected to the at least one processor and storing instructions, the instructions performing operations upon execution by the at least one processor, the operations comprising: receiving configuration information from a base station via higher layer signaling; and receiving the SSB from the base station based on the configuration information, wherein uplink transmission of at least one symbol included in a minimum time from transmission (Tx) to reception (Rx) for the user equipment before the first symbol of the SSB is not performed, and Therein, uplink transmission of at least one symbol within a minimum time from reception (Rx) to transmission (Tx) for the user equipment after the last symbol of the SSB is not performed.

7. The user equipment according to claim 6, wherein: The uplink transmission is a transmission of at least one of a physical uplink shared channel (PUSCH), a physical uplink control channel (PUCCH) and / or a sounding reference signal (SRS).

8. The user equipment according to claim 6, wherein: The SSB includes a primary synchronization signal (PSS), a secondary synchronization signal (SSS) and a physical broadcast channel (PBCH).

9. The user equipment according to claim 6, wherein: The user equipment is a half-duplex user equipment.

10. The user equipment according to claim 9, wherein: The half-duplex user equipment is a user equipment that cannot transmit and receive at the same time.

11. A base station, the base station being configured to send a synchronization signal block (SSB) in a wireless communication system supporting half-duplex frequency division duplex (FDD), the base station comprising: at least one transceiver; at least one processor; as well as at least one memory operably connected to the at least one processor and storing instructions, the instructions performing operations upon execution by the at least one processor, the operations comprising: Sending configuration information to the user equipment via higher layer signaling; and sending the SSB to the user equipment based on the configuration information, wherein uplink reception of at least one symbol included in a minimum time from transmission (Tx) to reception (Rx) for the user equipment before the first symbol of the SSB is not performed, and Therein, uplink reception of at least one symbol within a minimum time from reception (Rx) to transmission (Tx) for the user equipment after the last symbol of the SSB is not performed.

12. The base station according to claim 11, wherein: The uplink reception is reception of at least one of a physical uplink shared channel (PUSCH), a physical uplink control channel (PUCCH) and / or a sounding reference signal (SRS).

13. The base station according to claim 11, wherein: The SSB includes a primary synchronization signal (PSS), a secondary synchronization signal (SSS) and a physical broadcast channel (PBCH).

14. The base station according to claim 11, wherein: The user equipment is a half-duplex user equipment.

15. The base station according to claim 14, wherein: The half-duplex user equipment is a user equipment that cannot transmit and receive at the same time.

Images