Method and apparatus for transmitting and receiving data in a wireless communication system supporting half-duplex frequency division duplexing - Patents.com

Abstract

This specification discloses a method for transmitting and receiving data in a wireless communication system supporting half-duplex frequency division duplexing, and a device supporting the same. The method includes receiving configuration information and downlink control information (DCI) through higher layer signaling, and configuring, based on at least one of the configuration information and the DCI, (i) a first time duration in which first data is transmitted in a first direction and (ii) a second time duration in which second data is transmitted in a second direction opposite to the first direction, and performing switching from the first time duration to the second time duration based on the first and second directions being opposite directions. Priorities of the first and second data are determined based on a predefined rule, and a guard period required for switching may be included in a time duration in which lower-priority data is transmitted in the first time duration or the second time duration.

Description

[Technical field]

[0001] TECHNICAL FIELD This disclosure relates to wireless communication systems, and more particularly to a method and apparatus supporting same for transmitting and receiving data based on half-duplex frequency division duplexing. [Background technology]

[0002] Mobile communication systems were developed to provide voice services while ensuring user activity. However, the scope of mobile communication systems has expanded beyond voice to data services, and currently, the explosive increase in traffic has caused resource shortages and users are demanding faster services, so there is a demand for more advanced mobile communication systems.

[0003] The next generation mobile communication system has many requirements, including the ability to accommodate explosive data traffic, a dramatic increase in transmission rate per user, a significantly increased number of connected devices, extremely low end-to-end latency, and high energy efficiency. To achieve this, various technologies are being researched, including dual connectivity, massive multiple input multiple output (MIMO), in-band full duplex, non-orthogonal multiple access (NOMA), super wideband support, and device networking. Summary of the Invention [Problem to be solved by the invention]

[0004] This specification proposes a method for transmitting and receiving data in a wireless communication system supporting half-duplex frequency division duplexing (FDD).

[0005] Specifically, this specification provides methods to set the slot format for half-duplex FDD operation and to set / define the switching time for downlink to uplink switching or uplink to downlink switching.

[0006] Furthermore, this specification proposes a method to configure a guard period for switching from downlink to uplink or from uplink to downlink for half-duplex FDD operation.

[0007] Furthermore, this specification proposes a method to prevent link direction collisions in half-duplex FDD operation.

[0008] The technical problems to be solved in this specification are not limited to the technical problems mentioned above, and other technical problems not mentioned can be clearly understood by a person having ordinary skill in the art to which the present invention belongs from the description below. [Means for solving the problem]

[0009] In a method for transmitting and receiving data by a user equipment (UE) in a wireless communication system supporting half-duplex frequency division duplexing according to an embodiment of the present specification, the method includes: receiving configuration information through higher layer signaling; receiving downlink control information (DCI); and performing switching from the first time duration to the second time duration based on at least one of the configuration information or the DCI, where (i) a first time duration in which first data is transmitted in a first direction, and (ii) a second time duration in which second data is transmitted in a second direction opposite to the first direction, and based on the first direction and the second direction being opposite directions, performing switching from the first time duration to the second time duration. Priorities of the first data and the second data are determined based on a predefined rule, and a guard period required for the switching may be included in a time duration in which low priority data is transmitted in the first time duration or the second time duration.

[0010] Further, in the method according to one embodiment of the present specification, the predefined rule is related to a type of information for scheduling the second data, and based on the second data being scheduled by the DCI, the second data is determined to have a higher priority than the first data, and the protection period may be included in the first time interval.

[0011] Further, in the method according to an embodiment of the present specification, the predefined rule may be associated with at least one type of the first data or the second data.

[0012] Further, in the method according to one embodiment of the present specification, based on the second data being a PRACH (physical random access channel) preamble, the protection period may be included in the first time interval, and the first data may not be received during the protection period included in the first time interval.

[0013] Furthermore, in the method according to one embodiment of the present specification, the protection period may be positioned after the last symbol in which the first time interval SSB is received, based on the first data being an SSB (Synchronization Signal Block) and the second data being a PRACH (physical random access channel) preamble.

[0014] Furthermore, in the method according to one embodiment of the present specification, based on the first data being an SSB, the protection period may be included in the second time interval, and the second data may not be transmitted before the protection period included in the second time interval after the end of reception of the SSB.

[0015] Furthermore, in the method according to an embodiment of the present specification, the setting information may include information related to the protection period.

[0016] Further, in the method according to an embodiment of the present specification, based on information related to the protection period, the protection period may be set i) per SCS or ii) per frequency range.

[0017] Further, in the method according to one embodiment of the present specification, a second value, which is a protection period corresponding to another SCS, is determined based on a first value, which is a protection period corresponding to a reference SCS, and the ratio of the reference SCS to the other SCS may be the same as the ratio of the first value to the second value.

[0018] Further, in the method according to an embodiment of the present specification, the protection period may include a switching time from the first time interval to a second time interval.

[0019] Furthermore, the method according to an embodiment of the present specification may further include transmitting capability information related to the switching time.

[0020] Also, in the method according to one embodiment of the present specification, when the first direction is a downlink, the second direction may be an uplink, and when the first direction is an uplink, the second direction may be a downlink.

[0021] In a user equipment (UE) for transmitting and receiving data in a wireless communication system supporting half-duplex frequency division duplexing according to an embodiment of the present specification, the terminal includes one or more transceivers, one or more processors, and one or more memories that store instructions related to operations performed by the one or more processors and are connected to the one or more processors, the operations including receiving configuration information through higher layer signaling, receiving downlink control information (DCI), and, based on at least one of the configuration information or the DCI, performing switching from the first time duration to the second time duration based on (i) a first time duration in which first data is transmitted in a first direction and (ii) a second time duration in which second data is transmitted in a second direction opposite to the first direction being configured, and the first direction and the second direction being opposite directions, wherein a priority of the first data and the second data is determined based on a predefined rule, and a guard period required for the switching is determined based on the first time duration. The period may be included in a time period for transmitting low priority data in the first time period or the second time period.

[0022] In an apparatus including one or more memories and one or more processors functionally connected to the one or more memories according to an embodiment of the present specification, the one or more processors control the apparatus to receive configuration information and downlink control information (DCI) through higher layer signaling, and based on at least one of the configuration information or the DCI, to perform switching from the first time duration to the second time duration based on (i) a first time duration in which first data is transmitted in a first direction and (ii) a second time duration in which second data is transmitted in a second direction opposite to the first direction, and the first direction and the second direction being opposite directions, whereby the priority of the first data and the second data are determined based on a predefined rule, and a guard period required for the switching may be included in a time duration in which low priority data is transmitted in the first time duration or the second time duration.

[0023] In one or more non-transitory computer-readable mediums storing one or more instructions according to an embodiment of the present specification, the one or more instructions executable by one or more processors include instructions for a user equipment (UE) receiving configuration information and downlink control information (DCI) through higher layer signaling, and performing switching from the first time duration to the second time duration based on at least one of the configuration information or the DCI, where (i) a first time duration in which first data is transmitted in a first direction and (ii) a second time duration in which second data is transmitted in a second direction opposite to the first direction are set, and the first direction and the second direction are opposite directions. Priorities of the first data and the second data are determined based on a predefined rule, and a guard period required for the switching may be included in a time duration in which low priority data is transmitted in the first time duration or the second time duration.

[0024] According to an embodiment of the present specification, in a wireless communication system supporting half-duplex frequency division duplexing, a method for a base station to transmit and receive data includes a step of transmitting configuration information through higher layer signaling and a step of transmitting downlink control information (DCI), and based on at least one of the configuration information or the DCI, (i) a first time duration in which first data is transmitted in a first direction and (ii) a second time duration in which second data is transmitted in a second direction opposite to the first direction are set, switching from the first time duration to the second time duration is performed based on the first direction and the second direction being opposite directions, priorities of the first data and the second data are determined based on a predefined rule, and a guard period required for the switching may be included in a time duration in which low-priority data is transmitted in the first time duration or the second time duration.

[0025] In accordance with an embodiment of the present specification, a base station for transmitting and receiving data in a wireless communication system supporting half-duplex frequency division duplexing includes one or more transceivers, one or more processors, and one or more memories storing instructions for operations performed by the one or more processors and connected to the one or more processors, the operations including transmitting configuration information through higher layer signaling and transmitting downlink control information (DCI), wherein, based on at least one of the configuration information or the DCI, (i) a first time duration during which first data is transmitted in a first direction and (ii) a second time duration during which second data is transmitted in a second direction opposite to the first direction are set, switching from the first time duration to the second time duration is performed based on the first direction and the second direction being opposite directions, priorities of the first data and the second data are determined based on a predefined rule, and a guard period required for the switching is determined. The period may be included in a time period for transmitting low priority data, either in the first time period or the second time period. Effect of the Invention

[0026] According to an embodiment of the present specification, data can be transmitted and received in a wireless communication system that supports half-duplex frequency division duplexing (FDD).

[0027] Additionally, embodiments herein may configure slot formats for half-duplex FDD operation and may configure switching times for downlink to uplink switching or uplink to downlink switching.

[0028] Additionally, according to embodiments herein, guard periods for downlink to uplink switching or uplink to downlink switching can be configured for half-duplex FDD operation.

[0029] Additionally, embodiments of the present disclosure may prevent link direction collisions in half-duplex FDD operation.

[0030] The effects obtained by the present invention are not limited to those mentioned above, and other effects not mentioned will be clearly understood by those having ordinary skill in the art to which the present invention pertains from the following description. [Brief description of the drawings]

[0031] The accompanying drawings, which are included as part of the detailed description to aid in understanding the present invention, provide embodiments of the present invention and, together with the detailed description, explain the technical features of the present invention.

[0032] [Figure 1] An example of the overall system structure of NR to which the method proposed in this specification can be applied is shown. [Diagram 2] 2 illustrates the relationship between uplink and downlink frames in a wireless communication system in which the method proposed herein can be applied; [Diagram 3] 1 shows an example of a frame structure in an NR system. [Figure 4] 1 shows an example of a resource grid supported by a wireless communication system in which the methods proposed herein can be applied. [Diagram 5] 1 shows an example of an antenna port and numerology specific resource grid to which the method proposed in this specification can be applied. [Figure 6] 1 illustrates physical channels and typical signal transmission used in a 3GPP (registered trademark: the same applies below) system. [Figure 7]1 illustrates an example of a signaling flow chart between a terminal and a base station to which the methods and / or embodiments proposed herein may be applied. [Figure 8] 1 illustrates an example of an operational flowchart of a terminal performing data transmission and reception to which the methods and / or embodiments proposed in this specification can be applied. [Figure 9] 1 illustrates a communication system 1 to which the present invention is applied. [Figure 10] 1 illustrates an example of a wireless device to which the present invention can be applied. [Figure 11] 2 shows a signal processing circuit for a transmission signal. [Figure 12] 10 shows another example of a wireless device to which the present invention is applied. [Figure 13] 1 illustrates a portable device to which the present invention is applied. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0033] Hereinafter, preferred embodiments of the present invention will be described in detail with reference to the accompanying drawings. The detailed description disclosed below in conjunction with the accompanying drawings is intended to describe exemplary embodiments of the present invention, and is not intended to show the only embodiments in which the present invention can be practiced. The following detailed description includes specific details to provide a complete understanding of the present invention. However, those skilled in the art will appreciate that the present invention can be practiced without such specific details.

[0034] In some cases, well-known structures and devices may be omitted or shown in block diagram form focusing on the core functions of each structure and device in order to avoid obscuring the concept of the present invention.

[0035] Hereinafter, downlink (DL) means communication from a base station to a terminal, and uplink (UL) means communication from a terminal to a base station. In the downlink, a transmitter may be part of a base station, and a receiver may be part of a terminal. In the uplink, a transmitter may be part of a terminal, and a 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. A base station (BS) may be replaced with terms such as a fixed station, Node B, eNB (evolved-NodeB), gNB (Next Generation NodeB), BTS (base transceiver system), access point (AP), network (5G network), AI system, RSU (road side unit), vehicle, robot, drone (Unmanned Aerial vehicle, UAV), AR (Augmented Reality) device, VR (Virtual Reality) device, etc. In addition, a terminal may be fixed or mobile, and may be replaced with terms such as 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, Device-to-Device (D2D) device, vehicle, robot, AI module, Unmanned Aerial Vehicle (UAV), Augmented Reality (AR) device, Virtual Reality (VR) device, etc.

[0036] The following technologies may be used for various wireless access systems, such as 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 in wireless technologies such as GSM (Global System for Mobile communications / GPRS (General Packet Radio Service / EDGE (Enhanced Data Rates for GSM Evolution)). OFDMA may be implemented in wireless technologies such as IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802-20, E-UTRA (Evolved UTRA), etc. UTRA is part of UMTS (Universal Mobile Telecommunications System). 3GPP (3rd Generation Partnership Project) LTE (Long Term Evolution) is part of E-UMTS (Evolved UMTS) that uses E-UTRA, and LTE-A (Advanced / 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.

[0037] For clarity of explanation, the following description will be based on a 3GPP communication system (e.g., LTE-A, NR), but the technical idea of ​​the present invention is not limited thereto. LTE refers to technology from 3GPP TS 36.xxx Release 8 onwards. In detail, LTE technology from 3GPP TS 36.xxx Release 10 onwards is called LTE-A, and LTE technology from 3GPP TS 36.xxx Release 13 onwards is called LTE-A pro. 3GPP NR refers to technology from TS 38.xxx Release 15 onwards. LTE / NR may be referred to as a 3GPP system. "xxx" refers to the detailed number of a standard document. LTE / NR may be commonly referred to as a 3GPP system. For background technology, terms, abbreviations, etc. used in the description of the present invention, reference may be made to matters described in standard documents published before the present invention. For example, the following documents may be referenced.

[0038] 3GPP LTE

[0039] - 36.211:Physical channels and modULation

[0040] - 36.212:Multiplexing and channel coding

[0041] - 36.213:Physical layer procedures

[0042] - 36.300:Overall description

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

[0044] 3GPP NR

[0045] - 38.211:Physical channels and modULation

[0046] - 38.212:Multiplexing and channel coding

[0047] - 38.213:Physical layer procedures for control

[0048] - 38.214:Physical layer procedures for data

[0049] - 38.300:NR and NG-RAN Overall Description

[0050] - 36.331:Radio Resource Control (RRC) protocol specification

[0051] As more communication devices require larger communication capacity, the need for improved mobile broadband communication compared to conventional radio access technology is emerging. In addition, massive MTC (Machine Type Communications), which connects a large number of devices and things and provides various services anytime and anywhere, is also one of the important issues to be considered in next-generation communication. In addition, the design of communication systems that take into account reliability and latency-sensitive services / terminals is being discussed. Thus, the introduction of next-generation radio access technology that takes into account eMBB (enhanced mobile broadband communication), Mmtc (massive MTC), URLLC (ULtra-Reliable and Low Latency Communication), etc. is being discussed, and for convenience, the technology is referred to as NR in this specification. NR is an expression that shows an example of 5G wireless access technology (radio access technology, RAT).

[0052] The three main requirement areas for 5G include (1) the Enhanced Mobile Broadband (eMBB) area, (2) the massive Machine Type Communication (mMTC) area, and (3) the Ultra-reliable and Low Latency Communications (URLLC) area.

[0053] Some use cases may require multiple areas for optimization, while others may only be focused on one Key Performance Indicator (KPI). 5G will support such diverse use cases in a flexible and reliable way.

[0054] eMBB goes far beyond basic mobile Internet access and covers rich interactive work, media and entertainment applications in the cloud or augmented reality. Data is one of the core drivers of 5G, and it is possible that we will not see dedicated voice services for the first time in the 5G era. In 5G, voice is expected to be handled simply as an application using the data connection provided by the communication system. The main causes for the increased traffic volume are the increase in content size and the increase in the number of applications that require high data transmission rates. Streaming services (audio and video), interactive video and mobile Internet connections will be more widely used as more devices are connected to the Internet. Many such applications require always-on connectivity to push real-time information and notifications to users. Cloud storage and applications are proliferating on mobile communication platforms, which can be applied to both work and entertainment, and cloud storage is a particular use case that will drive the growth of uplink data transmission rates. 5G will also be used for remote work in the cloud, which requires much lower end-to-end latency to maintain an excellent user experience when haptic interfaces are used. Entertainment, e.g., cloud gaming and video streaming, is another key factor that increases the demand for mobile broadband capabilities. Entertainment is essential on smartphones and tablets everywhere, including in high mobility environments such as trains, cars, and airplanes. Another use case is augmented reality and information retrieval for entertainment, where augmented reality requires very low latency and instantaneous data volume.

[0055] Also, one of the most anticipated use cases for 5G is its ability to seamlessly connect embedded sensors in all sectors, i.e. mMTC. It is predicted that the number of potential IoT devices will reach 20.4 billion by 2020. Industrial IoT is one area where 5G will play a key role in enabling smart cities, asset tracking, smart utilities, agriculture and security infrastructure.

[0056] URLLC includes new services transforming industries through ultra-reliable / available low-latency links such as remote control of critical infrastructure and self-driving vehicles. Reliability and latency levels are essential for smart grid control, industrial automation, robotics, drone control and coordination.

[0057] A number of use cases will be described in more detail below.

[0058] 5G can complement fiber-to-the-home (FTTH) and cable-based broadband (or DOCSIS) as a means of delivering streams rated at hundreds of megabits per second to gigabits per second. Such high speeds are required to deliver TV at resolutions of 4K and above (6K, 8K and beyond), as well as virtual and augmented reality. Virtual reality (VR) and augmented reality (AR) applications include most immersive sports. Certain application programs may require special network configurations. For example, in the case of VR games, gaming companies may have to integrate their core servers with the network operator's edge network servers to minimize latency.

[0059] Automotive is expected to be an important new driver in 5G with many use cases for mobile communications to vehicles. For example, entertainment for passengers will require simultaneous high capacity and high mobility mobile broadband, because future users will expect continuous high quality connectivity regardless of their location and speed. Another use case in the automotive field is the augmented reality dashboard, which displays information overlaid on top of what the driver sees through the front window, identifying objects in the dark and informing the driver about the object's distance and movement. In the future, wireless modules will enable communication between vehicles, information exchange between vehicles and supporting infrastructure, and between cars and other connected devices (e.g. devices carried by pedestrians). Safety systems will be able to guide drivers on alternative courses of action to drive more safely and reduce the risk of accidents. The next step will be remotely piloted or self-driven vehicles, which will require very reliable and very fast communication between different autonomous vehicles and between cars and infrastructure. In the future, autonomous vehicles will perform all driving activities, leaving the driver to focus only on traffic anomalies that the vehicle itself cannot identify. The technical requirements for autonomous vehicles demand ultra-low latency and ultra-high speed reliability to increase traffic safety to a level unattainable by humans.

[0060] Smart cities and smart homes, also referred to as smart society, are embedded with high density wireless sensor networks. A distributed network of intelligent sensors identifies requirements for cost and energy efficient maintenance of the city or home. A similar setup can be made for each home. Temperature sensors, window and heating controllers, burglar alarms and home appliances are all wirelessly connected. Many of these sensors typically have low data transmission rates, low power consumption and low cost. However, for example, real-time HD video may be required by certain types of devices for surveillance.

[0061] The consumption and distribution of energy, including heat or gas, is highly decentralized, requiring automated control of distributed sensor networks. A smart grid interconnects such sensors using digital information and communication technologies to collect and act upon information. This information can include supplier and consumer actions, allowing the smart grid to improve the efficiency, reliability, economy, sustainability of production, and distribution of fuels, such as electricity, in an automated manner. A smart grid can also be viewed as another sensor network with low latency.

[0062] The health sector has many applications that can benefit from mobile communications. Communication systems can support telemedicine to provide clinical care over long distances. This reduces the barriers of distance and can improve access to medical services that are not sustainably available in remote rural areas. It can also be used to save lives in critical care and emergency situations. Mobile-based wireless sensor networks can provide remote monitoring and sensing for parameters such as heart rate and blood pressure.

[0063] Wireless and mobile communications are becoming more and more important in industrial applications. Wiring is expensive to install and maintain. The possibility to replace cables with reconfigurable wireless links is therefore an attractive opportunity in many industrial sectors. However, achieving this requires that wireless connections operate with similar latency, reliability and capacity as cables, and that their management is simplified. Low latency and very low error probability are new requirements that need to be addressed with 5G.

[0064] Logistics and freight tracking are important use cases for mobile communications that allow for inventory and package tracking anywhere using location-based information systems. Logistics and freight tracking use cases typically require low data rates, but require wide range and reliable location information.

[0065] New RAT systems including NR use OFDM transmission schemes or similar transmission schemes. New RAT systems may follow OFDM parameters different from those of LTE. Or, new RAT systems may follow the existing LTE / LTE-A numerology but have a larger system bandwidth (e.g., 100 MHz). Or, one cell may support multiple numerologies. That is, terminals operating with different numerologies can coexist in one cell.

[0066] A numerology corresponds to one subcarrier spacing in the frequency domain. By scaling the reference subcarrier spacing to an integer N, different numerologies can be defined.

[0067] Definition of Terms

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

[0069] gNB: A node that supports NR as well as linking with NGC.

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

[0071] Network slice: A network slice is a network defined by an operator to provide an optimized solution for a specific market scenario calling for specific requirements with end-to-end coverage.

[0072] network function: A network function is a logical node within the network infrastructure that has a well-defined external interface and a well-defined functional behavior.

[0073] NG-C: The control plane interface used as the NG2 reference point between the new RAN and NGC.

[0074] NG-U: User plane interface used for the NG3 reference point between the new RAN and NGC.

[0075] Non-standalone NR: A deployment configuration in which a gNB requests an LTE eNB to an EPC as an anchor for control plane connection, or requests an eLTE eNB to an NGC as an anchor for control plane connection.

[0076] Non-independent E-UTRA: A deployment configuration in which an eLTE eNB requests a gNB from the NGC as an anchor for control plane connectivity.

[0077] User Plane Gateway: The termination point of the NG-U interface.

[0078] System in general

[0079] FIG. 1 is a diagram showing an example of the overall system structure of NR to which the method proposed in this specification can be applied.

[0080] Referring to Figure 1, the NG-RAN consists of the gNB, which provides the NG-RA user plane (new AS sublayer / PDCP / RLC / MAC / PHY) and control plane (RRC) protocol termination for the UE (User Equipment).

[0081] The gNBs are interconnected via an Xn interface.

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

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

[0084] NR (New Rat) Numerology and Frame Structure

[0085] In the NR system, multiple numerologies can be supported. Here, the numerology can be defined by the subcarrier spacing and the overhead of the cyclic prefix (CP). In this case, multiple subcarrier spacing can be derived by scaling the basic subcarrier spacing to an integer N (or μ). In addition, the numerology used can be selected independently of the frequency band, even if it is assumed that very low subcarrier spacing is not used at very high carrier frequencies.

[0086] In addition, the NR system can support a variety of frame structures according to multiple numerologies.

[0087] Below, we will look at Orthogonal Frequency Division Multiplexing (OFDM) numerology and frame structure that can be considered in NR systems.

[0088] A number of OFDM numerologies supported in the NR system can be defined as shown in Table 1.

[0089] [Table 1]

[0090] NR supports multiple numerologies (or subcarrier spacing (SCS)) to support various 5G services. For example, a 15kHz SCS supports wide areas in traditional mobile phone bands, a 30kHz / 60kHz SCS supports dense-urban, lower latency and wider carrier bandwidth, and a 60kHz or higher SCS supports bandwidths larger than 24.25GHz to overcome phase noise.

[0091] The NR frequency band is defined by two types of frequency ranges (FR1 and FR2). FR1 and FR2 can be configured as shown in Table 2 below. FR2 can also refer to millimeter wave (mmW).

[0092] [Table 2]

[0093] [Table 3]

[0094] FIG. 2 shows the relationship between uplink and downlink frames in a wireless communication system in which the method proposed herein can be applied.

[0095] As shown in FIG. 2, the transmission of uplink frame number i from a terminal (User Equipment, UE) starts T from the start of the corresponding downlink frame at the terminal. TA =NTA T S It must start earlier.

[0096] [Table 4]

[0097] Not all terminals can transmit and receive simultaneously, which means that not all OFDM symbols of a downlink slot or an uplink slot can be used.

[0098] [Table 5]

[0099] [Table 6]

[0100] [Table 7]

[0101] An example of a frame structure in an NR system is shown in Figure 3. Figure 3 is merely for convenience of explanation and does not limit the scope of the present invention.

[0102] Table 4 is an example of the case where μ=2, i.e., the subcarrier spacing (SCS) is 60 kHz. Referring to Table 3, one subframe (or frame) can include four slots, and the one subframe={1, 2, 4} slots shown in FIG. 3 is an example, and the number of slots that can be included in one subframe can be defined as shown in Table 3.

[0103] Also, a mini-slot may consist of 2, 4, or 7 symbols, or may consist of more or less symbols.

[0104] In relation to physical resources in an NR system, antenna ports, resource grids, resource elements, resource blocks, carrier parts, etc. can be considered.

[0105] Hereinafter, the physical resources that can be considered in an NR system will be described in detail.

[0106] First, with respect to antenna ports, the antenna ports are defined such that the channel on which the symbols on an antenna port are carried can be inferred from the channel on which the other symbols on the same antenna port are carried. If the large-scale properties of the channel on which the symbols on one antenna port are carried can be inferred from the channel on which the symbols on the other antenna port are carried, the two antenna ports can be said to be in a quasi co-located (QC / QCL) relationship. Here, the large-scale properties include one or more of delay spread, Doppler spread, frequency shift, average received power, and received timing.

[0107] FIG. 4 shows an example of a resource grid supported by a wireless communication system in which the methods proposed herein can be applied.

[0108] [Table 8]

[0109] In this case, as shown in FIG. 5, one resource grid can be set for each numerology μ and antenna port p.

[0110] FIG. 5 shows an example of a resource grid by antenna port and numerology to which the method proposed herein can be applied.

[0111] [Table 9]

[0112] Point A serves as a common reference point for the resource block grid and can be obtained as follows:

[0113] - offsetToPointA for PCell downlink indicates the frequency offset between point A and the lowest subcarrier of the lowest resource block overlapped with the SS / PBCH block used by the UE for initial cell selection, expressed in resource block units assuming 15 kHz subcarrier spacing for FR1 and 60 kHz subcarrier spacing for FR2;

[0114] - absoluteFrequencyPointA indicates the frequency-location of point A expressed as an absolute radio-frequency channel number (ARFCN).

[0115] Common resource blocks are numbered from 0 upwards in the frequency domain for the subcarrier spacing setting μ.

[0116] [Table 10]

[0117] Bandwidth part (BWP)

[0118] In the NR system, up to 400 MHz can be supported per carrier. If a UE operating on such a wideband carrier always operates with the radio frequency (RF) module of the entire carrier turned on, the UE battery consumption may be large. Alternatively, when considering multiple use cases (e.g., eMBB, URLLC, mMTC, V2X, etc.) operating within one wideband carrier, different neurologies (e.g., subcarrier spacing) can be supported for each frequency band within the carrier. Alternatively, each UE may have a different capability for the maximum bandwidth. In consideration of this, the BS can instruct the UE to operate only with a portion of the bandwidth of the wideband carrier rather than the entire bandwidth, and the portion of the bandwidth is referred to as a bandwidth part (BWP). In the frequency domain, a BWP is a subset of contiguous common resource blocks defined for a neuroradio group μi in bandwidth part i on a carrier, for which one neurology (e.g., subcarrier spacing, CP length, slot / minislot duration) can be configured.

[0119] On the other hand, the BS can configure one or more BWPs within one carrier configured to the UE. Alternatively, when UEs are concentrated in a specific BWP, some UEs may be moved to other BWPs for load balancing. Alternatively, some spectrum in the entire bandwidth may be excluded in consideration of frequency domain inter-cell interference cancellation between adjacent cells, and both BWPs of the cells may be configured in the same slot. That is, the BS may configure at least one DL UL / BWP for a UE associated with a wideband carrier, activate at least one DL / ULBWP configured at a specific time (by L1 signaling, which is a physical layer control signal, a MAC control element (CE), which is a MAC layer control signal, or RRC signaling, etc.), and may instruct the UE to switch to another configured DL / UL BWP (by L1 signaling, MACCE, or RRC signaling, etc.), or may configure a timer value so that the UE switches to a specified DL / UL BWP when the timer expires. An activated DL / UL BWP is specifically called an active (DL / UL BWP). In situations such as when the UE is in the initial access process or before the RRC connection of the UE is set up, the UE may not receive configuration for the DL / UL BWP. In such a situation, the DL / UL BWP assumed by the UE is the initial active DL / UL BWP.

[0120] Physical Channels and General Signaling

[0121] Figure 6 illustrates physical channels and general signal transmission used in a 3GPP system. In a wireless communication system, a terminal receives information from a base station via a downlink (DL), and transmits information to the base station via an uplink (UL standard). Information exchanged between the base station and the terminal includes data and various control information, and various physical channels exist depending on the type / application of the information exchanged.

[0122] When the terminal is powered on or newly enters a cell, the terminal performs an initial cell search such as synchronizing with the base station (S601). To this end, the terminal receives a Primary Synchronization Signal (PSS) and a Secondary Synchronization Signal (SSS) from the base station to synchronize with the base station and obtain information such as a cell ID. Then, the terminal receives a Physical Broadcast Channel (PBCH) from the base station to obtain broadcast information within the cell. Meanwhile, the terminal receives a Downlink Reference Signal (DL RS) in the initial cell search stage to check the state of the downlink channel.

[0123] After completing the initial cell search, the terminal can obtain more specific system information by receiving a physical downlink control channel (PDCCH) and a physical downlink shared channel (PDSCH) based on information carried on the PDCCH (S602).

[0124] Meanwhile, when the terminal first connects to the base station or has no radio resources for signal transmission, the terminal can perform a random access procedure (RACH) to the base station (S603 to S606). To this end, the terminal can transmit a specific sequence as a preamble through a physical random access channel (PRACH) (S603 and S605) and receive a response message (RAR Random Access Response) to the preamble through a PDCCH and a corresponding PDSCH. In the case of a contention-based RACH, the terminal can further perform a contention resolution procedure (S606).

[0125] After performing the above-mentioned procedure, the terminal can then 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 procedure. In particular, the terminal can receive downlink control information (DCI) via the PDCCH.

[0126] Specifically, the UE monitors a set of PDCCH candidates at monitoring occasions configured in one or more control element sets (CORESETs) on a serving cell according to a corresponding search space configuration. The set of PDCCH candidates monitored by the UE is defined in terms of a search space set, which may be a common search space set or a UE-specific search space set. A CORESET consists of a set of (physical) resource blocks having a time duration of 1 to 3 OFDM symbols. A network may be configured such that a UE has multiple CORESETs. The UE monitors PDCCH candidates in one or more search space sets. Here, monitoring means attempting to decode the PDCCH candidates in the search space. If the UE successfully decodes one of the PDCCH candidates in the search space, the UE determines that it has detected a PDCCH in the corresponding PDCCH candidate, and performs PDSCH reception or PUSCH transmission based on DCI in the detected PDCCH.

[0127] The PDCCH is used to schedule DL transmission on the PDSCH and UL transmission on the PUSCH. Here, the DCI on the PDCCH includes a downlink assignment (i.e., DL grant) including at least modulation and coding format and resource allocation information related to the PDSCH, or an uplink grant including modulation and coding format and resource allocation information related to the PUSCH. The formats of the DCI are different depending on the purpose of use. For example, in an NR system, DCI format 0_0 and DCI format 0_1 ​​are used for scheduling the PUSCH in one cell, and DCI format 1_0 and DCI format 1_1 are used for scheduling the PDSCH in one cell. DCI format 2_0 can be CRC scrambled by the SFI-RNTI and is used to inform the slot format.

[0128] The above descriptions (e.g., 3GPP system, frame structure, physical channels, and general signal transmission, etc.) may be applied / used in combination with the methods and / or embodiments proposed herein, or may be supplemented to clarify the technical features of the methods proposed herein. In this specification, " / " may mean "and" including all of the content separated by " / " or "or" including only a part of the separated content.

[0129] Furthermore, for ease of explanation, the following terms are used in this specification in abbreviated form.

[0130] - UE: User Equipment

[0131] - redcap UE: reduced capability UE

[0132] - SSB: Synchronization Signal Block

[0133] - BW: Bandwidth

[0134] - BWP: Bandwidth Part

[0135] - SCS: subcarrier spacing

[0136] TB: Transport Block

[0137] -TDRA:Time domain resource allocation

[0138] - RO: RACH occasion

[0139] - MG: measurement gap

[0140] - DL: downlink

[0141] - UL:Uplink

[0142] - Rx:Reception

[0143] - Tx:Transmission

[0144] - FR:Frequency range

[0145] - PDCCH:Physical downlink control channel

[0146] PDSCH:Physical downlink shared channel

[0147] - PUCCH:Physical uplink control channel

[0148] - PUSCH:Physical uplink shared channel

[0149] - RNTI:Radio Network Temporary Identifier

[0150] - RRC:Radio resource control

[0151] - MAC-CE:medium access control-control element

[0152] - DCI:Downlink control information

[0153] - FDD:Frequency division duplexing

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

[0155] - CRC: Cyclic Redundancy Check

[0156] - SIB: System Information Block

[0157] - SIB1: SIB1=RMSI (Remaining Minimum System Information) for NR equipment. Broadcasts information necessary for cell connection of NR equipment.

[0158] - CORESET (COntrol REsource SET): Time / frequency resource on which the NR UE attempts candidate PDCCH decoding

[0159] - CORESET♯0: CORESET for Type0-PDCCH CSS set of NR device

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

[0161] - SIB1-R: (additional) SIB1 for reduced capability NR devices. May be limited to being generated in a separate TB from SIB1 and transmitted on a separate PDSCH.

[0162] - CORESET♯0-R: CORESET♯0 for reduced capability NR devices

[0163] - Type0-PDCCH-R CSS set: reduced Set of search spaces for the UE to monitor a set of PDCCH candidates with DCI format CRC scrambled by SI-RNTI.

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

[0165] - RSA (Redcap standalone): A cell that supports only Redcap devices or Redcap services.

[0166] In addition to the above-mentioned main use cases of 5G, such as mMTC, eMBB, and URLLC, the importance / interest of use cases such as a use case in which mMTC and eMBB are combined, or a use case in which mMTC and URLLC are combined, is increasing. In order to efficiently support such use cases, methods for designing terminals suitable for the use cases are being considered from the perspectives of device cost, power consumption, form factor, etc.

[0167] For the purposes of this specification, a normal NR terminal that supports at least one of the major 5G use cases is referred to as a "NR (normal UE)" or "NR device." An NR UE may be a terminal that has all of 5G's key capabilities (e.g., peak data rate, user experienced data rate, latency, mobility, connection density, energy efficiency, spectrum efficiency, and area traffic efficiency).

[0168] On the other hand, a terminal in which some capabilities have been intentionally reduced to achieve reduced device costs, power saving, and a small form factor is referred to as a (NR) reduced capability UE / reduced capability device, or reduced (NR) "redcap UE" or "redcap device." Redcap UE may be a terminal designed for use case areas spanning the above-mentioned mMTC and eMBB, or mMTC and URLLC.

[0169] In this specification, for convenience of explanation, the 5G use case area spanning mMTC and eMBB, or mMTC and URLLC, will be referred to as the "redcap use case."

[0170] An example of a Redcap use case could be in the connected industries sector. Sensors and actuators can be connected to the 5G network and core. Use cases and requirements for massive Industrial Wireless Sensor Networks (IWSN) could be included. URLLC, which has very high requirements, as well as relatively low-end services that require compact device form factors with battery life of several years could be offered. The requirements for such services are higher than Low Power Wide Area (LPWA, i.e. LTE-M / NB-IOT), but lower than URLCC and eMBB. For example, devices supporting such an environment could include pressure sensors, humidity sensors, thermometers, motion sensors, accelerometers, actuators, etc.

[0171] As another example of Redcap use case, in the case of smart cities, the smart city vertical covers data collection and processing to more efficiently monitor and control urban resources and provide services to city residents. In particular, the deployment of surveillance cameras is an integral part of smart cities, but also for factories and industrial companies.

[0172] As yet another example of a Redcap use case, wearable use cases may include smart watches, rings, smart health (eHealth) related devices, medical monitoring devices, and the like.

[0173] Depending on the low power wireless area (LPWA) terminal (e.g., LTE-M, NB-IoT, etc.), the above-mentioned Redcap use cases may not be supported in terms of bit rate, latency, etc. On the other hand, NR terminals can functionally support the above-mentioned Redcap use cases, but may be inefficient in terms of terminal manufacturing costs, form factor, battery life, etc. Supporting the above-mentioned Redcap use case areas in 5G networks with Redcap UEs having characteristics such as low cost, low power, and small form factor (i.e., small device size) can reduce terminal manufacturing and maintenance costs.

[0174] Redcap use cases have quite diverse requirements in terms of terminal complexity, target bit rate, latency, power consumption, etc. In this specification, the requirements that a redcap UE must meet are referred to as "redcap requirements." Redcap requirements can be divided into generic requirements that can be commonly applied to all redcap use cases and use case specific requirements that can only be applied to some use cases.

[0175] For example, typical redcap requirements can be summarized as follows:

[0176] - Device complexity / cost: The main motivation for new device types is to reduce device cost and complexity compared to Rel-15 / Rel-16 high-end eMBB and URLLC devices. This is especially the case for industrial sensors.

[0177] - Device size: A requirement of most use cases is that the standard enables the design of devices in a compact form factor.

[0178] - Deployment Scenario: The system must support all FR1 / FR2 bands for FDD and TDD.

[0179] For example, the redcap requirements by use case can be summarized as follows:

[0180] <Use Case 1: Industrial Wireless Sensor>

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

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

[0183] - Battery: Minimum several years

[0184] - Availability of communication services: 99.99%

[0185] - Stationary

[0186] <Use Case 2: Video Surveillance>

[0187] - Reference bitrate: <2~4 Mbps for economical video; ~7.5~25 Mbps for high-end video (high UL traffic)

[0188] - Latency: < 500 ms

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

[0190] <Use case 3: Wearables>

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

[0192] - Peak bitrate: 150 Mbps downlink, 50 Mbps uplink

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

[0194] Table 5 shows the schematic common requirements and use case-specific requirements for the three representative redcap use cases.

[0195] [Table 11]

[0196] The redcap requirements can be met by various features (combinations) provided by the terminal and base station. The following are examples of features and sub-features that the terminal / base station supports to meet the redcap requirements.

[0197] In terms of reducing the complexity of the Redcap UE, the Redcap UE can be characterized by i) a reduction in the number of UE RX / Tx antennas, ii) a reduction in UE bandwidth, iii) half-duplex FDD support, iv) relaxed UE processing time, and v) relaxed UE processing capability. Furthermore, in terms of power saving, i) PDCCH monitoring due to a smaller number of blind decoding (BD) and control channel element (CCE) restrictions can be reduced, ii) extended DRX of RRC inactive and / or idle can be applied, or iii) radio resource management (RRM) of stationary devices can be relaxed. In addition, the Redcap UE can be characterized by coverage recovery / enhancement.

[0198] Among the features of the red cap UE, half-duplex FDD is a method traditionally used for low cost / low complexity terminals. At the same time, in the case of full-duplex FDD terminals that support transmission and reception, a duplexer must be used to eliminate the effect of interference from the transmission signal on the reception signal, but half-duplex FDD operation limits the simultaneous transmission and reception capabilities, and by replacing the duplexer for interference elimination with a low-cost RF (radio frequency) switch, terminal costs can be reduced.

[0199] Half-duplex FDD operation in this specification may be as defined in LTE: in half-duplex FDD operation, a terminal cannot transmit and receive simultaneously, whereas in full-duplex FDD there is no such restriction.

[0200] LTE also defines two types (eg, Type A and Type B) of half-duplex FDD operation as follows:

[0201] For Type-A half-duplex FDD operation, the guard period is generated by the UE as follows:

[0202] - Not receiving the last part of a downlink subframe immediately preceding an uplink subframe from the same UE

[0203] For Type-B half-duplex FDD operation, the guard periods, each referred to as a half-duplex guard subframe, are generated by the UE as follows:

[0204] - not receiving a downlink subframe immediately preceding an uplink subframe from the same UE;

[0205] - Not receiving a downlink subframe immediately following an uplink subframe from the same UE

[0206] In the above guard period, there are guard periods in which no DL or UL transmission occurs. This can also be replaced by the term guard time.

[0207] Hereinafter, methods and / or embodiments for supporting half-duplex FDD operation in NR are proposed. Specifically, Proposal 1 proposes a method for setting a slot format for half-duplex FDD operation, setting / defining a switching time for switching from downlink to uplink or uplink to downlink, and setting a guard period. Proposal 2 proposes a method for preventing link direction collision in half-duplex FDD operation.

[0208] <Proposal 1>

[0209] A slot format indicates how each of the symbols in one slot is used. Multiple slot formats can be predefined, and a particular slot format can be indicated / set by a slot format index. In NR, each slot format can be composed of at least one of DL symbols, UL symbols, or flexible symbols. 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 yet another example, there may be i) a slot format consisting of DL symbols and flexible symbols, ii) a slot format consisting of UL symbols and flexible symbols, or iii) a slot format consisting of DL symbols and UL symbols. As yet another example, there may be a slot format including both DL symbols, UL symbols, and flexible symbols.

[0210] For half-duplex FDD operation, the base station may semi-statically configure (i) the UL carrier to a slot format consisting of UL-only symbols or a combination of UL and flexible symbols, and (ii) the DL carrier to a slot format consisting of DL-only symbols or a combination of DL and flexible symbols, via common or dedicated RRC signaling. The method of configuring the opposite slot format via common or dedicated RRC signaling may be similar to the conventional method of configuring the TDD slot format via the RRC parameters 'tdd-UL-DL-ConfigurationCommon' or 'tdd-UL-DL-ConfigurationCommon Dedicated'.

[0211] Alternatively, for half-duplex FDD operation, the base station can configure both UL and DL carriers as flexible symbols, e.g., in a simple manner to half-configure the slot formats as all flexible symbols, unless common or dedicated RRC parameters for separate slot format configuration for each of the DL or UL carriers are defined / indicated, the terminal can assume that the slot formats of that carrier are all configured with flexible symbols.

[0212] Based on the prior information method, the slot formats of the DL carrier and the UL carrier can be semi-statically configured. Based on the slot format configuration, the base station can ensure that half-duplex FDD operation is supported by essentially ensuring that simultaneous transmission and reception are not required from the perspective of a half-duplex FDD terminal through semi-static and / or dynamic scheduling via RRC and / or DCI signaling.

[0213] <Method 1>

[0214] To support half-duplex FDD operation, the time required for switching from A to B can be predefined. Hereinafter, for convenience of explanation, the operation of switching from A to B is expressed as "A-to-B switching". The data / signal transmission direction in A and the data / signal transmission direction in B can be opposite to each other. For example, if A is a downlink, B is an uplink, and it can be expressed as "DL-to-UL switching". Alternatively, if A is an uplink, B is a downlink, and it can be expressed as "UL-to-DL switching". Also, the time required for switching from A to B is expressed as "A-to-B switching time". Hereinafter, downlink (DL) means communication from a base station to a terminal, and uplink (UL) means communication from a terminal to a base station. Also, from the perspective of a terminal, DL RX means an operation of receiving a DL channel / signal from a base station, and UL TX means an operation of transmitting a UL channel / signal to a base station.

[0215] The DL-to-UL switching time required by a terminal supporting half-duplex FDD (for example, T DU ) may be predefined and the terminal may not be expected to perform DL Rx or UL Tx operation during that time.

[0216] For example, the DL-to-UL switching time T DU may be included in a DL symbol / slot before a UL Tx, and the terminal may not expect a DL Rx during that time. In other words, the terminal may not receive a DL Rx during that time. The base station may not perform a DL transmission during that time.

[0217] For example, the DL-to-UL switching time T DUmay be included in the UL symbol / slot following the DL Rx, and the terminal may not expect a UL Tx during that time. That is, in the case of paired spectrum operation, a terminal that is not capable of full-duplex FDD communication may expect the ending T of the last received DL symbol. DU In other words, the terminal may not transmit UL during this time. The base station may not expect to receive a UL Tx from the terminal during this time.

[0218] Similarly, the UL-to-DL switching time (e.g., T_UD) required by a half-duplex FDD terminal may be predefined, and the terminal may not expect to perform DL Rx or UL Tx operation during that period.

[0219] For example, the UL-to-DL switching time T UD may be included in a UL symbol / slot before a DL Rx, and the terminal may not expect a UL Tx during that time. In other words, the terminal may not transmit a UL during that time. The base station may not expect to receive a UL Tx from the terminal during that time.

[0220] For example, the UL-to-DL switching time T UD may be included in the DL symbol / slot following the UL Tx, and the terminal may not expect a DL Rx during that time. That is, in the case of paired spectrum operation, a terminal not capable of full-duplex FDD communication may receive T after the end of the last transmitted UL symbol. UD You may not expect to receive DL much faster than that.

[0221] [Table 12]

[0222] Instead of predefining the DL-to-UL switching time or the UL-to-DL switching time as a fixed value as in the above example, the terminal may report the switching time supported by the terminal to the base station in the form of terminal capability (or capability information). For example, the terminal may report the N value (i.e., N sw Alternatively, a set of multiple N values ​​may be predefined (e.g., in a table format), and the terminal may report the N values ​​it supports from the set of N values. DU' N UD' A particular value of N can be reported to the base station, possibly by the terminal reporting a minimum switching time value, thereby reporting to the base station that it supports all values ​​above it.

[0223] Based on the terminal capabilities reported by the terminal, the base station can set the switching time to the terminal via an RRC parameter. In this case, if the corresponding parameter does not exist (or is not indicated / configured), the terminal can assume a default switching time.

[0224] For example, the terminal may assume the largest N value among multiple predefined N values ​​as the default switching time. The reason for assuming the largest N value as the default switching time may be to prevent the base station scheduling from becoming overly complicated in a situation where terminals supporting different switching times coexist by making all terminals operating in half-duplex FDD operate assuming the same N value.

[0225] As another example, the N value that the UE reports as being supportable through the capability information may be assumed as the default switching time, or, if the UE reports as being supportable for multiple N values, the smallest N value among them may be assumed as the default switching time.

[0226] The set of N values ​​may be divided according to the switching time supported by the terminal. For example, when two sets of N values ​​are predefined, the N value that a low-cost / low-noise terminal (e.g., Redcap UE) can support may be equal to or greater than the N value supported by a high-cost / high-complexity terminal (e.g., NR UE), and the high-cost / high-complexity terminal (e.g., NR UE) may be equal to or greater than the N value supported by the low-cost / low-noise terminal (e.g., Redcap UE). It is possible that a high complexity terminal reports via its capability information that it supports all of the two sets of N values.

[0227] For example, N DU and N UD When the values ​​are set separately, the switching time for capability 1 and the switching time for capability 2 can be defined in two table formats. A high-cost / high-complexity terminal can support both capability 1 and capability 2, and a low-cost / low-complexity terminal can report to the base station through capability information that it supports only capability 1. A high-cost / high-complexity terminal can expect the switching time to be set through higher layer signaling at one of the values ​​in Table 6 and Table 7. Meanwhile, a low-cost / low-complexity terminal can expect the switching time to be set through higher layer signaling only at the value in Table 6. That is, a low-cost / low-complexity terminal may not expect the switching time to be set to the value in Table 7.

[0228] Table 6 shows the switching time N DU and N UD Example values ​​are:

[0229] [Table 13]

[0230] Table 7 shows the switching time N DU and N UD Example values ​​are:

[0231] [Table 14]

[0232] The values ​​in Tables 6 and 7 are merely examples for the convenience of explanation, and do not limit the technical scope of the present invention. The values ​​in Table 7 correspond to 25600*1 / 480E3*4096*1E6=13us in FR1 (e.g., 410MHz to 7125MHz) and 13792*1 / 480E3*47us in FR2 (e.g., 24250MHz to 52600MHz), which are examples of values ​​mainly required for RF circuit switching, and may be determined to different values ​​according to the requirements of terminal manufacturers, etc.

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

[0234] <Method 2>

[0235] In method 2, a method is proposed to define / configure a guard period to support half-duplex FDD operation in NR. In the guard period, all DL and UL transmissions are suspended. The term guard period can be used interchangeably with the term guard time. The switching time in method 1 is included in the guard period.

[0236] The guard period may be defined in units of symbols or slots, and the terminal may report information regarding the guard period to the base station in the form of capability information. A guard period defined in units of symbols may be defined as a guard symbol and may be expressed as the number of OFDM symbols used as the guard period (e.g., G_sym). A guard period defined in units of slots may be defined as a guard slot and may be expressed as the number of slots used as the guard period (e.g., G_slot).

[0237] The guard period for Type-A half-duplex FDD operation can be defined as G_sym, A guard symbols.

[0238] The guard period for Type-A half-duplex FDD operation may be generated by the terminal as follows.

[0239] - No G_sym and no A DL symbol are received immediately before the UL slot from the same UE.

[0240] Example 1-1 may be a case where a guard period is secured by defining a guard symbol only in the case of DL-to-UL switching, and in the case of UL-to-DL switching, the base station secures the guard period through TA (Timing advance) setting. This method may be appropriate when the required guard period is small, i.e., in the case of Type A, etc.

[0241] For Type A half-duplex FDD operation, the guard period is So it can be generated as follows:

[0242] - no G_sym, no A1 DL symbol is received immediately before the UL slot from the same UE, and

[0243] - No G_sym, A2 DL symbol received immediately following a UL slot from the same UE.

[0244] Example 1-2 is a case where a guard period is set for both DL-to-UL and UL-to-DL switching. For example, it may be difficult for the base station to secure sufficient time for switching in TA because the required guard period (or switching time) is not small.

[0245] In the case of Type B half-duplex FDD operation, additional time for frequency retuning operation is required due to reasons such as the use of a single oscillator for low cost / complexity, and a guard period value larger than that of Type A may generally be required. Therefore, it can be defined as G_sym,B (>G_sym,A) guard symbols or G_slot guard slot. G_sym,B can have a value larger than G_sym,A.

[0246] Example 2-1) Type B For half-duplex FDD operation, guard periods, each of which is a half-duplex guard slot, may be generated by the terminal as follows:

[0247] - no G_slot or B1 DL slot is received immediately before the UL slot from the same UE, and

[0248] - No G_slot or B2 DL slot is received immediately after a UL slot from the same UE,

[0249] Example 2-1 may be the case where the required guard period in the case of Type B is large, the guard period is defined in slot units, and all the guard periods are set for DL-to-UL and UL-to-DL.

[0250] Example 2-2) For half-duplex FDD operation of type B, the guard period, each referred to as a half-duplex guard symbol, may be generated by the terminal as follows:

[0251] - no G_sym, no B1 DL symbol is received immediately before the UL slot from the same UE, and

[0252] - No G_sym, B2 DL symbol received immediately following a UL slot from the same UE.

[0253] Example 2-2 shows a case where guard periods are set for both DL-to-UL and UL-to-DL switching, and the guard period of Type B is defined not in slot units but as multiple symbols. For example, it may be difficult for the base station to secure enough time for switching in TA because the required guard period (or switching time) is not small.

[0254] A guard period is defined without distinguishing the type of half-duplex FDD, and the guard period (or switching time) information required for each type of terminal is transmitted to the base station in the form of a capability report, and the base station can set the guard symbol by referring to the corresponding information.

[0255] Example 3) For half-duplex FDD operation, the guard periods, each referred to as a half-duplex guard symbol, may be generated by the terminal as follows:

[0256] - not receiving G_sym, 1 DL symbol immediately preceding a UL slot from the same UE, and - Same U

[0257] G_sym and 2 DL symbols are not received immediately after the UL slot from E.

[0258] In the above example, the G value (e.g., G_sym, G_slot, G_sym, A or G_sym, B, etc.) can be defined for each frequency range. This is because the performance and cost of the elements used for each frequency range may differ, and the associated circuit switching and RF readjustment time may differ. For example, the G value can be set / defined separately for FR1 (e.g., 410 MHz to 7125 MHz) and FR2 (e.g., 24250 MHz to 52600 MHz).

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

[0260] Alternatively, the G values ​​(e.g., G_sym, G_slot, G_sym,A, or G_sym,B) can be set / defined by simply scaling the guard symbol / slot for each SCS with the SCS ratio. For example, if the guard symbol / slot for a specific SCS (e.g., SCS1) is defined, the guard symbol(s) / slot for SCS2 (> SCS1) can be defined / set by simply scaling it to the SCS2 / SCS1 value based on that.

[0261] As described above, when applying simple scaling of guard symbols / slots for each SCS according to the SCS ratio, it may be necessary to define an SCS value that serves as a reference for defining the guard symbols / slots, i.e., a reference SCS.

[0262] For example, from the viewpoint of signaling overhead, the reference SCS can be defined as the lowest SCS used for data transmission in a corresponding frequency range or frequency band without additional signaling parameters. As a specific example, as shown in Table 2 above, 15, 30, and 60 KHz are supported in FR1, and 60, 120, and 240 kHz are supported in FR2, so 15 kHz can be defined as the reference SCS in FR1, and 60 kHz can be defined as the reference SCS for guard symbol / slot setting in FR2.

[0263] As another example, in the case of a terminal configured to monitor DCI format 2_0 in FDD, the reference SCS for each UL / DL slot format can be configured via a higher layer. In this case, the base station does not define a separate parameter (or there is no separate parameter) in consideration of signaling overhead, and the terminal can assume that the reference SCS for the guard symbol / slot / subframe is the reference SCS for the slot format. That is, the SCS associated with DCI format 2_0 can be assumed to be the reference SCS. The DCI format 2_0 is CRC scrambled by the SFI-RN ​​TI and used to indicate the slot format.

[0264] In this case, in the A-to-B switching operation, when the reference SCS of A and the reference SCS of B are different (for example, when the reference SCS of UL and the reference SCS of DL are different), the guard period (for example, guard symbol / slot / subframe) can be defined based on the reference SCS of A. In the A-to-B switching, when A is the source carrier and B is the carrier, the guard period can be defined / set 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 it belongs. That is, in the A-to-B switching, if the guard period belongs to A, it can be defined based on the A carrier, and if it belongs to B, it can be defined based on the B carrier. Alternatively, as in the above example 1-1 / 1-2 / destination 2-1 / 2-2 / 3, if all the guard symbols / slots belong to DL and are generated in the form of noRX or DRX (Discrete reception), the guard period can be defined based on the reference SCS of the DL carrier.

[0265] [Table 15]

[0266] The number of symbols / slots / subframes of the guard period can be set based on the method and / or embodiment proposed in Method 2 above.

[0267] <Method 3>

[0268] Meanwhile, to support half-duplex FDD operation in NR, flexible symbols / slots can also be defined to be included in the guard period. Currently, in NR, a terminal that is not configured to monitor DCI format 2_0 can perform DL reception and UL transmission as instructed by DCI or higher layer configuration in flexible symbols / slots configured via higher layer signaling. If such a flexible symbol / slot is included in the guard period, the terminal may not be expected to perform DL Rx or UL Tx operation.

[0269] In the above-mentioned method 1, a method of defining the A-to-B switching time to support half-duplex FDD is proposed. However, when the method of setting the flexible symbol / slot to the guard period in method 3 is applied to method 1, the switching time can be defined as shown in the following example.

[0270] For example, DL-to-UL switching time T DU may be included in the UL or flexible symbol / slot following DL Rx, and the terminal may not expect UL Tx or flexible operation during that time. In other words, in the case of paired spectrum operation, a terminal that is not capable of full-duplex FDD communication may expect T after the end of the last received DL symbol. DU Do not expect to transmit on the UL or flexible symbols / slots any earlier than this.

[0271] For example, DL-to-UL switching time T DUmay be included in the DL or flexible symbol / slot following the UL Tx, and the terminal may not expect DL Rx or flexible operation during that time. That is, in the case of paired spectrum operation, a terminal that is not capable of full-duplex FDD communication may expect T after the end of the last transmitted UL symbol. DU One may not expect to receive DL or flexible symbols / slots much earlier than this.

[0272] In the case of an extended CP, since the OFDM symbol length and the number of symbols in a slot may be different from those of a normal CP, a separate guard period definition may be required, and the same method as that assuming a normal CP described above (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 that defines a guard period on a slot basis, a separate definition may be made for the extended CP only for the guard symbol that defines a guard period on a symbol basis.

[0273] Alternatively, the guard period of the extended CP may be determined based on the guard period defined based on the general CP without defining a separate setting, capability, etc. for the extended CP. For example, an OFDM symbol of an extended CP that is fully or partially overlapped with an OFDM symbol of a general CP defined as a guard symbol may be defined as a guard symbol having an extended CP. That is, when one of the overlapped general CP symbols is a guard symbol, the terminal may determine the extended CP symbol as a guard symbol.

[0274] <Proposal 2>

[0275] Although the base station can support half-duplex FDD operation through scheduling using the method of Proposal 1 described above, if it is difficult for the base station to accurately predict the UL transmission of the terminal or difficult to practically avoid collisions with resources that are periodically set in advance for a specific use, a method for avoiding link direction collisions for synchronized half-duplex FDD operation between the base station and the terminal may be required. In Proposal 2 of this specification, a method for preventing link direction collisions in half-duplex FDD operation is proposed.

[0276] As mentioned above, for convenience of explanation, switching from A to B in half-duplex FDD operation is referred to as "A-to-B switching". For example, switching from downlink to uplink can be represented as "DL-to-UL switching" and switching from uplink to downlink can be represented as "UL-to-DL switching".

[0277] A-to-B switching may be (i) indicated by DCI or (ii) indicated by higher layer signaling (e.g., RRC, MAC-CE). Indication of A-to-B switching by DCI may be interpreted as scheduling for B being indicated by DCI, and may also be interpreted as resources for B being allocated by DCI. Indication of A-to-B switching via higher layer signaling may mean that A-to-B switching is indicated based on other information / signals excluding DCI. Indication of A-to-B switching via higher layer signaling may be interpreted as scheduling for B being indicated by higher layer signaling, and may also be interpreted as resources for B being allocated by higher layer signaling.

[0278] The link direction collision refers to a collision that may occur during DL-to-UL switching or UL-to-DL switching in half-duplex FDD operation. This may refer to a case where time domain resources associated with a DL carrier overlap with time domain resources associated with a UL carrier. Therefore, proposal 2 proposes a method for preventing / avoiding such collisions and / or a method for operating a terminal / base station in a collision situation.

[0279] In addition, the terminal of Proposal 2 may correspond to the above-mentioned redcap UE.

[0280] <Method 1>

[0281] In half-duplex FDD operation, the position of the guard period and / or the operation of the terminal and the base station can be set / instructed depending on which layer of signal or information the A-to-B switching occurs based on. In other words, the position of the guard period and / or the operation of the terminal and the base station can be set / instructed depending on whether the A-to-B switching is i) caused by B scheduled based on DCI (i.e., dynamic manner) or ii) caused by B scheduled based on signaling excluding DCI (e.g., higher layer signaling) (i.e., configured manner).

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

[0283] Alternatively, in half-duplex FDD operation, if uplink to downlink switching (UL-to-DL switching) occurs by DL Rx indicated by DCI (i.e., DL reception is scheduled by DCI), the terminal may not expect UL Tx during the guard period before the DL slot / symbol. This may be interpreted as the terminal dropping UL Tx during the guard period. In this case, the guard period may exist before the DL section in the time domain. In other words, the guard period may be included in the UL section in the time domain, and the terminal may not expect UL Tx during the guard period. If the guard period occupies a part or some symbols of the slot, the terminal may drop the entire slot or only the part / symbols of the slot that overlap with the guard period.

[0284] In half-duplex FDD operation, if DL-to-UL switching occurs due to UL Tx configured through higher layer signaling after DL Rx indicated by DCI, the UE may not expect UL Tx during the guard period after the DL slot / symbol. This can be interpreted as the UE dropping UL Tx during the guard period. In this case, the guard period may be present after the DL section in the time domain. In other words, the guard period may be included in the UL section in the time domain, and the UE may not transmit on the UL during the guard period. Alternatively, if the guard period occupies a part of a slot or some symbols included in the UL section, the UE may i) drop the entire slot, or ii) drop only the part / symbol that overlaps with the guard period in the slot. Dropping only the overlapped part / symbol may be limited to only some UL transmissions (e.g., SRS transmissions).

[0285] In half-duplex FDD operation, if UL-to-DL switching occurs due to DL Rx configured through higher layer signaling after a DCI-indicated UL Tx slot / symbol transmission, the terminal may not expect DL Rx during the guard period after the UL Tx slot / symbol. This may be interpreted as the terminal dropping DL Rx during the guard period. In this case, the guard period may be after the UL section in the time domain. In other words, the guard period may be included in the DL section in the time domain, and the terminal may not expect DL Rx during the guard period. The base station may not transmit DL Rx to the terminal during the guard period after the UL Tx slot / symbol.

[0286] According to method 1 of Proposal 2 described above, when the scheduling methods of A and B in A-to-B switching are different from each other, i.e., one is scheduled based on DCI and the other is scheduled based on signaling excluding DCI (e.g., higher layer signaling), scheduling based on DCI may be given priority, and the guard period may be included in the time interval set based on the higher layer signaling.

[0287] <Method 2>

[0288] In half-duplex FDD operation, A-to-B switching can set / instruct the location of the guard period and / or the operation of the terminal and base station depending on the type / content of the information / signal being transmitted at A and / or B.

[0289] First embodiment

[0290] The first embodiment is an example in which information / signal transmitted on the UL in DL-to-UL switching or UL-to-DL switching is a PRACH preamble.

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

[0292] The UE may transmit an optional access preamble via the PRACH as message 1 (Msg1) of an optional access process in the UL. The optional access preamble transmitted via the PRACH may be referred to as a PRACH preamble.

[0293] Two different lengths of arbitrary connection preamble sequences are supported: the long sequence length 839 applies to subcarrier spacings of 1.25 and 5 kHz, and the short sequence length 139 applies to subcarrier spacings of 15, 30, 60 and 120 kHz.

[0294] Multiple preamble formats are defined by one or more RACH OFDM symbols and different cyclic prefixes (and / or guard times). A RACH configuration for a cell is provided to a UE in the system information of the cell. The RACH configuration includes information on the subcarrier spacing of PRACH, available preambles, preamble formats, etc. The RACH configuration includes association information between SSBs and RACH (time-frequency) resources. The UE transmits an optional connection preamble on a RACH time-frequency resource associated with a detected or selected SSB.

[0295] A threshold value of SSBs for RACH resource association can be set by the network, and the RACH preamble is transmitted or retransmitted based on the SSBs whose reference signal received power (RSRP) measured based on the SSBs satisfies the threshold value. For example, the UE can select one of the SSBs that satisfies the threshold value, and transmit or retransmit the RACH preamble based on the RACH resource associated with the selected SSB.

[0296] In half-duplex FDD operation, if DL-to-UL switching occurs due to PRACH preamble transmission during DL Rx, it can be defined that the UE does not expect DL Rx during the guard period before a valid RO (RACH occasion, hereinafter, RO) in which the PRACH preamble can be transmitted. This can also be interpreted as the UE dropping DL Rx during the guard period. In this case, the guard period can be located before the valid RO in the time domain. In other words, the guard period can be included in the DL section in the time domain, and the UE may not expect DL Rx during the guard period.

[0297] The above example may mean that when switching from a dynamically scheduled DL (e.g., a DL scheduled by DCI) to a valid RO for PRACH preamble transmission, the valid RO is prioritized over a dynamic DL, and when switching from a semi-statically configured DL (e.g., a DL configured via higher layer signaling) to a valid RO for PRACH preamble transmission, the valid RO is prioritized over a semi-statically configured DL.

[0298] That is, for the collision case where a dynamically scheduled DL transmission overlaps with a VALID RO, a valid RO may be prioritized over a dynamic DL. Similarly, for the collision case where a semi-statically configured DL transmission overlaps with a valid RO, a valid RO may be prioritized over a semi-static DL. However, in both of the above cases, unlike the TDD case, an RX-TX (i.e., DL-To-UL) switching time must be considered for HD-FDD operation in the FDD band before the valid RO. In other words, the UE may not expect to receive on the DL later than the RX-to-TX switching time before the valid RO starts. Similarly, a TX-to-RX switching time may be considered for HD-FDD operation in the FDD band after the valid RO. In other words, the UE may not expect to receive on the DL earlier than the TX-to-RX switching time after the valid RO ends. A valid RO herein may or may not include N_gap symbols before the valid RO. Here, N_gap (i.e., N gap ) can be defined as shown in Table 8 below.

[0299] Table 8 shows the N of different preamble SCSs. gap This is an example.

[0300] [Table 16]

[0301] The operation according to the first embodiment of Proposal 2 described above can be defined as shown in Table 9.

[0302] [Table 17]

[0303] In Table 9, N_GP symbols represents a value defined in symbol units to provide the switching time. For example, N_GP symbols can be defined in symbol units for each SCS based on the method of Proposal 1 described above. As an example, N_GP = 1 symbol can be defined for all SCSs, or N_GP can be set to 1, 2, and 4 for 15 kHz, 30 kHz, and 60 kHz SCSs, respectively. N_GP can be defined in T_c time units like the switching time in Proposal 1 described above.

[0304] As another example, when the DL Rx is an operation instructed by DCI (i.e., scheduled by DCI), an RO existing after the guard period from the last DL symbol may be defined as a valid RO in which PRACH preamble transmission is possible. That is, in half-duplex FDD operation, PRACH preamble transmission may not be expected in an RO starting before a time that is a guard period away from the last DL symbol for DL ​​Rx instructed by DCI. In other words, the UE may transmit a PRACH preamble in a valid RO after a time that is at least a guard period away from the last symbol of DL RX. This may mean that DL Rx dynamically scheduled by DCI is given higher priority than the PRACH preamble.

[0305] As another example, in half-duplex FDD operation, if DL-to-UL switching occurs due to PRACH preamble transmission from SSB Rx over RO, PRACH preamble transmission may be allowed on RO starting after the guard period from the last symbol of SSB transmission. In other words, a valid RO may have to satisfy the above condition.

[0306] Alternatively, if UL-to-DL switching occurs due to SSB Rx after PRACH preamble transmission over an RO, if there is an SSB before the guard period from the last symbol of the RO, PRACH preamble transmission may not be expected on the RO. That is, a valid RO may not meet the above condition. In other words, PRACH preamble transmission may be allowed on an RO that ends before the guard period from the first symbol of an SSB transmission. In other words, a valid RO may meet the above condition. Also, if there is a PRACH preamble during the guard period before the SSB transmission symbol, PRACH preamble transmission may not be expected on the RO.

[0307] Based on the above example, the valid ROs can be defined as follows:

[0308] [Table 18] JPEG0007631379000019.jpg112140

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

[0310] Second embodiment

[0311] The second embodiment is an example in which information / signals received in DL in DL-to-UL switching or UL-to-DL switching are SSBs (Synchronization Signal Blocks). UEs can perform cell search, system information acquisition, beam alignment for initial connection, DL measurement, etc. based on the SSBs. The SSBs are mixed with SS / PBCH (Synchronization Signal / Physical Broadcast channel) blocks. The SSBs are composed of PSSs (Primary Synchronization Signals), SSSs (Secondary Synchronization Signals) and PBCHs (Physical Broadcast Channels). The SSBs transmit four consecutive OFDMs or PBCHs. The PSSs and SSSs are each composed of one OFDM symbol and one symbol, and each OFDM symbol is composed of PSS, PBCH, SSS / PBCH and 127 subcarriers, and the PBCH is composed of three OFDM symbols and 576 subcarriers.

[0312] In half-duplex FDD operation, if DL-to-UL switching occurs for UL Tx after SSB Rx, the terminal may not expect UL Tx during the guard period after the last symbol of the SSB transmission. This can be interpreted as the terminal dropping the UL Tx during the guard period. In this case, the guard period may be after the last symbol of the SSB transmission in the time domain. In this case, a part or the whole of the guard period may overlap with the UL section, and the terminal may not transmit on the UL during the guard period. If the guard period occupies a part or a part of symbols of the corresponding UL slot, the terminal may drop the entire UL slot, or drop only the part / symbols of the corresponding slot that overlap with the guard period. The operation of dropping only the overlapped part / symbols may be limited to only some UL transmissions (e.g., SRS transmissions).

[0313] In half-duplex FDD operation, if UL-to-DL switching occurs due to SSB Rx after UL Tx, the terminal may not expect UL Tx during the guard period before the SSB transmission start symbol. This can be interpreted as the terminal dropping UL Tx during the guard period. In this case, in the time domain, part or all of the guard period may overlap with the UL section, and the terminal may not transmit on the UL during the guard period. If the guard period occupies part or some symbols of the corresponding UL slot, the terminal may drop the entire UL slot or drop only the part / symbols of the corresponding slot that overlap with the guard period. The operation of dropping only the overlapped part / symbols may be limited to only some UL transmissions (e.g., SRS transmissions).

[0314] For collision cases where a dynamically scheduled UL transmission (e.g., a UL transmission scheduled via DCI) overlaps with an SSB, the SSB may be prioritized over a dynamic UL. Similarly, for collision cases where a semi-statically configured UL transmission (e.g., a UL transmission configured via higher layer signaling) overlaps with an SSB, the SSB may be prioritized over a semi-static UL. However, in both of the above cases, unlike the TDD case, the RX-to-TX (i.e., DL-to-UL) switching time must be considered for HD-FDD operation in the FDD band after the set of SSB symbols. That is, the UE may not expect to transmit on the UL any faster than the RX-to-TX switching time after the end of the last received DL symbol for the SSB. Similarly, the TX-to-RX switching time may be considered for HD-FDD operation in the FDD band before the set of SSB symbols. That is, the UE may not expect to transmit on the UL any slower than the TX-to-RX switching time before the start of the first received DL symbol for the SSB.

[0315] For the collision case where semi-statically configured UL transmission and SSB are overlapped, the semi-statically configured UL transmission includes a valid RO and a valid PUSCH opportunity for two-stage RACH. In both cases, unlike TDD, the RX-to-TX (or TX-to-RX) switching time must be accounted for HD-FDD operation of the FDD band after (or before) the set of SSB symbols. The valid RO in this specification may or may not include N_gap symbols before the valid RO. Here, N_gap can be defined as shown in Table 8 above.

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

[0317] [Table 19]

[0318] Meanwhile, the UE may need to receive SSBs for measurement before, after, or during UL transmission. In an SSB burst set, up to L SSBs may be transmitted, and the number / location of SSBs actually transmitted may vary depending on the BS / cell. The number / location of SSBs actually transmitted may provide the UE with information on the actually transmitted SSBs used for rate matching and measurement. For SSB reception for measurement, the base station may set an SSB-based RRM measurement timing configuration (SMTC) window and set all or some SSBs within the window to be received for measurement. In this case, a time interval for receiving SSBs for measurement may be defined, and it may be assumed that the UE does not expect UL Tx or does not receive a request for UL transmission from the base station during the corresponding interval. The SSB reception interval for measurement in half-duplex FDD operation may be defined as an interval consisting of an SSB transmission symbol and a guard period before, after, or before and after the SSB transmission symbol. The method may be applied only when timing synchronization between serving cells is guaranteed. In addition, a measurement gap (MG) can be configured for intra / inter frequency measurement, during which the UE is assumed not to expect DL Rx and / or UL Tx. Considering UL-to-DL switching, DL-to-UL switching, and the guard period required during switching in half-duplex FDD operation, the SSB reception period in the MG can be defined as from {MG start point + guard period} to {MG end point - guard period}.

[0319] If the guard period is large in half-duplex FDD operation, the number of SSB receptions in the MG may be reduced, which may affect measurement performance. To solve the problem of measurement performance degradation that may occur when the guard period is large, a new MG value including the guard period can be defined and made available to the terminal (by higher layer configuration) in half-duplex FDD operation.

[0320] <Method 3>

[0321] When a collision occurs between DL and UL, the priority can be determined according to the transmission type of DL and UL. For example, the transmission type of DL can be a mapping type of PDSCH, and the transmission type of UL can be a mapping type of PUSCH. This can mean that the transmission type of DL and UL is determined by the DMRS position in each (mini) slot / subframe.

[0322] For example, if a DMRS for PUSCH transmission is transmitted in the first symbol of a subsequent UL slot during 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. / i.e., UL transmission may take priority over DL Rx. In this case, the guard period may be included in the DL time interval, and the UE may drop DL rx during the guard period.

[0323] The above method 3 can be applied only when A and B are all configured via higher layer signaling or all A and B are dynamically scheduled by DCI in A-to-B switching. If the methods of configuring or scheduling A and B are different (e.g., A is configured via higher layer signaling and B is dynamically scheduled by DCI), it can operate according to the above method 1 / method 2 of Proposal 2.

[0324] <Method 4>

[0325] When DL-to-UL switching occurs, the position of the guard time / guard period can be fixed at the end (symbol, guard time) of the DL slot (LTE approach) or at the beginning (symbol, guard time) of the UL slot (NR approach). Alternatively, the base station can choose between the two methods. The position information of the guard time / guard period can be transmitted in the system information or indicated via UE-specific RRC signaling.

[0326] The base station configuration as in the above-mentioned Method 4 can be applied only when, in A-to-B switching, A and B are all configured via higher layer signaling or all A and B are dynamically scheduled by DCI. If the methods of configuring or scheduling A and B are different (e.g., A is configured via higher layer signaling and B is dynamically scheduled by DCI), it can operate according to Method 1 / Method 2 of Proposal 2 above.

[0327] Based on the above-mentioned methods and / or embodiments of Proposal 1 / Proposal 2, a method for setting a guard period for supporting half-duplex FDD operation has been described. In order to efficiently use resources during half-duplex FDD operation, data or control information can be transmitted by performing rate matching around the guard period. Puncturing can be considered instead of rate matching, but when assuming the same amount of transmission information and guard period, rate matching has the advantage of being able to receive transmission data at a lower SNR compared to puncturing.

[0328] Rate matching around the guard period can be applied only when the UE and the base station have the same understanding of the guard period. For example, only when the guard period is predefined to a specific value or set through higher layer configuration, the UE can assume rate matching and perform PDSCH reception or PUSCH transmission. In this way, if there is no misunderstanding about the guard period between the base station and the UE, the base station may not transmit separate rate matching information through DCI. In this case, the UE can receive a rate-matched PDSCH or transmit a PUSCH using time domain resource allocation (TDRA) information received through DCI and previously acquired guard period information.

[0329] Alternatively, the base station may configure a higher layer as to whether or not to apply rate matching to a slot in which a guard period exists. A common or dedicated RRC parameter may be defined for the above purpose. Furthermore, a higher layer may configure whether or not to apply rate matching to a slot in which a guard period exists. A common or dedicated RRC parameter may be defined for the above purpose. Furthermore, a rate matching indication flag may be added to the DCI in order to dynamically select whether or not to apply rate matching to a slot in which a guard period exists. For example, if the value of the corresponding flag is 1, the terminal may perform DL Rx operation assuming rate matching in a slot in which a guard period exists, and if the value is 0, the terminal may perform DL Rx operation assuming puncturing (the reverse operation is also possible).

[0330] FIG. 7 illustrates an example of a signaling flowchart between a terminal (User Equipment, UE) and a base station to which the method proposed in this specification (e.g. Proposal 1 / Proposal 2, etc.) can be applied. In FIG. 7, it is assumed that the terminal operates in a half-duplex FDD mode. Also, the terminal in FIG. 7 may correspond to the above-mentioned "redcap UE". FIG. 7 is merely for convenience of explanation and does not limit the scope of the present invention. Also, some steps illustrated in FIG. 7 may be omitted depending on the situation and / or settings, etc.

[0331] The terminal can transmit UE capability information to the base station. That is, the base station can receive UE capability information from the terminal (S710). The UE capability information can include at least one of switching time capability information or protection period capability information described in Proposal 1 / Proposal 2. The base station can schedule the terminal based on the UE capability information.

[0332] The terminal may receive configuration information from the base station, i.e., the base station may transmit configuration information to the terminal (S720). The configuration information may include at least one of information on a switching time or information on a protection period determined based on UE capability information reported by the terminal.

[0333] For example, as described in Method 2 of Proposal 1 above, the information on the protection period may include the number of symbols or the number of slots constituting the protection period. The information on the protection period may be set for each SCS or for each frequency range.

[0334] Data can be transmitted and received between the terminal and the base station based on the above-mentioned setting information (S730). Since it operates according to half-duplex FDD, DL and UL are not executed simultaneously in the same time period. Also, data can be transmitted and received while avoiding collision between DL and UL based on the method of Proposal 2 described above.

[0335] FIG. 8 shows an example of an operation flowchart of a terminal (User equipment, UE) to which the method proposed in this specification (e.g. Proposal 1 / Proposal 2, etc.) can be applied, transmitting and receiving data. In FIG. 8, it is assumed that the terminal operates in a half-duplex FDD mode. Note that the terminal in FIG. 8 may correspond to the above-mentioned "redcap UE". FIG. 8 is merely for convenience of explanation and does not limit the scope of the present invention. Also, some steps shown in FIG. 8 may be omitted depending on the situation and / or settings, etc.

[0336] The terminal may receive configuration information (S810). That is, the base station may transmit the configuration information to the terminal. The configuration information may be received via higher layer signaling (e.g., RRC, MAC-CE, etc.). The configuration information may include information on a protection period for preventing collision / overlap that may occur during DL-to-UL switching or UL-to-DL switching in half-duplex FDD operation. A protection period for DL-to-UL switching or UL-to-DL switching may be set based on the information on the protection period. The protection period may be i) set for each SCS or ii) set for each frequency range.

[0337] As a specific example, a protection period corresponding to each SCS can be set / indicated, or a second value that is a protection period corresponding to another SCS can be determined based on a first value that is a protection period corresponding to a reference SCS, and the ratio of the reference SCS to the other SCS can be the same as the ratio of the first value to the second value.

[0338] For example, the operation of the terminal (100 / 200 in Figs. 9 to 13) receiving the setting information in step S810 described above can be realized by the devices in Figs. 9 to 13 described below. For example, referring to Fig. 10, one or more processors 102 can control one or more transceivers 106 and / or one or more memories 104, etc. to receive the setting information, and one or more transceivers 106 can receive the setting information.

[0339] The terminal may receive downlink control information (DCI) (S820). That is, the base station may transmit DCI to the terminal. The DCI may be received via a control channel (e.g., PDCCH). For example, the DCI may include scheduling information of a data channel (e.g., PDSCH, PUSCH). Also, if the DCI is DCI format 2_0, a slot format may be indicated based on the DCI.

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

[0341] For example, the operation of the terminal (100 / 200 in Figs. 9 to 13) receiving downlink control information in step S820 described above can be realized by the devices in Figs. 9 to 13 described below. For example, referring to Fig. 10, one or more processors 102 can control one or more transceivers 106 and / or one or more memories 104, etc. to receive DCI, and one or more transceivers 106 can receive the DCI.

[0342] Based on the first direction being opposite to the second direction, the terminal may perform switching from the first time interval to the second time interval (S830). For example, based on the first direction being downlink and the second direction being uplink, the terminal may perform switching in the first time interval for receiving a downlink to the second time interval for uplink transmission. As yet another example, based on the first direction being uplink and the second direction being downlink, the terminal may perform switching in the first time interval for transmitting an uplink to the second time interval for downlink reception.

[0343] A guard period required for the switching may be included in a time period in which low priority data is transmitted among the first time period or the second time period. This may mean that a time period in which low priority data is transmitted among the first time period or the second time period is overlapped with a part or the whole of a guard period. The guard period may include a switching time from the first time period to the second time period.

[0344] The priority of the first data and the second data may be determined based on a predefined rule.

[0345] For example, the predefined rule may be related to a type of information for scheduling the second data. As a specific example, the second data may be determined to have a higher priority than the first data based on the second data being scheduled by the DCI. In this case, the protection period may be included in the first time period.

[0346] 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 protection period may be included in the first time interval based on the second data being a PRACH preamble. In this case, the terminal may not receive the first data during the protection period included in the first time interval. As yet another example, the protection period may be located after the last symbol in which an SSB is received in the first time interval based on the first data being an SSB and the second data being a PRACH preamble.

[0347] For example, the protection period may be included in the second time interval based on the fact that the first data is an SSB, in which case the terminal may not transmit the second data before the protection period included in the second time interval after the end of SSB reception.

[0348] For example, the operation of the terminal (100 / 200 in Figs. 9 to 13) performing switching in step S830 described above may be realized by the devices in Figs. 9 to 13 described below. For example, referring to Fig. 10, one or more processors 102 may control one or more transceivers 106 and / or one or more memories 104, etc. to perform the switching.

[0349] After switching, the terminal may transmit data or receive data according to a second direction in a second time interval.

[0350] Although not shown in Fig. 8, the terminal can transmit capability information. That is, the base station can receive capability information from the terminal. The capability information can include at least one of capability information related to switching time or capability information related to protection period described in Proposal 1 / Proposal 2. The base station can schedule the terminal based on the capability information.

[0351] As mentioned above, the above base station / UE signaling and operations (e.g., proposals 1 / 2 / FIG. 7 / FIG. 8, etc.) can be realized by the devices described below (e.g., FIG. 9 to FIG. 13). For example, the base station can be the first radio device and the UE can be the second radio device, and vice versa in some cases.

[0352] For example, the above-mentioned base station / UE signaling and operations (eg. Proposal 1 / 2 / FIG. 7 / FIG. 8, etc.) may be processed by one or more processors (eg. 102, 202) of FIG. 9 to FIG. 13, and the above-mentioned base station / UE signaling and operations (eg. Proposal 1 / 2 / FIG. 7 / FIG. 8, etc.) may also be stored in one or more memories (eg. 104, 204) in the form of instructions / programs (eg. instruction, executable code) for driving at least one processor (eg. 102, 202) of FIG. 9 to FIG. 13.

[0353] An example of a communication system to which the present invention is applied

[0354] Although the configurations disclosed herein are not limited thereto, the various descriptions, functions, procedures, suggestions, methods and / or operational flow diagrams of the present invention disclosed herein may be applicable to various fields requiring wireless communication / connection (e.g., 5G) between devices.

[0355] Hereinafter, the present invention will be described in more detail with reference to the drawings. In the following drawings and description, the same reference numerals denote the same or corresponding hardware blocks, software blocks, or function blocks unless otherwise stated.

[0356] FIG. 9 illustrates an example of a communication system to which the present invention can be applied (1).

[0357] As shown in FIG. 9, the communication system applied to the present invention includes wireless devices, base stations, and networks. Here, the wireless devices refer to devices that communicate using wireless connection technologies (e.g., 5G NR (New RAT), LTE (Long Term Evolution)), and may be referred to as communication / wireless / 5G devices. Although not limited thereto, the wireless devices may include a robot 100a, vehicles 100b-1, 100b-2, an XR (eXtended Reality) device 100c, a handheld device (Hand-held device) 100d, a home appliance 100e, an IoT (Internet of Things) device 100f, and an AI device / server 400. For example, the vehicles may include vehicles equipped with wireless communication functions, autonomous vehicles, vehicles capable of inter-vehicle communication, and the like. Here, the vehicles may include an UAV (Unmanned Aerial Vehicle) (e.g., a drone). The XR devices include Augmented Reality (AR) / Virtual Reality (VR) / Mixed Reality (MR) devices, and may be realized 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, digital signage, a vehicle, a robot, etc. The portable devices include a smartphone, a smart pad, a wearable device (e.g., a smart watch, a smart glass), a computer (e.g., a laptop, etc.), etc. The home appliances include a TV, a refrigerator, a washing machine, etc. The IoT devices may include a sensor, a smart meter, etc. For example, a base station and a network may be realized as a wireless device, and a specific wireless device 100a may operate as a base station / network node for other wireless devices.

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

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

[0360] Examples of wireless devices to which the present invention can be applied

[0361] FIG. 10 illustrates a wireless device to which the present invention can be applied.

[0362] 10, the first wireless device 100 and the second wireless device 200 can transmit and receive wireless signals via various wireless access technologies (e.g., LTE, NR), where {the first wireless device 100, the second wireless device 200} can correspond to {wireless device 100x, base station 200} and / or {wireless device 100x, wireless device 100x} in FIG.

[0363] The first wireless device 100 includes 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 102 is configured to control the memory 104 and / or the transceiver 106 to implement the descriptions, functions, procedures, suggestions, methods, and / or operational flow diagrams disclosed herein. For example, the processor 102 may process information in the memory 104 to generate a first information / signal, and then transmit a wireless signal including the first information / signal via the transceiver 106. The processor 102 may also receive a wireless signal including a second information / signal via the transceiver 106, and then store information obtained from signal processing of the second information / signal in the memory 104. The memory 104 may be connected to the processor 102 and may store various information related to the operation of the processor 102. For example, the memory 104 may store software code including instructions for performing some or all of the processes controlled by the processor 102 or performing the descriptions, functions, procedures, suggestions, methods and / or operational flow diagrams disclosed herein. Here, the processor 102 and the memory 104 may be part of a communication modem / circuit / chip designed to realize a wireless communication technology (e.g., LTE, NR). The transceiver 106 may be connected to the processor 102 and may transmit and / or receive wireless signals via one or more antennas 108. The transceiver 106 may include a transmitter and / or a receiver. The transceiver 106 may be mixed with an RF (Radio Frequency) unit. In the present invention, a wireless device may also mean a communication modem / circuit / chip.

[0364] The second wireless device 200 includes one or more processors 202, one or more memories 204, and may further include one or more transceivers 206 and / or one or more antennas 208. The processor 202 may be configured to control the memory 204 and / or the transceiver 206 to implement the descriptions, functions, procedures, suggestions, methods, and / or operational flow diagrams disclosed herein. For example, the processor 202 may process information in the memory 204 to generate a third information / signal, and then transmit a wireless signal including the third information / signal via the transceiver 206. The processor 202 may also receive a wireless signal including a fourth information / signal via the transceiver 206, and then store information obtained from signal processing of the fourth information / signal in the memory 204. The memory 204 may be connected to the processor 202 and may store various information related to the operation of the processor 202. For example, the memory 204 may store software code including instructions for performing some or all of the processes controlled by the processor 202 or performing the descriptions, functions, procedures, suggestions, methods and / or operational flow diagrams disclosed in this document. Here, the processor 202 and the memory 204 may be part of a communication modem / circuit / chip designed to realize a wireless communication technology (e.g., LTE, NR). The transceiver 206 may be connected to the processor 202 and may transmit and / or receive wireless signals via one or more antennas 208. The transceiver 206 may include a transmitter and / or a receiver. The transceiver 206 may be mixed with an RF unit. In the present invention, a wireless device may also mean a communication modem / circuit / chip.

[0365] The hardware elements of the wireless device 100, 200 are described in more detail below. Without being limited thereto, one or more protocol layers may be implemented by one or more processors 102, 202. For example, one or more processors 102, 202 may implement one or more layers (e.g., functional layers such as PHY, MAC, RLC, PDCP, RRC, SDAP, etc.). One or more processors 102, 202 may generate one or more Protocol Data Units (PDUs) and / or one or more Service Data Units (SDUs) according to the descriptions, functions, procedures, suggestions, methods, and / or operational flow diagrams disclosed herein. One or more processors 102, 202 may generate messages, control information, data, or information according to the descriptions, functions, procedures, suggestions, methods, and / or operational flow diagrams disclosed herein. The one or more processors 102, 202 may generate and provide signals (e.g., baseband signals) including PDUs, SDUs, messages, control information, data or information according to the functions, procedures, suggestions, and / or methods disclosed herein to the one or more transceivers 106, 206. The one or more processors 102, 202 may receive signals (e.g., baseband signals) from the one or more transceivers 106, 206 and obtain the PDUs, SDUs, messages, control information, data or information according to the descriptions, functions, procedures, suggestions, methods and / or operational flow diagrams disclosed herein.

[0366] The one or more processors 102, 202 may be referred to as a controller, a microcontroller, a microprocessor, or a microcomputer. The one or more processors 102, 202 may be implemented in hardware, firmware, software, or a combination thereof. As an 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 the one or more processors 102, 202. The descriptions, functions, procedures, suggestions, methods, and / or operational flow diagrams disclosed herein may be implemented using firmware or software, and the firmware or software may be implemented to include modules, procedures, functions, etc. Firmware or software configured to perform the descriptions, functions, procedures, suggestions, methods and / or operational flowcharts disclosed herein may be included in one or more processors 102, 202 or stored in one or more memories 104, 204 and executed by one or more processors 102, 202. The descriptions, functions, procedures, suggestions, methods and / or operational flowcharts disclosed herein may be implemented using firmware or software in the form of code, instructions and / or collections of instructions.

[0367] One or more memories 104, 204 may be connected to one or more processors 102, 202 and may store various types of data, signals, messages, information, programs, code, instructions, and / or commands. The one or more memories 104, 204 may be comprised of ROM, RAM, EPROM, flash memory, hard drives, registers, cache memory, computer readable storage media, and / or combinations thereof. The one or more memories 104, 204 may be located internal and / or external to the one or more processors 102, 202. The one or more memories 104, 204 may be connected to the one or more processors 102, 202 by various techniques, such as wired or wireless connections.

[0368] One or more transceivers 106, 206 may transmit user data, control information, wireless signals / channels, etc., as described in the methods and / or operational flow diagrams, etc., of this document to one or more other devices. One or more transceivers 106, 206 may receive user data, control information, wireless signals / channels, etc., as described in the descriptions, functions, procedures, suggestions, methods and / or operational flow diagrams, etc., of this document from one or more other devices. For example, one or more transceivers 106, 206 may be coupled to one or more processors 102, 202 and may transmit and receive wireless signals. For example, one or more processors 102, 202 may control one or more transceivers 106, 206 to transmit user data, control information, or wireless signals to one or more other devices. Also, one or more processors 102, 202 may control one or more transceivers 106, 206 to receive user data, control information, or wireless signals from one or more other devices. In addition, one or more transceivers 106, 206 may be connected to one or more antennas 108, 208, and the one or more transceivers 106, 206 may be configured to transmit and receive user data, control information, radio signals / channels, etc., as referred to in the descriptions, functions, procedures, suggestions, methods, and / or operation flow diagrams disclosed herein, via one or more antennas 108, 208. In this document, one or more antennas may be multiple physical antennas (e.g., antenna ports). The one or more transceivers 106, 206 may convert received radio signals / channels, etc., from RF band signals to baseband signals for processing the received user data, control information, radio signals / channels, etc., using one or more processors 102, 202. The one or more transceivers 106, 206 may convert user data, control information, radio signals / channels, etc., processed using one or more processors 102, 202, from baseband signals to RF band signals. To this end, one or more of the transceivers 206, 206 may include (analog) oscillators and / or filters.

[0369] Example of a signal processing circuit to which the present invention is applied

[0370] FIG. 11 shows a signal processing circuit for a transmission signal.

[0371] Referring to FIG. 11, the signal processing circuit 1000 may include a scrambler 1010, a modulator 1020, a layer mapper 1030, a free coder 1040, a resource mapper 1050, and a signal generator 1060. Although not limited thereto, the operations / functions of FIG. 11 may be performed by the processor 102, 202 and / or the transceiver 106, 206 of FIG. 10. The hardware elements of FIG. 11 may be implemented by the processor 102, 202 and / or the transceiver 106, 206 of FIG. 10. For example, the blocks 1010 to 1060 may be implemented by the processor 102, 202 of FIG. 10. Also, the blocks 1010 to 1050 may be implemented by the processor 102, 202 of FIG. 10, and the block 1060 may be implemented by the transceiver 106, 206 of FIG. 10.

[0372] The codeword can be converted into a wireless signal through the signal processing circuit 1000 of FIG. 11. Here, the codeword is a coded bit sequence of an information block. The information block can include a transmission block (e.g., a UL-SCH transmission block, a DL-SCH transmission block). The wireless signal can be transmitted through various physical channels (e.g., a PUSCH, a PDSCH).

[0373] Specifically, the codeword may be converted into a scrambled bit sequence by the scrambler 1010. The scrambling sequence used for scrambling may be generated based on an initialization value, and the initialization value may include ID information of the wireless device, etc. The scrambled bit sequence may be modulated into a sequence of modulation symbols by the modulator 1020. The modulation scheme may include pi / 2-BPSK (pi / 2-Binary Phase Shift Keying), m-PSK (m-Phase Shift Keying), m-QAM (m-Quadrature Amplitude Modulation), etc. The sequence of complex modulation symbols may be mapped to one or more transmission layers by the layer mapper 1030. The modulation symbols of each transmission layer may be mapped to the antenna port by the free coder 1040 (free coding). The output z of the free coder 1040 may be obtained by multiplying the output y of the layer mapper 1030 by a precoding matrix W of N*M, where N is the number of antenna ports and M is the number of transmission layers. Here, the free coder 1040 may perform free coding after performing transform free coding (e.g., DFT transform) on the complex modulation symbols, or may perform free coding without performing transform precoding.

[0374] The resource mapper 1050 can map the modulation symbols of each antenna port to a time-frequency resource. The time-frequency resource can include a plurality of symbols (e.g., CP-OFDMA symbols, DFT-s-OFDMA symbols) in the time domain and a plurality of subcarriers in the frequency domain. The signal generator 1060 generates a radio signal from the mapped modulation symbols, and the generated radio signal can be transmitted to other devices via each antenna. To this end, the signal generator 1060 can include an Inverse Fast Fourier Transform (IFFT) module, a Cyclic Prefix (CP) inserter, a Digital-to-Analog Converter (DAC), a frequency uplink converter, and the like.

[0375] The signal processing process for a received signal in a wireless device may be configured in reverse to the signal processing process (1010 to 1060) of FIG. 18. For example, a wireless device (e.g., 100, 200 of FIG. 17) may receive a wireless signal from the outside through an antenna port / transceiver. The received wireless signal may be converted to a baseband signal by a signal restorer. For this purpose, 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. Thereafter, the baseband signal may be restored to a codeword through a resource de-mapper process, a postcoding process, a demodulation process, and a descrambling process. The codeword may be restored to the original information block through decoding. Therefore, a signal processing circuit (not shown) for a received signal may include a signal restorer, a resource de-mapper, a postcoder, a demodulator, a descrambler, and a decoder.

[0376] Examples of wireless device applications to which this invention can be applied

[0377] Figure 12 shows another example of a wireless device to which the present specification applies. The wireless device can be realized in various forms depending on the use-case / service (see Figure 19).

[0378] 12, the wireless devices 100, 200 correspond to the wireless devices 100, 200 of FIG. 10 and may be composed of various elements, components, units, and / or modules. For example, the wireless devices 100, 200 may include a communication unit 110, a control unit 120, a memory unit 130, and an additional element 140. The communication unit may include a communication circuit 112 and a transceiver 114. For example, the communication circuit 112 may include one or more processors 102, 202 and / or one or more memories 104, 204 of FIG. 10. For example, the transceiver 114 may include one or more transceivers 106, 206 and / or one or more antennas 108, 208 of FIG. 10. The control unit 120 is electrically connected to the communication unit 110, the memory unit 130, and the additional element 140, and controls the operations of the wireless device. For example, the control unit 120 can control electrical / mechanical operations of the wireless device based on the programs / codes / commands / information stored in the memory unit 130. In addition, the control unit 120 can transmit information stored in the memory unit 130 to an outside (e.g., another communication device) via the communication unit 110 through a wireless / wired interface, and can store information received from an outside (e.g., another communication device) via the communication unit 110 through a wireless / wired interface in the memory unit 130.

[0379] The additional element 140 may be configured in various ways depending on the type of wireless device. For example, the additional element 140 may include at least one of a power unit / battery, an input / output unit (I / O unit), a driving unit, and a computing unit. Without being limited thereto, the wireless device may be realized in the form of a robot (FIG. 9, 100a), a vehicle (FIG. 9, 100b-1, 100b-2), an XR device (FIG. 9, 100c), a mobile device (FIG. 9, 100d), a home appliance (FIG. 9, 100e), an IoT device (FIG. 9, 100f), a digital broadcasting terminal, a hologram device, a public safety device, an MTC device, a medical device, a Fintech device (or a financial device), a security device, a climate / environment device, an AI server / device (FIG. 9, 400), a base station (FIG. 9, 200), a network, a node, etc. The wireless device may be mobile or fixed depending on the use case / service.

[0380] In FIG. 12, various elements, components, units / parts, and / or modules in the wireless devices 100 and 200 may be entirely connected to each other via a wired interface, or at least some of them may be connected wirelessly via the communication unit 110. For example, in the wireless devices 100 and 200, the control unit 120 and the communication unit 110 may be connected by wire, and the control unit 120 and a first unit (e.g., 130, 140) may be connected wirelessly via the communication unit 110. Also, each element, component, unit / part, and / or module in the wireless devices 100 and 200 may further include one or more elements. For example, the control unit 120 may be configured with a set of one or more processors. For example, the control unit 120 may be configured with a set of a communication control processor, an application processor, an ECU (Electronic Control Unit), a graphics processing processor, a memory control processor, etc. As another example, the memory unit 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.

[0381] Examples of portable devices to which the present invention can be applied

[0382] Figure 13 illustrates a mobile device applied in this specification. The mobile device may include a smartphone, a smart pad, a wearable device (e.g., a smart watch, a smart glass), a handheld computer (e.g., a notebook, etc.). The mobile 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).

[0383] 13, the portable device 100 includes an antenna unit 108, a communication unit 110, a control unit 120, and a memory unit 130, which may include a power supply unit 140a, an interface unit 140b, and an input / output 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 blocks 110 to 130 / 140 in FIG. 12, respectively.

[0384] The communication unit 110 can transmit and receive signals (e.g., data, control signals, etc.) to and from other wireless devices and base stations. The control unit 120 can control components of the portable device 100 to perform various operations. The control unit 120 can include an AP (Application Processor). The memory unit 130 can store data / parameters / programs / codes / commands required for driving the portable device 100. The memory unit 130 can also store input / output data / information, etc. The power supply unit 140a supplies power to the portable device 100 and can include a wired / wireless charging circuit, a battery, etc. The interface unit 140b can support connection between the portable device 100 and other external devices. The interface unit 140b can include various ports (e.g., audio input / output ports, video input / output ports) for connection with external devices. The input / output unit 140c can receive and output video information / signals, audio information / signals, data, and / or information input by a user. The input / output unit 140c may include a camera, a microphone, a user input unit, a display unit 140d, a speaker, and / or a haptic module, etc.

[0385] As an example, in the case of data communication, the input / output unit 140c may acquire information / signals (e.g., touch, text, voice, image, video) input by a user, and the acquired information / signals may be stored in the memory unit 130. The communication unit 110 may convert the information / signals stored in the memory into wireless signals, and may transmit the converted wireless signals directly to another wireless device or to a base station. In addition, the communication unit 110 may receive a wireless signal from another wireless device or a base station, and then restore the received wireless signal to the original information / signal. The restored information / signals may be stored in the memory unit 130, and then output in various forms (e.g., text, voice, image, video, haptic) via the input / output unit 140c.

[0386] Here, the wireless communication technology realized by the wireless device (e.g., 100, 200) of the present specification may include not only LTE, NR, and 6G, but also Narrowband Internet of Things for low power communication. At this time, for example, the NB-IoT technology may be an example of a Low Power Wide Area Network (LPWAN) technology, and may be realized by standards such as LTE Cat NB1 and / or LTE Cat NB2, and is not limited to the above names. Additionally or alternatively, the wireless communication technology realized by the wireless device (e.g., 100, 200) of the present specification may perform communication based on the LTE-M technology. At this time, as an example, the LTE-M technology may be an example of an LPWAN technology, and may be called various names such as eMTC (enhanced Machine Type Communication). For example, the LTE-M technology may be realized by at least 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 is not limited to the above names. Additionally or alternatively, the wireless communication technology realized by the wireless device (100, 200) of the present specification may include at least one of ZigBee, Bluetooth (registered trademark), and Low Power Wide Area Network (LPWAN), which consider low power communication, and is not limited to the above names. As an example, the ZigBee technology can create personal area networks (PANs) related to small / low-power digital communication based on various standards such as IEEE 802.15.4, and may be called by various names.

[0387] The embodiments described above are combinations of the components and features of the present invention in a predetermined form. Each component or feature should be considered as optional unless otherwise expressly stated. Each component or feature may be implemented in a form not combined with other components or features. It is also possible to combine some components and / or features to constitute an embodiment of the present invention. The order of operations described in the embodiments of the present invention may be changed. Some configurations or features of an embodiment may be included in other embodiments, or may be replaced with corresponding configurations or features of other embodiments. It is obvious that claims that do not have an explicit reference relationship in the claims may be combined to constitute an embodiment, or may be included in a new claim by amendment after filing.

[0388] Embodiments in accordance with the present invention may be implemented in a variety of ways, such as hardware, firmware, software, or a combination thereof. In a hardware implementation, an embodiment of the present invention may be implemented using 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.

[0389] In the case of a firmware or software implementation, an embodiment of the present invention may be implemented in the form of a module, procedure, function, etc. that performs the functions or operations described above. The software code may be stored in a memory and executed by a processor. The memory may be located inside or outside the processor and may exchange data with the processor by various means known in the art.

[0390] It is obvious to those skilled in the art that the present invention can be embodied in other specific forms without departing from the essential features of the present invention. Therefore, the above detailed description should not be interpreted as limiting in all respects, but should be considered as illustrative. The scope of the present invention should be determined by a reasonable interpretation of the appended claims, and all modifications within the equivalent scope of the present invention are included in the scope of the present invention.

[0391] The method for transmitting and receiving data in a wireless communication system supporting half-duplex FDD of the present invention has been described mainly as an example applied to a 3GPP LTE / LTE-A system and a 5G system (New RAT system), but can also be applied to various other wireless communication systems.

Claims

1. A method for a terminal (User Equipment: UE) receiving a synchronization signal block (SSB) in a wireless communication system supporting half-duplex frequency division duplexing (FDD), comprising: receiving configuration information from a base station (BS) via higher layer signaling; and receiving the SSB from the base station (BS) based on the configuration information; The SSB is received by the terminal (UE) before and after a guard period associated with an uplink transmission; The guard period is i) the first symbol before a slot of said uplink transmission; and ii) a second symbol following the slot of the uplink transmission; the first symbol is based on a first radio frequency (RF) readjustment time from downlink reception to uplink transmission; The method of claim 1, wherein the second symbol is based on a second RF retuning time from the uplink transmission to a downlink reception.

2. 2. The method of 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. 2. The method of claim 1, wherein the SSB comprises a Primary Synchronization Signal (PSS), a Secondary Synchronization Signal (SSS), and a Physical Boardcast Channel (PBCH).

4. 2. The method of claim 1, wherein the terminal is a half-duplex terminal.

5. 5. The method according to claim 4, characterized in that the half-duplex terminal is a terminal which has no possibility to transmit and receive simultaneously.

6. A terminal (User Equipment: UE) configured to receive a synchronization signal block (SSB) in a wireless communication system supporting half-duplex frequency division duplexing (FDD), comprising: one or more transceivers; one or more processors; and one or more memories operatively connected to the one or more processors that store instructions for operations to be performed by the one or more processors; The operation includes: receiving configuration information from a base station (BS) via higher layer signaling; and receiving the SSB from the base station (BS) based on the configuration information; The SSB is received by the terminal (UE) before and after a guard period associated with an uplink transmission; The guard period is i) the first symbol before a slot of said uplink transmission; and ii) a second symbol following the slot of the uplink transmission; the first symbol is based on a first radio frequency (RF) readjustment time from downlink reception to uplink transmission; The terminal, wherein the second symbol is based on a second RF retuning time from the uplink transmission to the downlink reception.

7. 7. The terminal of 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 terminal according to claim 6, wherein the SSB comprises a Primary Synchronization Signal (PSS), a Secondary Synchronization Signal (SSS), and a Physical Boardcast Channel (PBCH).

9. The terminal according to claim 6, characterized in that the terminal is a half-duplex terminal.

10. 10. The terminal according to claim 9, wherein the half-duplex terminal is a terminal that does not have the possibility to transmit and receive simultaneously.

11. In a wireless communication system supporting half-duplex frequency division duplexing (FDD), a base station (BS) configured to transmit a synchronization signal block (SSB), comprising: one or more transceivers; one or more processors; and one or more memories operatively connected to the one or more processors that store instructions for operations to be performed by the one or more processors; The operation includes: Sending configuration information to a terminal (User Equipment: UE) via higher layer signaling; and transmitting the SSB to the terminal (UE) based on the configuration information; The SSB is received by the terminal (UE) before and after a guard period associated with an uplink transmission; The guard period is i) the first symbol before a slot of said uplink transmission; and ii) a second symbol following the slot of the uplink transmission; the first symbol is based on a first radio frequency (RF) readjustment time from downlink reception to uplink transmission; The base station, wherein the second symbol is based on a second RF retuning time from the uplink transmission to the downlink reception.

12. 12. The base station according to claim 11, wherein the uplink transmission is at least one transmission 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 comprises a Primary Synchronization Signal (PSS), a Secondary Synchronization Signal (SSS), and a Physical Boardcast Channel (PBCH).

14. The base station according to claim 11, wherein the terminal is a half-duplex terminal.

15. The base station according to claim 14, wherein the half-duplex terminal is a terminal that has no possibility of transmitting and receiving simultaneously.

Images