Method for data transmission / reception in wireless communication system, and device using method

Abstract

An operation method of a device in a wireless communication system, and a device using the method are provided. According to the method, a terminal receives, from a base station, group information about a terminal group related to multi-terminal scheduling, monitors PDCCH candidates for a specific DCI format on the basis of the group information, and transmits or receives data on the basis of the specific DCI format. Here, the multi-terminal scheduling is a scheduling method performing scheduling for a plurality of terminals through the same DCI format, and the terminal monitors the PDCCH candidates in order to detect the specific DCI format in a search space determined on the basis of the group information.

Description

Method for transmitting and receiving data in a wireless communication system and a device using the method

[0001] The present disclosure relates to a method for transmitting and receiving data by a device in a wireless communication system and a device using the method.

[0002] As more and more communication devices demand greater communication capacity, the need for improved mobile broadband communications over existing radio access technology (RAT) is emerging. Furthermore, massive Machine Type Communications (MTC), which connects numerous devices and objects to provide diverse services anytime, anywhere, is also a key issue to be considered in next-generation communications. Furthermore, communication system design that considers reliability and latency-sensitive services / terminals is being discussed. The introduction of next-generation radio access technologies that take into account enhanced mobile broadband communications, massive MTC, and URLLC (Ultra-Reliable and Low Latency Communication) is being discussed, and for convenience, these technologies are referred to as new RAT or NR in this disclosure.

[0003] In conventional wireless communication systems, scheduling of data transmitted to a single terminal is performed through a single downlink control information (DCI). However, for devices with relatively low mobility and similar traffic characteristics (e.g., Internet of Things (IoT) devices), the amount of control information required to schedule the transmitted traffic may be relatively large compared to the amount of traffic. Furthermore, when the channel environment or traffic for transmitting and receiving traffic remains unchanged for a relatively long period of time, or when traffic transmission and reception patterns between devices are similar, the existing scheduling method using DCI may be inefficient.

[0004] Meanwhile, for devices located within the same vehicle, the channel environment between devices can be maintained similarly. In such an environment, scheduling data independently for each terminal would incur unnecessary scheduling overhead, as similar scheduling information would need to be transmitted independently for each piece of data.

[0005] The technical problem to be solved by the present disclosure is to provide a method for transmitting and receiving data by a device in a wireless communication system and a device using the method.

[0006] A method for transmitting and receiving data by a terminal in a wireless communication system is provided. According to the method, the terminal receives group information about a terminal group related to multi-UE scheduling from a base station, monitors PDCCH (physical downlink control channel) candidates for a specific DCI (downlink control information) format based on the group information, and transmits or receives data based on the specific DCI format. In this case, the multi-terminal scheduling is a scheduling method for performing scheduling for a plurality of terminals through the same DCI format, and the terminal monitors the PDCCH candidates to detect the specific DCI format in a search space determined based on the group information.

[0007] In another aspect, a terminal, chipset and computer-readable medium for executing the above method are provided.

[0008] According to the method according to the present disclosure, a single DCI can be transmitted instead of multiple DCIs to schedule multiple data. Accordingly, the number of DCIs transmitted in the search space can be reduced.

[0009] Additionally, when scheduling multiple data, the amount of information transmitted through DCI can be reduced by sharing some DCI fields.

[0010] Since the number of DCIs required to schedule multiple data sets is reduced, the number of PDCCH (physical downlink control channel) candidates that the terminal must monitor can also be reduced. This also reduces the terminal's PDCCH blind decoding overhead.

[0011] Figure 1 illustrates the system architecture of a New Generation Radio Access Network (NG-RAN) to which NR is applied.

[0012] Figure 2 is a block diagram showing a radio protocol architecture for a user plane.

[0013] Figure 3 is a block diagram showing the wireless protocol structure for the control plane.

[0014] Figure 4 illustrates the functional division between NG-RAN and 5GC.

[0015] Figure 5 illustrates a frame structure that can be applied in NR.

[0016] Figure 6 shows an example of a resource grid in NR.

[0017] Figure 7 shows an example of a physical resource block in NR.

[0018] Figure 8 illustrates the slot structure of an NR frame.

[0019] Figure 9 illustrates a core set.

[0020] Figure 10 illustrates an example of a slot structure for a new wireless access technology.

[0021] Figure 11 illustrates the structure of a self-contained slot.

[0022] Figure 12 illustrates physical channels and typical signal transmission.

[0023] Figure 13 illustrates an example of a flexible network topology to which embodiments of the present specification may be applied.

[0024] Figure 14 shows an example of a DCI format for multi-terminal scheduling.

[0025] Figure 15 illustrates the operation method of the terminal.

[0026] Figure 16 illustrates the signaling process and operation between a base station and a terminal.

[0027] Figure 17 illustrates a wireless device applicable to the present specification.

[0028] Figure 18 illustrates another example of a wireless device.

[0029] Figure 19 illustrates an example of a signal processing module structure.

[0030] Figure 20 illustrates another example of the structure of a signal processing module within a transmission device.

[0031] FIG. 21 illustrates an example of a wireless communication device according to an implementation example of the present disclosure.

[0032] Fig. 22 illustrates a communication system (1) applied to this specification.

[0033] As used herein, "A or B" can mean "only A," "only B," or "both A and B." In other words, as used herein, "A or B" can be interpreted as "A and / or B." For example, as used herein, "A, B or C" can mean "only A," "only B," "only C," or "any combination of A, B and C."

[0034] As used herein, a slash ( / ) or a comma can mean "and / or." For example, "A / B" can mean "A and / or B." Accordingly, "A / B" can mean "only A," "only B," or "both A and B." For example, "A, B, C" can mean "A, B, or C."

[0035] In this specification, "at least one of A and B" may mean "only A", "only B" or "both A and B". Additionally, in this specification, the expressions "at least one of A or B" or "at least one of A and / or B" may be interpreted identically to "at least one of A and B".

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

[0037] Additionally, parentheses used herein may mean "for example." Specifically, when "control information (ABC)" is indicated, "ABC" may be described as an example of "control information." For example, "control information" may include DEF as another example. In other words, "control information" in this specification is not limited to "ABC," and "ABC" may be described as an example of "control information." Furthermore, even when indicated as "control information (i.e., ABC)," "ABC" may be described as an example of "control information."

[0038] Additionally, in this specification, terms such as “first,” “second,” etc. are used only for the purpose of distinguishing one component from another, and are not used to limit the components, and do not limit the order or importance between the components unless specifically limited. Accordingly, a first component in one embodiment of this specification may be referred to as a second component in another embodiment, and similarly, a second component in one embodiment may be referred to as a first component in another embodiment.

[0039] In the following explanation, ‘when, if, in case of’ can be replaced with ‘based on’.

[0040] Technical features individually described within a single drawing in this specification may be implemented individually or simultaneously. The following drawings are designed to illustrate specific examples of this specification. The names of specific devices and the names of specific signals, messages, and fields depicted in the drawings are provided for illustrative purposes only, and therefore, the technical features of this specification are not limited to the specific names used in the drawings.

[0041] In this specification, a terminal is a user equipment (UE) or a consumer-side device, and may also be referred to as a base station / second node / IAB node / TRP (Transmission-Reception Point) that receives / transmits signals from / to. A terminal may correspond to a physical node or a logical node. A terminal may correspond to an endpoint on the user side, or may correspond to an intermediate point between other endpoints. In communication between two points that are not limited to endpoints (including one-to-one / many-to-one / one-to-many / many-to-many communication), a terminal may correspond to a served node. A terminal may be a node with a fixed location, or a node with an unfixed location (or mobile).

[0042] In this specification, a base station (BS) is a device on the network side, and may be referred to as a second node / IAB node / x-NodeB (x-NodeB, x may be an abbreviation related to radio access technology (RAT)) / TRP. A BS may correspond to a physical node or a logical node. A BS may correspond to an endpoint on the network side, or may correspond to an intermediate point between other endpoints. In communication between two points that are not limited to endpoints (including one-to-one / many-to-one / one-to-many / many-to-many communication), a BS may correspond to a serving node. A BS may be a node with a fixed location, or a node with an unfixed location.

[0043] In this specification, higher layer parameters may be set for the terminal, preset, or predefined. For example, the base station may transmit higher layer parameters to the terminal. For example, the terminal may transmit parameters such as capabilities to the base station as higher layer parameters. For example, the higher layer parameters may be transmitted via radio resource control (RRC) signaling or medium access control (MAC) signaling.

[0044] In this specification, the information / state / parameter being “configured or pre-configured” can be interpreted as the information / state / parameter being provided / pre-provided to the terminal through pre-defined signaling (e.g., SIB, MAC, RRC) from the base station. In this specification, the information / state / parameter being “defined or pre-defined” can be interpreted as the information / state / parameter being known in advance or pre-stored at the base station and the terminal without signaling between the base station and the terminal.

[0045] The technology described in this specification can be used in various wireless communication systems such as CDMA (code division multiple access), FDMA (frequency division multiple access), TDMA (time division multiple access), OFDMA (orthogonal frequency division multiple access), and SC-FDMA (single carrier frequency division multiple access). CDMA can be implemented with wireless technologies such as UTRA (universal terrestrial radio access) or CDMA2000. TDMA can be implemented with wireless technologies such as GSM (global system for mobile communications) / GPRS (general packet radio service) / EDGE (enhanced data rates for GSM evolution). OFDMA can be implemented with wireless technologies such as IEEE (Institute of Electrical and Electronics Engineers) 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802-20, E-UTRA (evolved UTRA), LTE (long term evolution), and 5G NR.

[0046] The technology described in this specification can be implemented with 6G wireless technology and applied to various 6G systems. For example, the 6G system can have key factors such as enhanced mobile broadband (eMBB), ultra-reliable low latency communications (URLLC), massive machine-type communication (mMTC), artificial intelligence (AI) integrated communication, tactile internet, high throughput, high network capacity, high energy efficiency, low backhaul and access network congestion, and enhanced data security.

[0047] Hereinafter, downlink (DL) refers to communication from a base station to a terminal, and uplink (UL) refers to communication from a terminal to a base station. In downlink, a transmitter may be part of a base station, and a receiver may be part of a terminal. In uplink, a transmitter may be part of a terminal, and a receiver may be part of a base station. A base station may be expressed as a first communication device, and a terminal may be expressed as a second communication device. A base station (BS) may be replaced by terms such as a fixed station, Node B, eNB (evolved-NodeB), gNB (Next Generation NodeB), BTS (base transceiver system), access point (AP: Access Point), network (5G network), AI (Artificial Intelligence) system / module, RSU (road side unit), robot, drone (Unmanned Aerial Vehicle, UAV), AR (Augmented Reality) device, VR (Virtual Reality) device, etc.In addition, the terminal may be fixed or mobile, and may be replaced with terms such as UE (User Equipment), MS (Mobile Station), UT (user terminal), MSS (Mobile Subscriber Station), SS (Subscriber Station), AMS (Advanced Mobile Station), WT (Wireless terminal), MTC (Machine-Type Communication) device, M2M (Machine-to-Machine) device, D2D (Device-to-Device) device, vehicle, RSU (road side unit), robot, AI (Artificial Intelligence) module, drone (Unmanned Aerial Vehicle, UAV), AR (Augmented Reality) device, VR (Virtual Reality) device, etc.

[0048] The following technologies can be used in various wireless access systems, such as CDMA, FDMA, TDMA, OFDMA, and SC-FDMA. 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.

[0049] For clarity, the description is based on the 3GPP communication system (e.g., LTE-A, NR), but the technical idea of ​​the present disclosure is not limited thereto. LTE refers to technology after 3GPP TS 36.xxx Release 8. Specifically, LTE technology after 3GPP TS 36.xxx Release 10 is referred to as LTE-A, and LTE technology after 3GPP TS 36.xxx Release 13 is referred to as LTE-A pro. 3GPP NR refers to technology after TS 38.xxx Release 15. LTE / NR may be referred to as a 3GPP system. “xxx” refers to a standard document detail number. LTE / NR may be collectively referred to as a 3GPP system. For background technology, terms, abbreviations, etc. used in the description of the present disclosure, reference may be made to matters described in standard documents published prior to the present disclosure. For example, reference may be made to the following documents.

[0050] 3GPP LTE

[0051] - 36.211: Physical channels and modulation

[0052] - 36.212: Multiplexing and channel coding

[0053] - 36.213: Physical layer procedures

[0054] - 36.300: Overall description

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

[0056] 3GPP NR

[0057] - 38.211: Physical channels and modulation

[0058] - 38.212: Multiplexing and channel coding

[0059] - 38.213: Physical layer procedures for control

[0060] - 38.214: Physical layer procedures for data

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

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

[0063] As more and more communication devices demand greater communication capacity, the need for improved mobile broadband communication compared to existing radio access technologies is emerging. Furthermore, massive Machine Type Communications (MTC), which connects numerous devices and objects to provide various services anytime, anywhere, is also a key issue to be considered in next-generation communications. Furthermore, communication system design that considers reliability and latency-sensitive services / terminals is being discussed. Accordingly, the introduction of next-generation wireless access technologies such as enhanced mobile broadband communication (eMBB), massive MTC (MMTC), and Ultra-Reliable and Low Latency Communication (URLLC) is being discussed, and for convenience, these technologies are referred to as NR in this specification. NR is an expression representing an example of 5G radio access technology (RAT).

[0064] A new RAT system, including NR, uses OFDM transmission scheme or a similar transmission scheme. The new RAT system may follow OFDM parameters different from those of LTE. Alternatively, the new RAT system may follow the existing LTE / LTE-A numerology but have a larger system bandwidth (e.g., 100 MHz). Alternatively, a single cell may support multiple numerologies. For example, terminals operating under different numerologies may coexist within a single cell.

[0065] A numerology corresponds to a single subcarrier spacing in the frequency domain. Different numerologies can be defined by scaling the reference subcarrier spacing by an integer N.

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

[0067] Some use cases may require optimization across multiple domains, while others may focus on just one Key Performance Indicator (KPI). 5G supports these diverse use cases in a flexible and reliable manner.

[0068] eMBB extends far beyond basic mobile internet access, encompassing rich interactive tasks, cloud computing, and augmented reality media and entertainment applications. Data is a key driver of 5G, and dedicated voice services may not be the first to emerge in the 5G era. In 5G, voice is expected to be handled as an application, simply using the data connection provided by the communication system. The primary drivers of increased traffic volume are the increasing size of content and the growing number of applications requiring high data rates. Streaming services (audio and video), interactive video, and mobile internet connectivity will become more prevalent as more devices connect to the internet. Many of these applications require always-on connectivity to push real-time information and notifications to users. Cloud storage and applications are rapidly growing on mobile communication platforms, applicable to both work and entertainment. Cloud storage is a particular use case driving the growth of uplink data rates. 5G is also used for remote work in the cloud, requiring significantly lower end-to-end latency to maintain a superior user experience when tactile interfaces are used. Entertainment, for example, cloud gaming and video streaming are other key factors driving the demand for mobile broadband. Entertainment is essential on smartphones and tablets, regardless of location, including in highly mobile environments such as trains, cars, and airplanes. Another use case is augmented reality and information retrieval for entertainment, where augmented reality requires extremely low latency and instantaneous data volumes.

[0069] Additionally, one of the most anticipated 5G use cases involves the ability to seamlessly connect embedded sensors across all sectors, such as mMTC. The number of potential IoT devices is projected to reach 20.4 billion by 2020. Industrial IoT is one area where 5G will play a key role, enabling smart cities, asset tracking, smart utilities, agriculture, and security infrastructure.

[0070] URLLC encompasses new services that will transform industries through ultra-reliable, low-latency links, such as remote control of critical infrastructure and self-driving vehicles. Reliability and latency are essential for smart grid control, industrial automation, robotics, and drone control and coordination.

[0071] Let's take a more specific look at several use cases.

[0072] 5G can complement fiber-to-the-home (FTTH) and cable-based broadband (or DOCSIS) by delivering streams rated at hundreds of megabits per second to gigabits per second. These high speeds are required to deliver TV at resolutions beyond 4K (6K, 8K, and beyond), as well as virtual and augmented reality. Virtual reality (VR) and augmented reality (AR) applications include near-immersive sports events. Certain applications may require specialized network configurations. For example, for VR games, game companies may need to integrate their core servers with the network operator's edge network servers to minimize latency.

[0073] Automotive is expected to be a significant new driver for 5G, with numerous use cases for in-vehicle mobile communications. Passenger entertainment, for example, demands simultaneous high-capacity and high-mobility mobile broadband. This is because future users will expect high-quality connectivity regardless of their location or speed. Another automotive application is an augmented reality dashboard, which overlays information on what the driver sees through the windshield, identifying objects in the dark and informing the driver about their distance and movement. In the future, wireless modules will enable communication between vehicles, the exchange of information between vehicles and supporting infrastructure, and between vehicles and other connected devices (e.g., devices accompanying pedestrians). Safety systems can guide drivers on alternative courses of action to reduce the risk of accidents, enabling safer driving. The next step will be remotely controlled or self-driving vehicles, which will require highly reliable and fast communication between different self-driving vehicles and between vehicles and infrastructure. In the future, self-driving cars will perform all driving tasks, leaving drivers to focus solely on traffic anomalies that the vehicles themselves cannot detect. The technological requirements for self-driving cars will require ultra-low latency and ultra-high-speed reliability, increasing traffic safety to levels unattainable by humans.

[0074] Smart cities and smart homes, often referred to as "smart societies," will be embedded with dense wireless sensor networks. A distributed network of intelligent sensors will identify conditions for cost- and energy-efficient maintenance of cities or homes. A similar setup can be implemented for each home. Temperature sensors, window and heating controllers, burglar alarms, and appliances will all be connected wirelessly. Many of these sensors typically have low data rates, low power, and low cost. However, for example, real-time HD video may be required for certain types of devices for surveillance purposes.

[0075] The consumption and distribution of energy, including heat and gas, are becoming increasingly decentralized, requiring automated control of distributed sensor networks. Smart grids interconnect these sensors using digital information and communication technologies to collect and act on information. This information can include the behavior of suppliers and consumers, enabling smart grids to improve efficiency, reliability, economic efficiency, sustainable production, and automated distribution of fuels like electricity. Smart grids can also be viewed as another low-latency sensor network.

[0076] The health sector has numerous applications that can benefit from mobile communications. Telecommunications systems can support telemedicine, which provides clinical care in remote locations. This can help reduce distance barriers and improve access to health services that are otherwise unavailable 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 sensors for parameters such as heart rate and blood pressure.

[0077] Wireless and mobile communications are becoming increasingly important in industrial applications. Wiring is expensive to install and maintain. Therefore, the potential to replace cables with reconfigurable wireless links presents an attractive opportunity for many industries. However, achieving this requires wireless connections to operate with similar latency, reliability, and capacity to cables, while simplifying their management. Low latency and extremely low error rates are new requirements for 5G connectivity.

[0078] Logistics and freight tracking are important use cases for mobile communications, enabling the tracking of inventory and packages anywhere using location-based information systems. Logistics and freight tracking typically require low data rates but wide coverage and reliable location information.

[0079] Multi-Input Multi-Output (MIMO) technology in NR systems provides a scalable and flexible MIMO framework. Basically, it includes beam-based operation, scalable and flexible Channel State Information (CSI) codebook, reference signal (RS) design, and codebook design for CSI Type I and CSI Type II. Additionally, improvements have been introduced to support a CSI Type II codebook for multi-user (MU)-MIMO, multiple transmit / receive points (TRPs) or multiple panel transmission operations depending on backhaul conditions, multi-beam operation, high uplink transmit power support, and reference signals with low Peak-to-Average Power Ratio (PAPR) characteristics. Furthermore, beam management methods to reduce beam failure for wireless devices moving at high frequencies, expansion of multi-TRP transmission in uplink and downlink, sounding reference signals (SRSs) for capacity and coverage expansion, and improvements to Type II CSI-RSs can be supported.

[0080] Describes a conventional wireless communication system. This may also be called an Evolved-UMTS Terrestrial Radio Access Network (E-UTRAN) or a Long Term Evolution (LTE) / LTE-A system.

[0081] E-UTRAN includes a base station (BS), which provides a control plane and a user plane to user equipment (UE). A UE may be fixed or mobile, and may be referred to by other terms such as a mobile station (MS), a user terminal (UT), a subscriber station (SS), a mobile terminal (MT), a wireless device, or a terminal. A base station (BS) is a fixed point that communicates with a UE, and may be referred to by other terms such as an evolved-NodeB (eNB), a gNodeB (gNB), a base transceiver system (BTS), or an access point.

[0082] Base stations can be interconnected via the X2 interface. Base stations are connected to the Evolved Packet Core (EPC) via the S1 interface, more specifically, to the Mobility Management Entity (MME) via the S1-MME, and to the Serving Gateway (S-GW) via the S1-U.

[0083] The EPC consists of an MME, an S-GW, and a P-GW (Packet Data Network Gateway). The MME holds information about terminal access and capabilities, and this information is primarily used for terminal mobility management. The S-GW is a gateway that terminates on the E-UTRAN, and the P-GW is a gateway that terminates on the PDN.

[0084] Figure 1 illustrates the system architecture of a New Generation Radio Access Network (NG-RAN) to which NR is applied.

[0085] Referring to Fig. 1, the NG-RAN may include gNBs and / or eNBs that provide user plane and control plane protocol termination to the UE. Fig. 1 exemplifies a case including only gNBs. The gNBs (eNBs) are connected to each other via Xn interfaces. The gNBs and eNBs are connected to the 5th generation core network (5G Core Network: 5GC) via the NG interface. More specifically, they are connected to the access and mobility management function (AMF) via the NG-C interface, and to the user plane function (UPF) via the NG-U interface.

[0086] The layers of the radio interface protocol between the terminal and the network can be divided into L1 (layer 1), L2 (layer 2), and L3 (layer 3) based on the three lower layers of the Open System Interconnection (OSI) standard model, which is widely known in communication systems. Among these, the physical layer belonging to layer 1 provides information transfer service using physical channels, and the RRC (Radio Resource Control) layer located in layer 3 controls radio resources between the terminal and the network. To this end, the RRC layer exchanges RRC messages between the terminal and the base station.

[0087] Figure 2 is a block diagram illustrating the radio protocol architecture for the user plane. Figure 3 is a block diagram illustrating the radio protocol architecture for the control plane. The user plane is a protocol stack for transmitting user data, and the control plane is a protocol stack for transmitting control signals.

[0088] Referring to Figures 2 and 3, the physical layer (PHY layer) provides information transfer services to upper layers using physical channels. The PHY layer is connected to its upper layer, the Medium Access Control (MAC) layer, through a transport channel. Data is transferred between the MAC layer and the PHY layer via the transport channel. Transport channels are classified based on how and with what characteristics data is transmitted over the wireless interface.

[0089] Data travels between different physical layers, i.e., between the physical layers of a transmitter and receiver, via a physical channel. This physical channel can be modulated using Orthogonal Frequency Division Multiplexing (OFDM) and utilizes time and frequency as radio resources.

[0090] The MAC layer's functions include mapping between logical channels and transport channels, and multiplexing / demultiplexing MAC service data units (SDUs) belonging to logical channels into transport blocks provided as physical channels on the transport channels. The MAC layer provides services to the RLC (Radio Link Control) layer through logical channels.

[0091] The functions of the RLC layer include concatenation, segmentation, and reassembly of RLC SDUs. To guarantee the various Quality of Service (QoS) required by radio bearers (RBs), the RLC layer provides three operating modes: Transparent Mode (TM), Unacknowledged Mode (UM), and Acknowledged Mode (AM). AM RLC provides error correction through automatic repeat request (ARQ).

[0092] The RRC (Radio Resource Control) layer is defined only in the control plane. The RRC layer is responsible for controlling logical, transport, and physical channels, including the configuration, reconfiguration, and release of radio bearers. An RB is a logical path provided by Layer 1 (PHY layer) and Layer 2 (MAC layer, RLC layer, PDCP layer) for data transmission between a terminal and the network.

[0093] The functions of the Packet Data Convergence Protocol (PDCP) layer in the user plane include the transmission of user data, header compression, and ciphering. The functions of the Packet Data Convergence Protocol (PDCP) layer in the control plane include the transmission of control plane data and encryption / integrity protection.

[0094] Establishing an RB refers to the process of defining the characteristics of the radio protocol layer and channel to provide a specific service, and setting specific parameters and operating methods for each. RBs can be further divided into two types: signaling RBs (SRBs) and data RBs (DRBs). SRBs are used as a conduit for transmitting RRC messages in the control plane, while DRBs are used as conduits for transmitting user data in the user plane.

[0095] When an RRC connection is established between the RRC layer of the terminal and the RRC layer of the E-UTRAN, the terminal is in an RRC connected state, otherwise it is in an RRC idle state.

[0096] Downlink transmission channels that transmit data from the network to the terminal include the Broadcast Channel (BCH), which transmits system information, and the downlink Shared Channel (SCH), which transmits user traffic or control messages. Traffic or control messages for downlink multicast or broadcast services may be transmitted through the downlink SCH or a separate downlink Multicast Channel (MCH). Meanwhile, uplink transmission channels that transmit data from the terminal to the network include the Random Access Channel (RACH), which transmits initial control messages, and the uplink Shared Channel (SCH), which transmits user traffic or control messages.

[0097] Logical channels that are located above the transport channel and are mapped to the transport channel include BCCH (Broadcast Control Channel), PCCH (Paging Control Channel), CCCH (Common Control Channel), MCCH (Multicast Control Channel), and MTCH (Multicast Traffic Channel).

[0098] A physical channel consists of multiple OFDM symbols in the time domain and multiple subcarriers in the frequency domain. A single subframe consists of multiple OFDM symbols in the time domain. A resource block is a resource allocation unit and consists of multiple OFDM symbols and multiple subcarriers. Additionally, each subframe can use specific subcarriers of specific OFDM symbols (e.g., the first OFDM symbol) of the subframe for a Physical Downlink Control Channel (PDCCH), for example, an L1 / L2 control channel. A Transmission Time Interval (TTI) is a unit time for subframe transmission.

[0099] Figure 4 illustrates the functional division between NG-RAN and 5GC.

[0100] Referring to FIG. 4, the gNB can provide functions such as inter-cell radio resource management (Inter Cell RRM), radio bearer management (RB control), connection mobility control (Connection Mobility Control), radio admission control (Radio Admission Control), measurement configuration and provision, and dynamic resource allocation. The AMF can provide functions such as NAS security and idle state mobility processing. The UPF can provide functions such as mobility anchoring and PDU processing. The SMF (Session Management Function) can provide functions such as terminal IP address allocation and PDU session control.

[0101] Figure 5 illustrates a frame structure that can be applied in NR.

[0102] Referring to FIG. 5, a radio frame (hereinafter abbreviated as a frame) can be used for uplink and downlink transmission in NR. A frame has a length of 10 ms and can be defined as two 5 ms half-frames (Half-Frames, HF). A half-frame can be defined as five 1 ms sub-frames (Subframes, SF). A frame can include 10 sub-frames. A sub-frame can be divided into one or more slots, and the number of slots in a sub-frame depends on the Subcarrier Spacing (SCS). Each slot includes 12 or 14 OFDM (A) symbols depending on the cyclic prefix (CP). When a normal CP is used, each slot includes 14 symbols. When an extended CP is used, each slot includes 12 symbols. Here, the symbol may include an OFDM symbol (or CP-OFDM symbol), an SC-FDMA symbol (or a DFT-s-OFDM symbol). A mini-slot may include, for example, 2, 4, or 7 symbols, or may include more or fewer symbols.

[0103] NR systems can support multiple numerologies. Numerologies can be defined by subcarrier spacing and cyclic prefix (CP) overhead. Multiple subcarrier spacings can be derived by scaling the basic subcarrier spacing by an integer N. Furthermore, even if it is assumed that very low subcarrier spacing is not utilized at very high carrier frequencies, the numerologies utilized can be selected independently of the frequency band. Furthermore, NR systems can support various frame structures corresponding to multiple numerologies.

[0104] Below, we examine the Orthogonal Frequency Division Multiplexing (OFDM) numerologies and frame structures that can be considered in NR systems. Table 1 lists the various OFDM numerologies supported in NR systems.

[0105] Table 1 below illustrates the subcarrier spacing configuration μ (also referred to as subcarrier spacing configuration).

[0106] [Table 1]

[0107]

[0108] Regarding the frame structure in the NR system, the sizes of the various fields in the time domain are T s =1 / (Δf max ·N f ) can be expressed as a multiple of the time unit. Here, Δf max =480·10 3 and N f =409. Downlink and uplink transmissions are T f =(Δf max ·N f / 100)·T s = It consists of a radio frame with a duration of 10ms. Here, each radio frame is T sf =(Δf max ·N f / 1000)·T s = It consists of 10 subframes with a duration of 1ms. In this case, there may be one set of frames for uplink and one set of frames for downlink. In addition, the transmission of uplink frame number i from a terminal (User Equipment, UE) is T earlier than the start of the corresponding downlink frame from the terminal. TA =N TA ·T sIt must start before. For numerology μ, slots are n within a subframe. μ s ∈{0, ..., N slots,μ subframe -1} are numbered in increasing order, and n within a radio frame μ s,f ∈{0, ..., N slots,μ frame -1} are numbered in increasing order. One slot is N μ symb It consists of consecutive OFDM symbols, and N μ symb is determined by the numerology and slot configuration used. Slot n in a subframe μ s The start of OFDM symbol n in the same subframe μ s N μ symb are aligned temporally with the start of the OFDM signal. Not all terminals can transmit and receive simultaneously, which means that not all OFDM symbols in a downlink slot or uplink slot can be utilized.

[0109] Table 2 below shows the number of slots (N) in a frame according to the subcarrier spacing setting μ. frame,μ slot ), number of slots in a subframe (N subframe,μ slot ), number of symbols in the slot (N slot symb ) are examples.

[0110] [Table 2]

[0111]

[0112] Table 2-1 below illustrates that when extended CP is used, the number of symbols per slot, the number of slots per frame, and the number of slots per subframe change depending on the SCS.

[0113] [Table 2-1]

[0114]

[0115] In an NR system, OFDM(A) numerologies (e.g., SCS, CP length, etc.) may be set differently between multiple cells that are merged into a single terminal. Accordingly, the (absolute time) interval of a time resource (e.g., SF, slot, or TTI) (conveniently referred to as TU (Time Unit)) consisting of the same number of symbols may be set differently between the merged cells.

[0116] In relation to physical resources in an NR system, antenna ports, resource grids, resource elements, resource blocks, and carrier parts can be considered. Hereinafter, the physical resources that can be considered in an NR system will be described in detail. First, with respect to antenna ports, an antenna port is defined such that the channel through which a symbol on the antenna port is carried can be inferred from the channel through which another symbol on the same antenna port is carried. If the large-scale properties of the channel through which a symbol on one antenna port is carried can be inferred from the channel through which a symbol on another antenna port is carried, then the two antenna ports can be said to be in a QC / QCL (quasi co-located or quasi co-location) relationship. Here, the large-scale properties include one or more of delay spread, Doppler spread, frequency shift, average received power, and received timing.

[0117] Figure 6 shows an example of a resource grid in NR.

[0118] Referring to Figure 6, the resource grid is N in the frequency domain. μ RB N RB sc It consists of subcarriers, and one subframe is 14·2 μ It is described as an example, but not limited to, that it consists of OFDM symbols. In an NR system, the transmitted signal is N μ RB N RB sc One or more resource grids consisting of subcarriers and 2 μ N (μ) symb is described by OFDM symbols. Here, N μ RB≤ N max,μ RB is. The above N max,μ RB represents the maximum transmission bandwidth, which may vary between numerologies as well as between uplink and downlink. In this case, one resource grid may be configured for each numerology μ and each antenna port p. Each element of the resource grid for numerology μ and each antenna port p is referred to as a resource element and is uniquely identified by an index pair {index in the frequency domain, position of the symbol within the subframe}. If there is no risk of confusion or if a particular antenna port or numerology is not specified, the indices p and μ may be dropped. In addition, a resource block (RB) is defined as N in the frequency domain. RB sc =12 is defined as a series of consecutive subcarriers.

[0119] Point A serves as a common reference point of the resource block grid and is obtained as follows.

[0120] offsetToPointA for primary cell (Pcell) downlink represents the frequency offset between the lowest subcarrier of the lowest resource block overlapping the SS / PBCH block used by the terminal for initial cell selection and point A, expressed in resource block units assuming 15 kHz subcarrier spacing for FR1 and 60 kHz subcarrier spacing for FR2, and absoluteFrequencyPointA represents the frequency-location of point A expressed as in absolute radio-frequency channel number (ARFCN).

[0121] Common resource blocks (CRBs) are numbered from 0 upwards in the frequency domain for a subcarrier spacing setting μ. The center of subcarrier 0 of CRB 0 for a subcarrier spacing setting μ coincides with 'point A'. CRB number n in the frequency domain μ CRB The resource elements (k,l) for the subcarrier spacing setting μ are given by the following equation.

[0122] [Formula 1]

[0123]

[0124] k is defined relative to point A so that k=0 corresponds to the subcarrier centered at point A. Physical resource blocks are numbered from 0 to N within the bandwidth part (BWP). size BWP,i - Numbered from 1 to 1, where i is the number of BWP. Physical resource block n in BWP i PRB and common resource block n CRBThe relationship between them is given by the equation below.

[0125] [Formula 2]

[0126]

[0127] N start BWP,i is a common resource block where BWP starts relative to common resource block 0.

[0128] Figure 7 shows an example of a physical resource block in NR.

[0129] Referring to FIG. 7, a physical resource block (PRB) may be composed of different frequency resources and time resources depending on the subcarrier spacing.

[0130] Figure 8 illustrates the slot structure of an NR frame.

[0131] Referring to FIG. 8, a slot may include multiple symbols in the time domain. For example, in the case of a normal CP, one slot may include 14 symbols, but in the case of an extended CP, one slot may include 12 symbols. A carrier may include multiple subcarriers in the frequency domain. A Resource Block (RB) may be defined as multiple (e.g., 12) consecutive subcarriers in the frequency domain. A Bandwidth Part (BWP) may be defined as multiple consecutive (P)RBs in the frequency domain, and may correspond to a single numerology (e.g., SCS, CP length, etc.). A carrier may include up to N BWPs (e.g., 4 or 5). Data communication is performed through activated BWPs, and only one BWP may be activated for one terminal. In the resource grid, each element is referred to as a Resource Element (RE), to which one complex symbol can be mapped.

[0132] As another example, in the time domain, a slot for a normal CP contains 7 symbols, but in the case of an extended CP, a slot contains 6 symbols. A carrier contains multiple subcarriers in the frequency domain. A Resource Block (RB) is defined as multiple (e.g., 12) consecutive subcarriers in the frequency domain. A Bandwidth Part (BWP) is defined as multiple consecutive (P)RBs in the frequency domain, and can correspond to a single numerology (e.g., SCS, CP length, etc.). A carrier can contain up to N (e.g., 5) BWPs. Data communication is performed through activated BWPs, and only one BWP can be activated for a single terminal. Each element in the resource grid is referred to as a Resource Element (RE), to which one complex symbol can be mapped.

[0133] A PDCCH (physical downlink control channel) may be composed of one or more CCEs (control channel elements) as shown in Table 3 below.

[0134] [Table 3]

[0135]

[0136] For example, a PDCCH can be transmitted via a resource consisting of 1, 2, 4, 8, or 16 CCEs, where a CCE is composed of six REGs (resource element groups), and one REG is composed of one resource block in the frequency domain and one OFDM (orthogonal frequency division multiplexing) symbol in the time domain.

[0137] Monitoring refers to decoding each PDCCH candidate according to the DCI (downlink control information) format. The terminal monitors a set of PDCCH candidates in one or more core sets (CORESETs, described below) on the active DL BWP of each activated serving cell for which PDCCH monitoring is configured, according to the corresponding search space set.

[0138] In NR, a new unit called a control resource set (CORESET) can be introduced. A terminal can receive PDCCHs in a CORESET.

[0139] Figure 9 illustrates a core set.

[0140] Referring to Figure 9, the core set is N in the frequency domain. CORESET RB It consists of N resource blocks and is in the time domain. CORESET symb ∈ {1, 2, 3} symbols. N CORESET RB , N CORESET symb can be provided by the base station via upper layer signals. As illustrated in Fig. 9, a core set may include multiple CCEs (or REGs).

[0141] A terminal may attempt PDCCH detection in units of 1, 2, 4, 8, or 16 CCEs within a core set. One or more CCEs for which PDCCH detection can be attempted may be referred to as PDCCH candidates.

[0142] A terminal can be configured with multiple core sets.

[0143] In conventional wireless communication systems (e.g., LTE / LTE-A), the control domain spans the entire system bandwidth used by the base station. Except for some terminals that support only narrow bandwidths (e.g., eMTC / NB-IoT terminals), all terminals must be able to receive radio signals across the entire system bandwidth of the base station to properly receive / decode the control information transmitted by the base station.

[0144] In contrast, NR introduces the aforementioned core set. A core set is a radio resource for control information that a terminal must receive. It can utilize only a portion of the system bandwidth in the frequency domain, rather than the entire bandwidth. Furthermore, it can utilize only a portion of the symbols within a slot in the time domain. The base station can assign a core set to each terminal and transmit control information through the assigned core set. In NR, a terminal can receive control information from the base station without necessarily receiving the entire system bandwidth.

[0145] The core set may include a terminal-specific core set for transmitting terminal-specific control information and a common core set for transmitting control information common to all terminals.

[0146] Meanwhile, in NR, depending on the application field, high reliability may be required, and in such a situation, the target BLER (block error rate) for downlink control information (DCI) transmitted through a downlink control channel (e.g., physical downlink control channel: PDCCH) may be significantly lower than in the prior art. One example of a method for satisfying such a requirement requiring high reliability is to reduce the amount of content included in the DCI and / or increase the amount of resources used when transmitting the DCI. In this case, the resources may include at least one of time domain resources, frequency domain resources, code domain resources, and spatial domain resources.

[0147] The following technologies / features can be applied in NR:

[0148] Self-contained subframe structure

[0149] Figure 10 illustrates an example of a slot structure for a new wireless access technology.

[0150] In NR, a structure in which a control channel and a data channel are time-division multiplexed (TDM) within one TTI, as shown in Fig. 10, can be considered for the purpose of minimizing latency.

[0151] FIG. 10 illustrates an example in which a downlink control region is located at the front of the TTI and an uplink control region is located at the back of the TTI. The region between the downlink control region and the uplink control region can be used for downlink data (DL data) transmission or uplink data (UL data) transmission. A characteristic of this structure is that downlink (DL) reception and uplink (UL) transmission are sequentially performed within a single subframe / slot, so that DL data can be received and UL ACK / NACK (Acknowledgement / Not-acknowledgement) can be transmitted within a single subframe / slot. As a result, the time required for data retransmission when a data transmission error occurs is reduced, thereby minimizing the latency of the final data transmission.

[0152] In this way, in a structure where data and control domains are TDMed, a time gap is required for the base station and terminal to transition from transmission mode to reception mode, or from reception mode to transmission mode. To this end, some OFDM symbols at the transition point from DL to UL in a self-contained subframe structure can be designated as a guard period (GP).

[0153] Figure 11 illustrates the structure of a self-contained slot.

[0154] In an NR system, a single slot may contain a DL control channel, DL or UL data, and a UL control channel. For example, the first N symbols in a slot may be used to transmit a DL control channel (hereinafter, referred to as a DL control region), and the last M symbols in the slot may be used to transmit a UL control channel (hereinafter, referred to as a UL control region). N and M are each integers greater than or equal to 0. A resource region (hereinafter, referred to as a data region) between the DL control region and the UL control region may be used for DL ​​data transmission or UL data transmission. As an example, the following configuration may be considered. Each section is listed in chronological order.

[0155] 1. DL only configuration

[0156] 2. UL only configuration

[0157] 3. Mixed UL-DL configuration

[0158] - DL area + GP (Guard Period) + UL control area

[0159] - DL control area + GP + UL area

[0160] DL area: (i) DL data area, (ii) DL control area + DL data area

[0161] UL domain: (i) UL data domain, (ii) UL data domain + UL control domain

[0162] In the DL control region, a PDCCH can be transmitted, and in the DL data region, a PDSCH (physical downlink shared channel) can be transmitted. In the UL control region, a PUCCH (physical uplink control channel) can be transmitted, and in the UL data region, a PUSCH (physical uplink shared channel) can be transmitted. In the PDCCH, downlink control information (DCI), such as DL data scheduling information and UL data scheduling information, can be transmitted. In the PUCCH, uplink control information (UCI), such as ACK / NACK (Positive Acknowledgement / Negative Acknowledgement) information for DL ​​data, CSI (Channel State Information) information, and SR (Scheduling Request), can be transmitted. GP provides a time gap when a base station and a terminal switch from transmission mode to reception mode or from reception mode to transmission mode. Some symbols at the time of switching from DL to UL within a subframe can be set as GP.

[0163] System information of an NR system can be transmitted in a broadcasting manner. At this time, analog beams belonging to different antenna panels within one symbol can be transmitted simultaneously, and a method of introducing a beam reference signal (BRS), which is a reference signal (RS) transmitted by applying a single analog beam (corresponding to a specific antenna panel) to measure a channel for each analog beam, is being discussed. The BRS can be defined for multiple antenna ports, and each antenna port of the BRS can correspond to a single analog beam. At this time, unlike the BRS, a synchronization signal or xPBCH can be transmitted by applying all analog beams within an analog beam group so that any terminal can receive it well.

[0164] In NR, a synchronization signal block (SSB, or may be referred to as a synchronization signal and physical broadcast channel (SS / PBCH) in the time domain) may be composed of four OFDM symbols numbered in ascending order from 0 to 3 within the synchronization signal block, and a primary synchronization signal (PSS), a secondary synchronization signal (SSS), and a PBCH associated with a demodulation reference signal (DMRS) may be mapped to the symbols. As described above, the synchronization signal block may also be referred to as an SS / PBCH block.

[0165] In NR, multiple synchronization signal blocks can be transmitted at different times, and SSB can be used to perform initial access (IA), serving cell measurement, etc. Therefore, when the transmission time and resources overlap with other signals, it is desirable to transmit SSB preferentially. To achieve this, the network can broadcast SSB transmission time and resource information or indicate it through UE-specific RRC signaling.

[0166] NR can perform beam-based transmission and reception operations. If the reception performance of the current serving beam degrades, a process called beam failure recovery (BFR) can be used to find a new beam.

[0167] Since BFR is not a process for declaring an error / failure in the link between the network and the terminal, it can be assumed that the connection with the current serving cell is maintained even when the BFR process is performed. During the BFR process, measurements are performed on different beams set by the network (a beam can be expressed as a CSI-RS port or an SSB (synchronization signal block) index, etc.) and the best beam for the terminal is selected. The terminal can proceed with the BFR process by performing the RACH process associated with the beam with the best measurement result.

[0168] Now, we will describe the Transmission Configuration Indicator (TCI) state. The TCI state can be set for each core set of the control channel, and parameters for determining the terminal's receive (Rx) beam can be determined based on the TCI state.

[0169] For each downlink bandwidth portion (DL BWP) of a serving cell, a terminal may be configured with up to three core sets. Additionally, for each core set, the terminal may be provided with the following information:

[0170] 1) Coreset index p (e.g., one from 0 to 11, where the index of each coreset can be uniquely determined among the BWPs of a serving cell),

[0171] 2) PDCCH DM-RS scrambling sequence initialization value,

[0172] 3) Interval in the time domain of the core set (can be given in symbol units),

[0173] 4) A set of resource blocks,

[0174] 5) CCE-to-REG mapping parameters,

[0175] 6) Antenna port quasi co-location (QCL) information indicating quasi co-location (QCL) information of DM-RS antenna ports for PDCCH reception in each core set (from a set of antenna port quasi co-locations provided by a higher layer parameter called 'TCI-State');

[0176] 7) Indicating the presence or absence of a transmission configuration indication (TCI) field for a specific DCI format transmitted by PDCCH in the core set, etc.

[0177] Let's explain QCL. If the characteristics of the channel through which a symbol on one antenna port is transmitted can be inferred from the characteristics of the channel through which a symbol on another antenna port is transmitted, then the two antenna ports are said to be in quasi-co-location (QCL). For example, if two signals (A and B) are transmitted from the same transmit antenna array with identical / similar spatial filters applied, the two signals may experience identical / similar channel conditions. From the receiver's perspective, if one of the two signals is received, the channel characteristics of the received signal can be used to detect the other signal.

[0178] In this sense, the fact that A and B are QCL may mean that A and B experienced similar channel conditions, and thus, the channel information estimated to detect A is also useful for detecting B. Here, the channel conditions may be defined by, for example, Doppler shift, Doppler spread, average delay, delay spread, spatial reception parameters, etc.

[0179] The 'TCI-State' parameter associates one or two downlink reference signals with a corresponding QCL type (there are QCL types A, B, C, and D, see Table 4).

[0180] [Table 4]

[0181]

[0182] Each 'TCI-State' may include parameters for establishing a quasi-colocation (QCL) relationship between one or two downlink reference signals and a DM-RS port of a PDSCH (or PDCCH), or a CSI-RS port of a CSI-RS resource.

[0183] Meanwhile, in each DL BWP configured for a terminal in a serving cell, the terminal may be provided with up to 10 search space sets. For each search space set, the terminal may be provided with at least one of the following pieces of information.

[0184] 1) Search space set index s (0≤s<40), 2) Association between core set P and search space set s, 3) PDCCH monitoring period and PDCCH monitoring offset (slot unit), 4) PDCCH monitoring pattern within a slot (e.g., indicating the first symbol of the core set within a slot for PDCCH monitoring), 5) Number of slots in which search space set s exists, 6) Number of PDCCH candidates per CCE aggregation level, 7) Information indicating whether search space set s is CSS (common search space) or USS (UE-specific search space), etc.

[0185] In NR, core set #0 can be configured by PBCH (or terminal-specific signaling for handover, PSCell configuration, or BWP configuration). The search space (SS) set #0 configured by PBCH can have different monitoring offsets (e.g., slot offset, symbol offset) for each associated SSB. This may be necessary to minimize the search space occasions that the terminal must monitor. Alternatively, it may also be necessary to provide a beam sweeping control / data area that can transmit control / data for each beam so that communication with the terminal can be continuously performed in a situation where the best beam of the terminal dynamically changes.

[0186] Figure 12 illustrates physical channels and typical signal transmission.

[0187] Referring to Figure 12, in a wireless communication system, a terminal receives information from a base station via the downlink (DL), and the terminal transmits information to the base station via the uplink (UL). The information transmitted and received between the base station and the terminal includes data and various control information, and various physical channels exist depending on the type and purpose of the information they transmit and receive.

[0188] When a terminal is powered on again from a powered-off state or newly enters a cell, it performs an initial cell search operation, such as synchronizing with the base station (S11). To this end, the terminal receives the PSCH (Primary Synchronization Channel) and SSCH (Secondary Synchronization Channel) from the base station to synchronize with the base station and obtain information such as the cell ID (cell identity). In addition, the terminal can obtain broadcast information within the cell by receiving the PBCH (Physical Broadcast Channel) from the base station. In addition, the terminal can receive the DL RS (Downlink Reference Signal) during the initial cell search phase to check the downlink channel status.

[0189] (Initial) cell search can be defined as a procedure in which a terminal acquires time and frequency synchronization with a cell and detects the cell ID of the cell. Cell search can be based on the primary synchronization signal and secondary synchronization signal of the cell, and the PBCH DMRS.

[0190] A terminal that has completed initial cell search can obtain more specific system information by receiving a PDCCH (Physical Downlink Control Channel) and a corresponding PDSCH (Physical Downlink Control Channel) (S12).

[0191] Thereafter, the terminal may perform a random access procedure (Random Access Procedure) to complete connection to the base station (S13-S16). Specifically, the terminal may transmit a preamble through a Physical Random Access Channel (PRACH) (S13) and receive a Random Access Response (RAR) for the preamble through a PDCCH and a corresponding PDSCH (S14). Thereafter, the terminal may transmit a Physical Uplink Shared Channel (PUSCH) using scheduling information in the RAR (S15) and perform a contention resolution procedure (Contention Resolution Procedure) such as a PDCCH and a corresponding PDSCH (which may be considered a process of receiving a contention resolution message) (S16).

[0192] When accessing a base station for the first time or when there is no radio resource for signal transmission, a terminal may perform a random access procedure (RACH) for the base station. At this time, a 4-step contention-based or type-1 random access may include a first step in which the terminal transmits a random access preamble (or Msg1) to the base station, a second step in which the terminal receives a random access response (RAR) (or Msg2) from the base station, a third step in which the terminal transmits an uplink message (or Msg3) to the base station, and a fourth step in which the terminal receives a contention resolution message (or Msg4) from the base station. Alternatively, a 2-step contention-based or type-2 random access may include a step A in which the terminal transmits a random access preamble and an uplink message to the base station, and a step B in which the terminal receives a random access response and a contention resolution message from the base station. A contention-free random access procedure may only include steps 1 and 2 of a contention-based access procedure, and steps 3 and 4 are not required because no contention occurs between terminals.

[0193] The terminal can transmit a random access preamble or PRACH to the base station based on the random access opportunity (RO), preamble transmission power, etc. provided through SIB1 or dedicated RRC signaling. Here, the terminal can select an optimal SSB or CSI-RS (Channel Status Information-Reference Signal) and determine an RO and / or preamble index group associated with the selected SSB or CSI-RS. The terminal can select an optimal SSB and a corresponding reception beam from among a plurality of SSBs corresponding to the multi-beam sweeping of the base station during the initial access process. Meanwhile, after the initial access, the terminal can perform transmission beam and / or reception beam selection or change through a CSI measurement and reporting process based on the CSI-RS from the base station in an RRC connection state.

[0194] After the terminal transmits the preamble, the terminal can monitor RAR reception for a predetermined period of time. For example, the terminal can monitor the PDCCH scrambled with RA-RNTI and receive the RAR through the PDSCH transmitted in the resource scheduled by the DCI in the PDCCH. The RAR may include a Random Access Preamble Identifier (RAPID), an uplink grant (UL Grant) for Msg3 scheduling, a temporary cell identifier (Temporary C(Cell)-RNTI), and a Timing Advance Command (TAC) determined based on the preamble reception timing.

[0195] If the terminal fails to successfully receive the RAR, the preamble can be retransmitted by applying power ramping, etc.

[0196] If the terminal successfully receives the RAR, it can transmit Msg3 based on the UL grant within the RAR. Once Msg3 is transmitted, the terminal can start the contention resolution timer (CR timer) and perform PDCCH monitoring based on the C-RNTI for Msg4 reception. If Msg4 is received while the CR timer is running, the terminal can determine that contention resolution has been successfully completed.

[0197] A terminal that has performed the above-described procedure can then perform PDCCH / PDSCH reception (S17) and PUSCH / PUCCH (Physical Uplink Control Channel) transmission (S18) as general uplink / downlink signal transmission procedures. Control information that the terminal transmits to the base station is referred to as UCI (Uplink Control Information). UCI includes HARQ ACK / NACK (Hybrid Automatic Repeat and reQuest Acknowledgement / Negative-ACK), SR (Scheduling Request), CSI (Channel State Information), etc. CSI includes CQI (Channel Quality Indicator), PMI (Precoding Matrix Indicator), RI (Rank Indication), etc. UCI is generally transmitted through PUCCH, but can be transmitted through PUSCH when control information and data must be transmitted simultaneously. In addition, the terminal can aperiodically transmit UCI through PUSCH according to a request / instruction of the network. UCI can be repeatedly transmitted over PUCCH.

[0198] Meanwhile, the control information that the terminal transmits to the base station via the uplink (or that the terminal receives from the base station) may include downlink / uplink ACK / NACK signals, CQI (Channel Quality Indicator), PMI (Precoding Matrix Index), RI (Rank Indicator), etc. For example, in the case of a 3GPP LTE system, the terminal may transmit the above-described control information such as CQI / PMI / RI via PUSCH and / or PUCCH.

[0199] The table below shows an example of the DCI format.

[0200] [Table 5]

[0201]

[0202] Referring to Table 5 above, DCI formats 0_0, 0_1, and 0_2 may include resource information related to scheduling of PUSCH (e.g., UL / SUL (Supplementary UL), frequency resource allocation, time resource allocation, frequency hopping, etc.), transport block (TB) related information (e.g., MCS, NDI, RV, etc.), HARQ related information (e.g., process number, DAI, PDSCH-HARQ feedback timing, etc.), multi-antenna related information (e.g., DMRS sequence initialization information, antenna port, CSI request, etc.), power control information (e.g., PUSCH power control, etc.), and the control information included in each DCI format may be predefined.

[0203] DCI format 0_0 is used for scheduling PUSCH in a single cell. The information contained in DCI format 0_0 is CRC-scrambled and transmitted using C-RNTI, CS-RNTI, or MCS-C-RNTI.

[0204] DCI format 0_1 ​​is used to schedule one or more PUSCHs in a single cell, or to indicate configured grant (CG) downlink feedback information to the UE. The information contained in DCI format 0_1 ​​is CRC-scrambled and transmitted using the C-RNTI, CS-RNTI, SP-CSI-RNTI, or MCS-C-RNTI.

[0205] DCI format 0_2 is used for scheduling PUSCH in a single cell. The information contained in DCI format 0_2 is CRC-scrambled and transmitted using C-RNTI, CS-RNTI, SP-CSI-RNTI, or MCS-C-RNTI.

[0206] Next, DCI formats 1_0, 1_1, and 1_2 may include resource information related to scheduling of PDSCH (e.g., frequency resource allocation, time resource allocation, VRB-PRB mapping, etc.), transport block (TB) related information (e.g., MCS, NDI, RV, etc.), HARQ related information (e.g., process number, DAI, PDSCH-HARQ feedback timing, etc.), multi-antenna related information (e.g., antenna port, TCI, SRS request, etc.), PUCCH related information (e.g., PUCCH power control, PUCCH resource indicator, etc.), and control information included in each DCI format may be predefined.

[0207] DCI format 1_0 is used for scheduling PDSCH in a DL cell. The information contained in DCI format 1_0 is CRC-scrambled and transmitted using C-RNTI, CS-RNTI, or MCS-C-RNTI.

[0208] DCI format 1_1 is used for scheduling PDSCH in a single cell. Information included in DCI format 1_1 is CRC-scrambled and transmitted using C-RNTI, CS-RNTI, or MCS-C-RNTI.

[0209] DCI format 1_2 is used for scheduling PDSCH in a single cell. The information contained in DCI format 1_2 is CRC-scrambled and transmitted using C-RNTI, CS-RNTI, or MCS-C-RNTI.

[0210] Meanwhile, the 5G mobile communications system, a successor to LTE (long-term evolution), is a new clean-slate mobile communications system characterized by high performance, low latency, and high availability. 5G NR can utilize all available spectrum resources, from low-frequency bands below 1 GHz, to intermediate-frequency bands between 1 GHz and 10 GHz, and high-frequency (millimeter wave) bands above 24 GHz. Based on these foundational technologies for 5G mobile communications, 6G mobile communications systems are being developed.

[0211] The 6G (wireless) system aims to provide (i) very high data rates per device, (ii) a very large number of connected devices, (iii) global connectivity, (iv) very low latency, (v) low energy consumption for battery-free Internet of Things (IoT) devices, (vi) ultra-reliable connectivity, and (vii) connected intelligence with machine learning capabilities. The vision of the 6G system can be divided into four aspects: intelligent connectivity, deep connectivity, holographic connectivity, and ubiquitous connectivity.

[0212] A 6G system can satisfy the requirements shown in Table 6 below. Table 6 can represent an example of the requirements of a 6G system.

[0213] [Table 6]

[0214]

[0215] 6G Network Structure

[0216] Figure 13 illustrates an example of a flexible network topology to which embodiments of the present specification may be applied.

[0217] Referring to Figure 13, a network topology in which a split radio access network (RAN) is configured more flexibly and resiliently can be considered to compensate for incomplete areas of network coverage.

[0218] For this purpose, various nodes such as IAB nodes, relays, and RF repeaters as in the example of Fig. 13 may be applied, and NTN (non-terrestrial network) may be integrated.

[0219] For example, an IAB node may correspond to a node providing wireless backhaul. For example, a relay may refer to any intermediate point, or in the case of a sidelink relay where a terminal functions as a relay, it may collectively refer to a terminal-to-network (U2N) relay and a terminal-to-terminal (U2U) relay.

[0220] For example, an RF repeater may be a node that simply performs the function of signal amplification and forwarding, or, in the case of a network-controlled repeater (NCR), it may not only amplify and forward signals, but also adjust its transmit and receive settings based on information provided by the network.

[0221] For example, NTN nodes could be satellites or aircraft that provide NTN coverage that terrestrial networks struggle to provide. Beyond these examples, various intermediate points can be introduced to improve the network topology.

[0222] In Figure 13, a split RAN can support partitioning a base station into a centralized unit (CU) and one or more distributed units (DUs). The CU and DU can correspond to logical units. The CU can be further partitioned into a control plane (CP) portion and one or more user plane (UP) portions. Since a failure in the CU-CP affects not only the CU-UP but also the DUs, various intermediate points can be introduced to compensate for this.

[0223] An intermediate point may correspond to a terminal or a base station, depending on its relationship to other nodes. For example, an IAB node may include a mobile-termination (MT) portion and a unit (DU). The MT may connect the IAB node to a donor node. The unit (DU) of an IAB node may serve other terminals or connect to other IAB nodes to provide multi-hop wireless backhaul to the terminal. In other words, an IAB node may correspond to a base station in its relationship to a user-side node, and to a terminal in its relationship to a network-side node.

[0224] Hereinafter, in some examples, the description of a terminal can be equally applied not only to a user-side end point, but also to an intermediate point corresponding to a terminal in a relative relationship with a network-side end point. Similarly, in some examples of this specification, the description of a base station can be equally applied not only to a network-side end point, but also to an intermediate point corresponding to a base station in a relative relationship with a user-side end point. However, in most cases where there is no additional description of the operations of three or more entities, the communication entities in this specification can be briefly described as terminals and / or base stations (or first nodes and / or second nodes). Here, the terms terminal and / or base stations (or first nodes and / or second nodes) can be interpreted to include / replace any end point or any intermediate point depending on the relationship with other nodes.

[0225] In some examples of the present specification below, for the sake of simplicity, the subjects of the operations may be referred to as base stations and / or terminals (or first nodes and / or second nodes). In addition, the terms base stations and / or terminals (or first nodes and / or second nodes) may also be interpreted / replaced as in the following examples: For example, the base stations (or first nodes) and terminals (or second nodes) may respectively correspond to the first endpoint and the second endpoint; may respectively correspond to the endpoint and the intermediate point; may respectively correspond to the intermediate point and the endpoint; or may respectively correspond to the first intermediate point and the second intermediate point.

[0226] In this specification, there may be zero or more intermediate points between the base station and the terminal. If intermediate points exist, they may be IAB nodes, relays, RF repeaters, NTN (non-terrestrial network) nodes, or nodes supporting other functions. An intermediate point may be a node with a fixed location or a node with an unfixed location.

[0227] For IoT devices with relatively low mobility and similar traffic characteristics, the overhead of control information required to schedule traffic can be significant relative to the amount of traffic transmitted. Furthermore, the channel environment or traffic used to transmit and receive traffic can remain unchanged for relatively long periods of time. Furthermore, traffic transmission and reception patterns between devices can be similar.

[0228] In this environment, scheduling data independently for each terminal can be inefficient.

[0229] Therefore, the present disclosure proposes an operation that simultaneously directs data scheduling for multiple terminals through a single control signal. For example, for devices located within the same vehicle, the channel conditions between the devices can be maintained similarly. In such cases, independent data transmission and reception can be achieved by sharing some scheduling information while independently directing the remaining scheduling information between devices.

[0230] Below, a specific method for indicating scheduling information of independent data for multiple terminals through a single DCI is described.

[0231] This behavior can be expected to reduce DCI overhead. For example, by transmitting 1 DCI instead of N DCIs when scheduling N data (where N is a natural number greater than or equal to 2), the total number of DCIs transmitted in the search space can be reduced. Furthermore, when scheduling N data, the total required amount of DCIs can be reduced by sharing some DCI fields. Therefore, the amount of resources used to transmit DCIs in the system can be reduced, and the amount of data that can be scheduled using the same resources can also be increased.

[0232] Additionally, since the number of DCIs required to schedule the same amount of data can be reduced, the number of PDCCH candidates that the terminal must monitor can be reduced. This is expected to have the effect of reducing PDCCH BD (blind decoding) overhead.

[0233] The present disclosure proposes an operation for scheduling multiple terminal-specific data to be transmitted to different terminals via a single DCI.

[0234] Hereinafter, the operation of scheduling multiple terminal-specific data to be transmitted to different terminals through a single DCI is called multi-terminal scheduling.

[0235] In the present disclosure, the terminal can operate as follows.

[0236] 1. A terminal receives information about a group of terminals that can receive data scheduling via the same DCI from a base station. A single terminal can receive configuration information for one or more terminal groups.

[0237] 2. The terminal can receive information from the base station about the terminal group(s) that performs monitoring of DCI for multi-terminal scheduling among multiple terminal groups.

[0238] 3. The terminal monitors the PDCCH indicating multi-terminal scheduling information based on terminal group configuration information for the instructed terminal group(s).

[0239] 4. The terminal receives DCI through PDCCH and determines whether to schedule the data to be transmitted or received.

[0240] 5. When data to be transmitted and received by the terminal is scheduled, the terminal obtains scheduling information for the physical channel to be transmitted and received through DCI.

[0241] 6. The terminal transmits and receives scheduled data by transmitting and receiving physical channels based on the acquired scheduling information.

[0242] <PDCCH 모니터링을 위한 단말 그룹핑>

[0243] The present disclosure proposes an operation in which terminals belonging to the same terminal group are scheduled on a physical channel (e.g., PDSCH / PUSCH) for transmitting data through the same DCI.

[0244] The terminal group to which a terminal belongs can vary depending on various terminal situations and environments. The composition of terminals within a terminal group suitable for scheduling data through the same DCI can vary due to factors such as terminal distribution, traffic changes, and channel environment changes.

[0245] Considering various characteristics, a single terminal can belong to one or more terminal groups. For example, since different terminal groups may be appropriate for different situations, multiple terminal groups can be established for each situation.

[0246] In this case, information for DCI monitoring can be independently configured for each terminal group. A terminal can perform DCI monitoring for multiple terminal groups and, by receiving DCI, transmit and receive data scheduled for itself.

[0247] When a terminal's group information changes, the terminal group information may be reset. To reduce the burden of resetting terminal group information each time the terminal's group information changes, a single terminal may belong to one or more terminal groups, and activation / deactivation information may be set / instructed for each terminal group. The terminal may perform DCI monitoring for terminal groups for which activation has been instructed, and receive DCI to transmit and receive data scheduled for itself.

[0248] In this disclosure, scheduling multiple terminal-specific data to be transmitted to different terminals through a single DCI is called multi-terminal scheduling.

[0249] A. DCI monitoring by terminal group and terminal group

[0250] Considering the above-described operation, the present disclosure proposes that a terminal set terminal group information and set and / or determine DCI monitoring-related information according to the terminal group as follows.

[0251] A terminal may receive information about one or more terminal groups from the base station to which it belongs for multi-terminal scheduling purposes for terminals within the same terminal group. In this case, scheduling information for data scheduled for terminals within the same terminal group may be indicated via the same DCI.

[0252] For example, multi-terminal scheduling operations, in which terminals with similar received SINRs, such as terminals located within the same vehicle or IoT terminals in adjacent areas, receive scheduling information together via a single DCI, may be suitable. In such cases, the same MCS can be applied to the terminals receiving scheduling information via multi-terminal scheduling for transmitting and receiving physical channels. However, since the transmission resources of the physical channels are designated differently, the terminals may transmit and receive data via different physical channels.

[0253] At this time, all or part of the following information may be set / determined for each terminal group to which the terminal belongs. In the present disclosure, it is proposed that the terminal receive the following setting information for each terminal group from the base station for multi-terminal scheduling operations.

[0254] This configuration information can be set from the base station to the terminal through signaling such as RRC.

[0255] 1) Terminal group index

[0256] Terminal group index information can be set to distinguish terminal groups.

[0257] 2) Terminal index

[0258] A virtual ID / logical ID value can be set to be used when distinguishing and indicating a terminal among the terminals included in the terminal group.

[0259] For example, if the number of terminals included in a terminal group is equal to N, a value from 0 to N-1 can be used as the terminal index. The terminal's C-RNTI value can be used to distinguish the terminal, but the C-RNTI has the disadvantage of requiring too large a bit size to represent it.

[0260] 3) The number of UEs

[0261] Information about the number of terminals in a terminal group can be set. For multi-terminal scheduling, information about terminals scheduled for data within the terminal group can be indicated. For example, such indications can be provided via DCI for multi-terminal scheduling. In this case, the size of the DCI field for indicating information about terminals scheduled for data can be determined based on the number of terminals included in the terminal group. In this case, the terminal needs to know information about the number of terminals included in the terminal group to determine the DCI field size.

[0262] The above information (the number of terminals) may be replaced by the size of a DCI field for indicating information about the terminal(s) receiving data scheduling within the DCI indicating multi-terminal scheduling information. The size of this DCI field may be determined based on the number of terminals present within the terminal group.

[0263] For example, the number of terminals in a terminal group is N UE,group When the size of the DCI field is N UE,group It may be the same as. In this case, information on the terminal receiving the scheduling of data in a bitmap manner may be indicated.

[0264] Or, for example, the number of terminals in a terminal group is N UE,group When the size of the DCI field is 'ceil(log2(N UE,group ))' or 'ceil(log2(N UE,group ))' may be a multiple of '. In this case, the index(es) of information of the terminal receiving data scheduling through this DCI field may be indicated.

[0265] 4) The maximum number of scheduled data per DCI

[0266] Information about the maximum number of data (e.g., the number of PDSCHs) that can be scheduled through a single multi-terminal scheduling instruction may be indicated.

[0267] In multi-terminal scheduling, when scheduling multiple data items to different terminals via a single DCI, some scheduling information may indicate different information for each scheduled data item. The size or number of DCI fields indicating such scheduling information may be determined based on the maximum number of data items that can be scheduled via a single DCI. To determine the size or number of some DCI fields, a terminal needs to know information regarding the maximum number of data items that can be scheduled via a single multi-terminal scheduling instruction.

[0268] 5) Multiplexing scheme

[0269] Information about a multiplexing scheme between multiple physical channels (e.g., PDSCH) scheduled via a multi-terminal scheduling instruction may be indicated.

[0270] Multiple physical channels scheduled via multi-terminal scheduling instructions can be transmitted together using various multiplexing methods such as TDM, FDM, and / or SDM. In this case, the configuration of information required to indicate scheduling information for the multiple physical channels may vary depending on which multiplexing method is used. For example, when multiple physical channels are transmitted using FDM, the same time-domain resource information is applied to the multiple physical channels, but frequency-domain resource information can be independently indicated and applied to each physical channel. When multiple physical channels are transmitted using TDM, the same frequency-domain resource information is applied to the multiple physical channels, but time-domain resource information can be independently indicated and applied to each physical channel.

[0271] Therefore, when a specific multiplexing method is applied to multiple physical channels scheduled through a multi-terminal scheduling instruction, and this multiplexing method may differ depending on a terminal group, the terminal needs to know this information in order to determine the multiplexing method among the multiple physical channels scheduled through the multi-terminal scheduling instruction and to determine the configuration of the scheduling information indicated therefrom (e.g., the configuration of DCI fields).

[0272] 6) DCI format

[0273] DCI format information for transmitting DCI for multi-terminal scheduling for each terminal group may be indicated for each terminal group. In this case, the terminal may determine that the DCI for performing multi-terminal scheduling is being transmitted using the DCI format corresponding to the terminal group and may perform DCI monitoring.

[0274] This DCI format information is not explicitly set, and can be determined based on the multiplexing technique applied to the terminal group. In this case, if the terminal receives multiplexing technique information corresponding to the terminal group, the terminal determines that DCI for performing multi-terminal scheduling using the DCI format corresponding to the multiplexing technique is being transmitted, and can perform DCI monitoring.

[0275] 7) RNTI

[0276] An RNTI value can be set for each terminal group. In this case, when a terminal monitors DCI for multi-terminal scheduling for a specific terminal group, it can assume that the DCI is transmitted CRC-scrambled with the RNTI corresponding to the terminal group.

[0277] This RNTI information can be used as a replacement for the terminal group index. Furthermore, the RNTI value can be set differently depending on the multiplexing scheme applied to multiple physical channels scheduled via the multi-terminal scheduling instruction. In this case, when monitoring DCI for multi-terminal scheduling for a specific multiplexing scheme, the terminal can assume that the DCI is transmitted CRC-scrambled with an RNTI corresponding to the multiplexing scheme. This RNTI information can be used as a replacement for information about the applied multiplexing scheme.

[0278] 8) Search space

[0279] Information regarding the search space for monitoring DCIs indicating multi-terminal scheduling may be provided. Depending on the terminal group, the traffic characteristics of the terminals within that terminal group may vary. For example, the frequency of traffic generation may vary depending on the terminal group. Taking this into account, the search space information for monitoring DCIs indicating multi-terminal scheduling may vary depending on the terminal group.

[0280] And / or, depending on the terminal group, the appropriate beam direction for transmitting PDCCHs to terminals belonging to that terminal group may vary. Considering this, the beam direction or coreset information applied by the terminal to monitor DCI indicating multi-terminal scheduling may vary depending on the terminal group. Considering this, search space-related information applicable to each terminal group may be applied differently.

[0281] Information about this search space may be specifically as follows:

[0282] i) Search space ID. A search space ID is indicated according to a terminal group, so that the terminal can monitor DCI for multi-terminal scheduling for the terminal group in the search space corresponding to the search space ID.

[0283] ii) Period and / or offset. Information corresponding to the period and / or offset may be indicated depending on the terminal group. When monitoring DCI for multi-terminal scheduling for a terminal group in the search space, the terminal may apply the corresponding period and / or offset information to determine the monitoring interval of the indicated search space.

[0284] For example, in the case of periodic information, it can be determined as a value n times and / or 1 / n times the period set when setting up the search space. In such a case, a value corresponding to n can be indicated. If such information is not available, the period and / or offset information set when setting up the search space can be applied.

[0285] iii) Coreset ID. Coreset information (e.g., coreset ID) associated / related to the search space may be indicated depending on the terminal group. When monitoring DCI for multi-terminal scheduling for a specific terminal group in the search space, the terminal may perform DCI monitoring in the search space by applying the indicated coreset information.

[0286] iv) TCI State ID. Information (e.g., TCI State ID) regarding the beam direction applied to monitor DCI in the search space may be indicated according to the terminal group. This information may refer to TCI State ID information applied to the core set associated / related to the search space. When monitoring DCI for multi-terminal scheduling for a specific terminal group in the search space, the terminal may perform DCI monitoring in the search space by applying information regarding the indicated beam direction.

[0287] B. Activate / deactivate terminal groups

[0288] For multi-terminal scheduling at the terminal group level, a terminal can receive information about one or more terminal groups to which it belongs from a base station. Scheduling information for physical channels (e.g., PDSCHs) scheduled to terminals belonging to the same terminal group can be indicated through the same DCI.

[0289] The terminal can perform DCI monitoring for some or all of the configured terminal groups.

[0290] The terminal group in which the terminal performs DCI monitoring can be set / determined as follows.

[0291] Method 1.

[0292] A terminal may be instructed by a base station to provide information about the terminal group(s) for which it performs DCI monitoring, among the terminal groups configured by the base station. In this case, the terminal may be instructed to perform DCI monitoring for only one terminal group at a time. Alternatively, the terminal may be instructed to perform DCI monitoring for multiple terminal groups at once.

[0293] Method 1-1.

[0294] This instruction information can be transmitted from the base station to the terminal via MAC-CE signaling. This can indicate information about the terminal group(s) that are activated to perform DCI monitoring. Alternatively, the activation / deactivation of each terminal group can be indicated.

[0295] Method 1-2.

[0296] This instruction information can be transmitted from the base station to the terminal via DCI signaling. For example, the terminal can receive instruction information for multi-terminal scheduling via a two-stage DCI consisting of a first DCI and a second DCI.

[0297] In this case, the terminal may be instructed via the first DCI about the terminal group(s) for which multi-terminal scheduling is performed. Scheduling information for multiple data items scheduled for the terminals included in the terminal group instructed via the first DCI may be instructed via the second DCI.

[0298] For the first DCI, it can be monitored / transmitted with a longer cycle than the second DCI.

[0299] A terminal that has been instructed with such terminal group information can monitor a second DCI that performs multi-terminal scheduling for the terminal group and thereby be instructed with multi-terminal scheduling information for the terminal group.

[0300] For the purpose of indicating the terminal group(s) for which these terminals perform DCI monitoring, the ID of the terminal group may be indicated. Alternatively, an RNTI value applicable to each terminal group may be set for each terminal group and this RNTI value may be indicated.

[0301] Method 2.

[0302] The terminal monitors DCI for multi-terminal scheduling for the terminal group(s) configured by the base station without any additional instructions. If the terminal receives multiple terminal groups configured by the base station, it monitors DCI for multi-terminal scheduling for the multiple terminal groups.

[0303] The terminal can perform the following actions for the terminal group(s) performing DCI monitoring through the above instructions / judgments.

[0304] The terminal may determine that a DCI for performing multi-terminal scheduling for the terminal group is transmitted and may perform monitoring of the DCI.

[0305] If a terminal has been set with search space information corresponding to a terminal group, the terminal can monitor the DCI performing multi-terminal scheduling for the terminal group in the search space. Alternatively, if search space-related configuration information (e.g., period and / or offset, coreset ID, TCI state ID) corresponding to a terminal group has been set, the terminal can monitor the DCI performing multi-terminal scheduling for the terminal group by applying the configuration information.

[0306] A terminal can assume that DCI for a specific terminal group is transmitted CRC-scrambled with an RNTI corresponding to the terminal group (set for the terminal group).

[0307] When the terminal receives multiplexing technique information corresponding to the terminal group, the terminal can determine that multiple physical channels (e.g., PDSCH) are multiplexed and transmitted by applying the multiplexing technique.

[0308] For example, when TDM is configured, the terminal can determine that multiple physical channels are transmitted using TDM using different time resources. In this case, the terminal can determine that independent time resources are indicated for the multiple physical channels through DCI. To this end, independent time resource information is indicated for each physical channel through DCI, and corresponding time resource information can be applied to each physical channel. In this case, the terminal can determine that frequency resources that are applied equally to the multiple physical channels are indicated through DCI. To this end, a single frequency resource information can be indicated through DCI, and applied equally to the multiple physical channels.

[0309] As another example, if FDM is configured, the terminal may determine that multiple physical channels are transmitted in FDM using different frequency resources. In this case, the terminal may determine that independent frequency resources for the multiple physical channels are indicated through DCI. To this end, independent frequency resource information is indicated for each physical channel through DCI, so that corresponding frequency resource information can be applied to each physical channel. In this case, the terminal may determine that time resources that are applied equally to the multiple physical channels are indicated through DCI. To this end, a single time resource information is indicated through DCI, and can be applied equally to the multiple physical channels.

[0310] As another example, if SDM is configured, the terminal may determine that multiple physical channels are transmitted using SDM using different spatial resources. In this case, the multiple physical channels may be transmitted through different layer(s). The terminal may determine that independent layer information for the multiple physical channels is indicated through DCI. In this case, independent layer resource information is indicated for each physical channel through DCI, so that each physical channel can be transmitted through the corresponding layer.

[0311] In this case, the terminal can determine that the time resource applied equally to multiple physical channels is indicated via DCI. To achieve this, a single time resource information is indicated via DCI and can be applied equally to multiple physical channels.

[0312] In this case, the terminal can determine that frequency resources that are equally applicable to multiple physical channels are indicated via DCI. To achieve this, a single frequency resource is indicated via DCI and can be applied equally to multiple physical channels.

[0313] If the terminal receives DCI format information corresponding to the terminal group, the terminal determines that DCI for performing multi-terminal scheduling using the DCI format is transmitted and can perform DCI monitoring. This DCI format information is not explicitly set and can be determined based on the multiplexing technique applied to the terminal group. In this case, if the terminal receives multiplexing technique information corresponding to the terminal group, the terminal determines that DCI for performing multi-terminal scheduling using the DCI format corresponding to the multiplexing technique is transmitted and can perform DCI monitoring.

[0314] <Multi-terminal data scheduling instructions>

[0315] Below, we propose an operation in which terminals belonging to the same terminal group schedule data (e.g., PDSCH / PUSCH) through the same DCI.

[0316] When scheduling information for multiple physical channels (e.g., PDSCH / PUSCH) for different terminals is indicated through a single DCI, only some of the physical channels for the terminals belonging to the terminal group may be scheduled. This is because data scheduled for all terminals within the terminal group may not always exist. Alternatively, the maximum number of physical channels that can be scheduled through a single DCI may be less than the number of terminals within the terminal group, taking into account factors such as DCI overhead.

[0317] In such a case, the terminal must be able to determine whether the physical channel it must transmit and receive is scheduled through DCI and which of the multiple physical channels scheduled through DCI is the physical channel scheduled for it.

[0318] Considering this, the present disclosure proposes a method for a terminal to determine which physical channel is scheduled for a terminal through DCI for multi-terminal scheduling, i.e., a method for a terminal to determine whether a physical channel it is to transmit and receive is scheduled. Furthermore, a method for determining scheduling information for a physical channel scheduled for the terminal is proposed.

[0319] A. Configuration of DCI fields

[0320] DCI for multi-terminal scheduling may consist of the following fields:

[0321] i) Terminal information field containing ‘scheduled terminal information’ indicating the terminal(s) to which data is scheduled.

[0322] ii) Fields containing ‘shared information for PXSCHs’, which is scheduling information commonly applied to multiple physical channels being scheduled.

[0323] iii) Fields containing 'individual information for PXSCHs', which is scheduling information that is independently applied to multiple physical channels being scheduled.

[0324] Figure 14 shows an example of a DCI format for multi-terminal scheduling.

[0325] Referring to FIG. 14, DCI information for multi-terminal scheduling can be indicated through a single DCI. In this case, 'scheduled terminal information' can be indicated through the same DCI as scheduling information of physical channel(s) (e.g., 'shared information for PXSCHs' and 'individual information for PXSCHs').

[0326] 'Scheduled terminal information' may be included in a terminal information field indicating a specific terminal among multiple terminals to which multi-terminal scheduling is applied.

[0327] If the scheduling information commonly applied to the above multiple terminals is referred to as 'shared information for PXSCHs', the 'shared information for PXSCHs' may be included in DCI field 1 to DCI field K. In this case, DCI field 1 to DCI field K may be referred to as shared information fields.

[0328] If the scheduling information independently applied to the above multiple terminals is referred to as 'individual information for PXSCHs', the 'individual information for PXSCHs' may be included in DCI field K+1 to DCI field K+N. In this case, DCI field K+1 to DCI field K+N may be referred to as individual information fields.

[0329] In some embodiments, DCI information for multi-terminal scheduling may be indicated via two DCIs, each consisting of a first DCI and a second DCI, using a two-stage DCI. In this case, information about terminal(s) to be scheduled for data may be indicated via the first DCI, and scheduling information about the physical channel(s) to be transmitted may be indicated via the second DCI. That is, 'scheduled terminal information' information may be indicated via the first DCI, and scheduling information of the physical channel(s) (e.g., 'shared information for PXSCHs' and 'individual information for PXSCHs') may be indicated via the second DCI.

[0330] In this disclosure, the maximum number of physical channels that can be indicated through one DCI is N. D,max , and the number of terminals included in the terminal group is N. UE,group At this time, the maximum number of physical channels that can be indicated through one DCI (e.g., N D,max ) is the number of terminals within the terminal group (e.g., N UE,group ) may be equal to or less than the maximum number of physical channels that can be directed through a single DCI (e.g., N D,max) is the number of terminals within the terminal group (e.g., N UE,group ) can always be the same.

[0331] At this time, the number of physical channels actually scheduled through one DCI is N. D When N D N is the maximum number of physical channels that can be directed through one DCI. D,max It can be equal to or less than .

[0332] At this time, the DCI field(s) containing the 'individual information for PXSCHs' information is the maximum number of physical channels that can be indicated through one DCI (e.g., N D,max ) may affect / determine the field size or the number of fields (and thus the overall DCI payload size).

[0333] For example, the size of the DCI field indicating specific information is N D,max may be a multiple of the value of and / or the number of DCI fields indicating specific information is N D,max There can be as many as dogs.

[0334] Alternatively, if DCI information for multi-terminal scheduling is indicated through two DCIs consisting of a first DCI and a second DCI using a two-stage DCI and information about terminal(s) that are scheduled to receive data is indicated through the first DCI, and if there is 'individual information for PXSCHs' transmitted through the first DCI, the size of the DCI field indicating the information is the maximum number of physical channels that can be indicated through one DCI (e.g., N D,max) may be influenced / determined by the field size or the number of fields (and the total (first) DCI payload size based thereon). If there is 'individual information for PXSCHs' transmitted via the second DCI, the size of the DCI field indicating the information is the number of actual physical channels indicated by one (the first) DCI (e.g., N D ) may affect / determine the field size or the number of fields (and thus the overall (second) DCI payload size).

[0335] B. Method of determining scheduling information

[0336] A method for indicating a scheduled terminal through DCI for multi-terminal scheduling and a method for determining scheduling information of a physical channel may be specifically as follows.

[0337] As follows, the terminal can determine the scheduling information of the physical channel it must transmit and receive and perform transmission and reception of the scheduled physical channel.

[0338] Method 1.

[0339] A terminal determines whether the physical channel it is to transmit and receive is scheduled. A terminal with a scheduled physical channel for transmission and reception is referred to as a scheduled terminal.

[0340] In this case, N within the terminal group UE,group N of the terminals D (<=N D,max , where A<=B indicates that B is greater than or equal to A) terminals can be designated / judged as scheduled terminals. The method for judging whether a terminal itself is a scheduled terminal can be applied more specifically to the contents of B.1 below.

[0341] For specific scheduling information that is applied independently to each physical channel,

[0342] Method 1-1. The u-th scheduled terminal determines the u-th scheduling information as scheduling information applicable to the physical channel on which it must transmit and receive.

[0343] Method 1-2. The u-th scheduled terminal determines the u-th valid scheduling information as scheduling information applicable to the physical channel on which it must transmit and receive.

[0344] The method by which the terminal determines the uth valid scheduling information can be applied more specifically to the contents of B.2 below.

[0345] When a terminal itself is designated / determined to be a scheduled terminal, it can perform transmission and reception on the scheduled physical channel by applying scheduling information applicable to the physical channel on which it must transmit and receive.

[0346] Method 2.

[0347] N within the terminal group UE,group Among the terminals, the u-th terminal (e.g., the terminal having the terminal index as u) determines the u-th scheduling information as scheduling information applicable to the physical channel on which it must transmit and receive, with respect to specific scheduling information independently applied to each physical channel.

[0348] At this time, the terminal determines whether the scheduling information applied to the physical channel it is to transmit and receive is valid. The method by which the terminal determines the validity of the scheduling information can be applied as described in B.2 below.

[0349] If the terminal determines that the scheduling information applied to the physical channel on which it must transmit and receive is valid scheduling information, it can perform transmission and reception on the scheduled physical channel by applying the scheduling information.

[0350] In the above methods 1 and 2, the u-th scheduling information may more specifically mean the following.

[0351] If independent time domain resource information is indicated for each scheduled physical channel, i) N D,max When time resource information for multiple physical channels is indicated through fields indicating time domain resource information, the information indicated through the field indicating the u-th time domain resource information can be determined as the u-th time resource scheduling information.

[0352] ii) When time resource information for multiple physical channels is indicated through a field indicating one time domain resource information, N is indicated through the time domain resource field. D Time resource information for the physical channels of the u-th can be indicated. In this case, the u-th time domain resource information can be determined as the u-th time resource scheduling information.

[0353] Time domain resource information may include, for example, information about the slot location in which a physical channel is transmitted, and / or information about the location of symbol(s) in which a physical channel is transmitted within a slot in which a physical channel is transmitted.

[0354] If independent frequency domain resource information is indicated for each scheduled physical channel, i) N D,max When frequency resource information for multiple physical channels is indicated through fields indicating frequency domain resource information, the information indicated through the field indicating the u-th frequency domain resource information can be determined as the u-th frequency resource scheduling information.

[0355] ii) When frequency resource information for multiple physical channels is indicated through a field indicating one frequency domain resource information, N is indicated through the frequency domain resource field. D Frequency resource information for the u physical channels may be indicated. In this case, the u-th frequency domain resource information may be determined as the u-th frequency resource scheduling information.

[0356] Frequency domain resource information may refer to, for example, information about the RB / RB group location where a physical channel is transmitted. This information may be indicated through a bitmap or RIV.

[0357] B.1. Method for determining scheduled terminals

[0358] Below is the N within the terminal group UE,group N terminals among which transmission and reception of physical channels are indicated D This section describes how scheduled terminals are indicated. This allows each terminal to determine whether it is a scheduled terminal (i.e., whether the physical channel on which it is to transmit and receive is scheduled).

[0359] Method 1.

[0360] A terminal information field exists in the DCI to indicate information about a scheduled terminal, and information about a terminal receiving a physical channel schedule can be indicated through this field. This field may refer to the 'scheduled terminal information' information of Section A above.

[0361] At this time, a bitmap value can be indicated through the terminal information field, and this bitmap is N UE,group It can be composed of bits. For a specific terminal, when the terminal index of the terminal within the terminal group is u, the uth bit of the bitmap can indicate whether / information about the scheduling of the physical channel transmitted and received by the terminal. For example, a value of the bitmap of 1 can indicate that the physical channel is scheduled, and a value of 0 can indicate that the physical channel is not scheduled.

[0362] At this time, the terminal can determine that it has been designated as a scheduled terminal if the value of the bit indicating its scheduled terminal information in the bitmap is 1.

[0363] At this time, N UE,group Among the terminals, the terminal designated as the scheduled terminal is ND When a dog exists, the terminal that is indicated as 1 in the bit order of the bitmap (i.e., indicated as the u-th scheduled terminal) is called the u-th scheduled terminal.

[0364] Method 2.

[0365] N that schedules data through the terminal information field(s) to indicate information about the scheduled terminal within the DCI D The terminal index information of the dog can be indicated.

[0366] Method 2-1. There is one such terminal information field, and N is assigned to that field. D Terminal index information of a number of terminals can be indicated. In this case, the size of the terminal information field is the maximum number of physical channels that can be indicated through one DCI (e.g., N D,max ) can be a multiple of . More specifically, the size of the terminal information field is 'ceil(log2(N UE,group )) x N D,max ' can be the same.

[0367] N through terminal information field(s) D (<=N D,max ) terminals are indicated, some bits in the DCI field (e.g., 'ceil(log2(N)' from the MSB (Most Significant bit) in the DCI field) UE,group )) x N D ' bits or LSB (Least Significant bit) from 'ceil(log2(N)) x N D ' bits) can be used to indicate terminal information.

[0368] At this time, the terminal can determine that it has been designated as a scheduled terminal if its terminal index is designated.

[0369] At this time, the scheduled terminal indicated as the uth terminal in the field is called the uth scheduled terminal.

[0370] Method 2-2. These terminal information fields are N D,max Since there is a dog, one terminal information can be indicated through one field. At this time, the size of each field is 'ceil(log2(N UE,group ))' can be the same.

[0371] N through terminal information field(s) D (<=N D,max ) terminals are indicated, N D Only the DCI fields of the terminal can be used to indicate terminal information. For example, a terminal may have N D,max N from the front of the terminal information fields D The DCI fields of the dog are N D It can be judged that it is used to indicate the terminal information of the dog.

[0372] At this time, the terminal can determine that it has been designated as a scheduled terminal if its terminal index is indicated through a specific terminal information field.

[0373] At this time, the terminal indicated as the scheduled terminal through the terminal information fields is N D When a dog exists, the terminal indicated as the uth scheduled terminal in the order of the DCI fields is called the uth scheduled terminal. Alternatively, the scheduled terminal indicated through the uth terminal information field is called the uth scheduled terminal.

[0374] At this time, N D (<=N D,max ) physical channels are scheduled, N D It must be able to determine the scheduled terminal information of the dog. The terminal is N D Knowing the value of allows one to determine which bits within the terminal information field are used to indicate actual scheduled terminal information or how many terminal information fields are used to indicate scheduled terminal information.

[0375] Considering this, the terminal is N DThe following methods can be used to determine the value of .

[0376] Option 1. Number of physical channels to be scheduled N D Information corresponding to may be included and indicated within the DCI for multi-terminal scheduling.

[0377] Option 2. If a specific value is indicated by the terminal index, this may mean that there is no terminal being indicated. For example, if 0 is indicated by the terminal index, this may mean that there is no terminal being indicated (no valid terminal index is indicated). Or, for example, the number of terminals in the terminal group N is indicated by the terminal index. UE,group If a value greater than or equal to 0 is indicated, it may mean that there is no terminal being indicated (no valid terminal index is indicated). Based on this, the terminal may count the number of terminals indicated with a valid terminal index as N. D can be judged by

[0378] Option 3. Independent scheduling information is indicated for each physical channel to be scheduled, and the validity of the scheduling information can be determined through this. The number of scheduling information for which information is determined to be valid is N. D It can be judged as follows. The method by which the terminal judges the validity of scheduling information can be applied to the contents of B.2 below.

[0379] B.2. How to determine the validity of scheduling information

[0380] Below, a method for a terminal to determine the validity of scheduling information and a method for determining the uth valid scheduling information among multiple scheduling information are described.

[0381] N through DCI D,max When scheduling information for physical channels N is indicated, the number of physical channels actually scheduled is N. D is N D,max It can be equal to or less than N. That is, N D,maxAmong the scheduling information (e.g., time domain resource information or frequency domain resource information) for the physical channels, the actual N D Only the dog's information may be valid.

[0382] Specifically, the following methods may be used by the terminal to determine the validity of scheduling information.

[0383] When independent scheduling information is indicated for each scheduled physical channel, if valid information is not indicated for a specific physical channel, the scheduling information for that physical channel can be determined to be invalid.

[0384] For example, if independent time domain resource information is indicated for each scheduled physical channel, the validity of the indicated scheduling information can be determined through the field(s) indicating the time domain resource information.

[0385] N D,max Time resource information for multiple physical channels can be indicated through fields indicating time domain resource information. In this case, time resource information for one physical channel can be indicated through one field.

[0386] At this time, if a specific value is indicated through specific time resource information or if the values ​​of some parameter(s) among the parameters indicated through time domain resource indication are a specific value or a combination of specific values, the time resource information may be determined to be invalid.

[0387] For example, if all '1' values ​​are indicated through time domain resource instructions, the time resource information can be judged to be invalid.

[0388] Alternatively, for example, a specific value indicated through a time domain resource indication may be defined / set to indicate 'invalid', and if that value is indicated, the time resource information may be judged to be invalid.

[0389] Or, for example, if all SLIV values ​​of a time resource are indicated as '1', the terminal may determine that the time resource information is invalid.

[0390] Or, for example, if the number of symbols constituting the time resource is indicated as 0, the terminal may determine that the time resource information is invalid.

[0391] In this case, the terminal is judged to be valid (not invalid) N D (<=N D,max ) When the time resource information is listed in the order of the indicated DCI fields, the u-th time domain resource information can be determined as the u-th valid time domain resource information.

[0392] Time resource information for multiple physical channels can be indicated through fields indicating one time domain resource information. In this case, N is indicated through the time domain resource field. D (<=N D,max ) time resource information can be indicated.

[0393] In this case, the terminal is 0 to N D-1 The second time domain resource information can be judged to be valid.

[0394] In this case, the terminal is N D For the time domain resource information of the dog, the u-th time domain resource information can be determined as the u-th valid time domain resource information in order.

[0395] Or, for example, if independent frequency domain resource information is indicated for each physical channel to be scheduled, the validity of the indicated scheduling information can be determined through the field(s) indicating the frequency domain resource information.

[0396] N D,max Frequency resource information for multiple physical channels can be indicated through fields indicating frequency domain resource information. In this case, frequency resource information for one physical channel can be indicated through one field.

[0397] At this time, if a specific value is indicated through specific frequency resource information or if the values ​​of some parameter(s) among the parameters indicated through frequency domain resource indication are a specific value or a combination of specific values, the frequency resource information may be determined to be invalid.

[0398] For example, if frequency resources are indicated in the form of a bitmap per RB or RB group, such as in RA (resource allocation) type 0 of the NR system, and if all bitmap values ​​are indicated as '0', the bitmap resource information can be determined to be invalid.

[0399] Or, for example, if the frequency resource is indicated in the form of RIV per RB or RB group, such as in RA type 1 of the NR system, and if all RIV values ​​are indicated as '1', the bitmap resource information may be judged to be invalid.

[0400] In this case, the terminal is judged to be valid (not invalid) N D (<=N D,max ) When the frequency resource information is listed in the order of the indicated DCI fields, the u-th frequency domain resource information can be determined as the u-th valid frequency domain resource information.

[0401] Frequency resource information for multiple physical channels can be indicated through fields indicating one frequency domain resource information. In this case, N through the frequency domain resource field D,max The frequency resource information of the dog can be indicated.

[0402] At this time, if a specific value is indicated by specific frequency resource information, the frequency resource information may be judged to be invalid.

[0403] For example, if frequency resources are indicated in the form of a bitmap in units of RB or RB groups, such as in RA type 0 of the NR system, and if all bitmap values ​​are indicated as '0', the bitmap resource information may be judged to be invalid.

[0404] Or, for example, if the frequency resource is indicated in the form of RIV per RB or RB group, such as in RA type 1 of the NR system, and if all RIV values ​​are indicated as '1', the bitmap resource information may be judged to be invalid.

[0405] In this case, the terminal determines that N is valid (not invalid). D (<=N D,max ) When frequency resource information is listed in order, the u-th frequency domain resource information can be determined as the u-th valid frequency domain resource information.

[0406] Figure 15 illustrates the operation method of the terminal.

[0407] Referring to FIG. 15, a terminal receives group information about a terminal group related to multi-UE scheduling from a base station, and the multi-UE scheduling is a scheduling method that performs scheduling for multiple terminals through the same DCI format (S151).

[0408] The group information may include information about a search space for detecting a specific DCI format. The specific DCI format may include scheduling information about physical downlink shared channels (PDSCHs) or physical uplink shared channels (PUSCHs) for the plurality of terminals.

[0409] The group information may include, for example, at least one of i) an identifier for the search space, ii) a period and offset related to the search space, iii) an ID of a control resource set (CORESET) related to the search space, or iv) a Transmission Configuration Indicator (TCI) state ID applied to the CORESET.

[0410] According to an embodiment, the group information may further include at least one of: i) a terminal group index for distinguishing a terminal group, ii) a terminal index for distinguishing a specific terminal within the terminal group, iii) information on the number of terminals within the terminal group, iv) a maximum number of data that can be scheduled in one DCI format, v) a multiplexing scheme between a plurality of physical channels scheduled by multi-terminal scheduling, vi) a DCI format for the terminal group, or vii) an RNTI (Radio Network Temporary Identifier) ​​for the terminal group. For example, let the RNTI for the terminal group be referred to as GC (group common)-RNTI for convenience.

[0411] The above group information can be provided / set to the terminal through a higher layer signal, for example, an RRC (radio resource control) information element (IE).

[0412] The terminals included in the above terminal group may be terminals that receive data scheduling through the specific DCI format (same DCI format).

[0413] The terminal monitors PDCCH (physical downlink control channel) candidates to detect a specific DCI (downlink control information) format in a search space determined based on the above group information (S152).

[0414] The above specific DCI format can be CRC (Cyclic Redundancy Check) scrambled by the aforementioned GC-RNTI and can transmit the following information.

[0415] The specific DCI format may include, for example, a terminal information field indicating a terminal among the plurality of terminals, shared information fields including scheduling information commonly applied to the plurality of terminals, and individual information fields including scheduling information independently applied to the plurality of terminals. The number of the individual information fields may be determined based on the maximum number of physical channels that can be scheduled through the specific DCI format. The configuration of the fields included in the specific DCI format has been described above with reference to FIG. 14.

[0416] The terminal transmits or receives data based on the specific DCI format (S153). The terminal may transmit data via PUSCH based on the specific DCI format. Alternatively, the terminal may receive data via PDSCH based on the specific DCI format.

[0417] According to an embodiment, the terminal may receive a terminal information field indicating the terminal among the plurality of terminals through a first DCI format, and may receive shared information fields including scheduling information commonly applied to the plurality of terminals and individual information fields including scheduling information independently applied to the plurality of terminals through a second DCI format.

[0418] It can be determined whether the terminal is a target of the multi-terminal scheduling based on a specific bit value of a bitmap included in the specific DCI format.

[0419] For example, a bitmap value may be indicated through the terminal information field, and this bitmap may be N UE,group It can be composed of bits. For a specific terminal, when the terminal index of the terminal within the terminal group is u, the u-th bit of the bitmap can indicate whether / information about the scheduling of the physical channel that the terminal transmits and receives. If the value of the u-th bit of the bitmap is 1, it indicates that the physical channel for the terminal with the terminal index u is scheduled, and if it is 0, it can indicate that the physical channel is not scheduled.

[0420] According to the above-described method, instead of transmitting multiple DCIs to schedule multiple data sets, a single DCI can be transmitted. Therefore, the number of DCIs transmitted in the search space can be reduced. Furthermore, by sharing some DCI fields when scheduling multiple data sets, the amount of information transmitted through the DCI can be reduced. Since the number of DCIs required to schedule multiple data sets is reduced, the number of PDCCH (physical downlink control channel) candidates that the UE must monitor can also be reduced, thereby reducing the UE's PDCCH blind decoding overhead.

[0421] Figure 16 illustrates the signaling process and operation between a base station and a terminal.

[0422] Referring to Figure 16, the base station transmits group information about a group of terminals involved in multi-UE scheduling to the terminals (S161). As described above, multi-UE scheduling is a scheduling method that performs scheduling for multiple terminals through the same DCI format.

[0423] The group information may include information about a search space for detecting a specific DCI format. The specific DCI format may include scheduling information about physical downlink shared channels (PDSCHs) or physical uplink shared channels (PUSCHs) for the plurality of terminals.

[0424] The terminal monitors PDCCH candidates to detect a specific DCI format in a search space determined based on the above group information (S162).

[0425] The specific DCI format may include, for example, a terminal information field indicating a terminal among the plurality of terminals, shared information fields including scheduling information commonly applied to the plurality of terminals, and individual information fields including scheduling information independently applied to the plurality of terminals. The number of the individual information fields may be determined based on the maximum number of physical channels that can be scheduled through the specific DCI format. The configuration of the fields included in the specific DCI format has been described above with reference to FIG. 14.

[0426] The base station and the terminal perform data transmission and reception based on the above-mentioned specific DCI format (S163).

[0427] Figure 17 illustrates a wireless device applicable to the present specification.

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

[0429] A first wireless device (100) includes at least one processor (102) and at least one memory (104), and may further include at least one transceiver (106) and / or at least one antenna (108). The at least one processor (102, hereinafter simply referred to as a processor) controls at least one memory (104, hereinafter simply referred to as a memory) and / or at least one transceiver (106, hereinafter simply referred to as a transceiver or a transceiver), and may be configured to implement the descriptions, functions, procedures, proposals, methods, and / or operational flowcharts disclosed in this document. For example, the processor (102) may process information in the memory (104) to generate first information / signal, and then transmit a wireless signal including the first information / signal via the transceiver (106). In addition, the processor (102) may receive a wireless signal including second information / signal through 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 perform some or all of the processes controlled by the processor (102), or may store software code including commands for performing the descriptions, functions, procedures, proposals, methods, and / or operation flowcharts disclosed in this document. Here, the processor (102) and the memory (104) may be part of a communication modem / circuit / chip designed to implement a wireless communication technology (e.g., LTE, NR). The transceiver (106) may be connected to the processor (102) and may transmit and / or receive a wireless signal through one or more antennas (108). The transceiver (106) may include a transmitter and / or a receiver. The transceiver (106) may be used interchangeably with an RF (Radio Frequency) unit.In this specification, wireless device may also mean a communication modem / circuit / chip.

[0430] A processor (102) may be included in a terminal. The processor (102) receives group information about a terminal group related to multi-UE scheduling from a base station, monitors PDCCH (physical downlink control channel) candidates for a specific DCI (downlink control information) format based on the group information, and transmits or receives data based on the specific DCI format. At this time, the multi-terminal scheduling is a scheduling method that performs scheduling for a plurality of terminals through the same DCI format, and the processor (102) monitors the PDCCH candidates to detect the specific DCI format in a search space determined based on the group information. The specific operation thereof has been described with reference to FIGS. 14 to 16.

[0431] A second wireless device (200) includes at least one processor (202), at least one memory (204), and may further include at least one transceiver (206) and / or at least one antenna (208). The processor (202) controls the memory (204) and / or the transceiver (206), and may be configured to implement the descriptions, functions, procedures, proposals, methods, and / or operational flowcharts disclosed in this document. For example, the processor (202) may process information in the memory (204) to generate third information / signal, and then transmit a wireless signal including the third information / signal via the transceiver (206). In addition, the processor (202) may receive a wireless signal including 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 perform some or all of the processes controlled by the processor (202), or may store software code including commands for performing the descriptions, functions, procedures, proposals, methods, and / or operation flowcharts disclosed in this document. Here, the processor (202) and the memory (204) may be part of a communication modem / circuit / chip designed to implement 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 used interchangeably with an RF unit. In this specification, a wireless device may also mean a communication modem / circuit / chip.

[0432] The processor (202) may be included in a base station. The processor (202) provides group information to terminals and performs multi-terminal scheduling by transmitting a specific DCI format. Multi-terminal scheduling is a scheduling method that performs scheduling for multiple terminals through the same DCI format. The group information includes information about a search space in which the specific DCI format can be transmitted. The specific operation thereof has been described with reference to FIGS. 14 to 16.

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

[0434] 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 by hardware, firmware, software, or a combination thereof. For example, one or more Application Specific Integrated Circuits (ASICs), one or more Digital Signal Processors (DSPs), one or more Digital Signal Processing Devices (DSPDs), one or more Programmable Logic Devices (PLDs), or one or more Field Programmable Gate Arrays (FPGAs) may be included in the one or more processors (102, 202). The one or more processors (102, 202) may also be implemented by at least one computer-readable medium (CRM) containing instructions based on which at least one processor is executed.

[0435] For example, at least one computer-readable medium (CRM) including instructions based on being executed by at least one processor performs the steps of receiving group information about a group of terminals related to multi-terminal scheduling from a base station, monitoring PDCCH candidates for a specific DCI format based on the group information, and transmitting or receiving data based on the specific DCI format. In this case, the multi-terminal scheduling is a scheduling method that performs scheduling for a plurality of terminals through the same DCI format. The CRM monitors the PDCCH candidates to detect the specific DCI format in a search space determined based on the group information. The specific operation thereof has been described with reference to FIGS. 14 to 16.

[0436] The descriptions, functions, procedures, suggestions, methods and / or operation flowcharts disclosed in this document may be implemented using firmware or software, and the firmware or software may be implemented to include modules, procedures, functions, etc. The descriptions, functions, procedures, suggestions, methods and / or operation flowcharts disclosed in this document may be implemented using firmware or software in the form of codes, instructions and / or sets of instructions. The firmware or software configured to perform the descriptions, functions, procedures, suggestions, methods and / or operation flowcharts disclosed in this document 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 operation flowcharts disclosed in this document may be implemented using firmware or software in the form of codes, instructions and / or sets of instructions.

[0437] One or more memories (104, 204) may be coupled to one or more processors (102, 202) and may store various forms of data, signals, messages, information, programs, codes, instructions, and / or commands. The one or more memories (104, 204) may be configured as 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 internally and / or externally to the one or more processors (102, 202). Additionally, the one or more memories (104, 204) may be coupled to the one or more processors (102, 202) via various technologies, such as wired or wireless connections.

[0438] One or more transceivers (106, 206) can transmit user data, control information, wireless signals / channels, etc., as mentioned in the methods and / or flowcharts of this document, to one or more other devices. One or more transceivers (106, 206) can receive user data, control information, wireless signals / channels, etc., as mentioned in the descriptions, functions, procedures, proposals, methods and / or flowcharts of this document, from one or more other devices. For example, one or more transceivers (106, 206) can be connected to one or more processors (102, 202) and can transmit and receive wireless signals. For example, one or more processors (102, 202) can control one or more transceivers (106, 206) to transmit user data, control information, or wireless signals to one or more other devices. Additionally, one or more processors (102, 202) may control one or more transceivers (106, 206) to receive user data, control information, or wireless signals from one or more other devices. Additionally, one or more transceivers (106, 206) may be coupled to one or more antennas (108, 208), and one or more transceivers (106, 206) may be configured to transmit and receive user data, control information, wireless signals / channels, or the like, as referred to in the descriptions, functions, procedures, proposals, methods, and / or operational flowcharts disclosed herein, via one or more antennas (108, 208). In this document, one or more antennas may be multiple physical antennas or multiple logical antennas (e.g., antenna ports). One or more transceivers (106, 206) can convert received user data, control information, wireless signals / channels, etc. from RF band signals to baseband signals in order to process the received user data, control information, wireless signals / channels, etc. using one or more processors (102, 202).One or more transceivers (106, 206) may convert user data, control information, wireless signals / channels, etc. processed by one or more processors (102, 202) from baseband signals to RF band signals. For this purpose, one or more transceivers (106, 206) may include an (analog) oscillator and / or filter.

[0439] Figure 18 illustrates another example of a wireless device.

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

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

[0442] Fig. 19 illustrates an example of a signal processing module structure. Here, signal processing may be performed in the processor (102, 202) of Fig. 17.

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

[0444] A transmitting device can transmit one or more codewords. The coded bits within each codeword are scrambled by a scrambler (301) and transmitted over a physical channel. A codeword may also be referred to as a data string and may be equivalent to a transport block, which is a data block provided by the MAC layer.

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

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

[0447] The resource block mapper (305) can map the complex modulation symbol for each antenna port to an appropriate resource element within a virtual resource block (VRB) allocated for transmission. The resource block mapper can map the VRB to a physical resource block (PRB) according to an appropriate mapping scheme. The resource block mapper (305) can assign the complex modulation symbol for each antenna port to an appropriate subcarrier and multiplex it according to the user.

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

[0449] Fig. 20 illustrates another example of a signal processing module structure within a transmission device. Here, signal processing may be performed in a processor of a terminal / base station, such as the processor (102, 202) of Fig. 17.

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

[0451] The transmitting device can transmit coded bits within a codeword through a physical channel after scrambling the coded bits within the codeword by a scrambler (401).

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

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

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

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

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

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

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

[0459] FIG. 21 illustrates an example of a wireless communication device according to an implementation example of the present disclosure.

[0460] Referring to FIG. 21, a wireless communication device, for example, a terminal, may include at least one of a processor (2310) such as a digital signal processor (DSP) or a microprocessor, a transceiver (2335), a power management module (2305), an antenna (2340), a battery (2355), a display (2315), a keypad (2320), a global positioning system (GPS) chip (2360), a sensor (2365), a memory (2330), a subscriber identification module (SIM) card (2325), a speaker (2345), and a microphone (2350). There may be a plurality of antennas and processors.

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

[0462] Memory (2330) is connected to the processor (2310) and stores information related to the processor's operation. The memory may be located internally or externally to the processor and may be connected to the processor via various technologies, such as wired or wireless connections. The memory (2330) of FIG. 21 may be the memory (104, 204) of FIG. 17.

[0463] A user may input various types of information, such as a phone number, using various techniques, such as pressing buttons on a keypad (2320) or activating sound using a microphone (2350). The processor (2310) may receive and process the user's information and perform an appropriate function, such as dialing the entered phone number. In some scenarios, data may be retrieved from a SIM card (2325) or memory (2330) to perform the appropriate function. In some scenarios, the processor (2310) may display various types of information and data on a display (2315) for the user's convenience.

[0464] A transceiver (2335) is coupled to a processor (2310) and transmits and / or receives wireless signals, such as radio frequency (RF) signals. The processor may control the transceiver to initiate communication or transmit wireless signals containing various types of information or data, such as voice communication data. The transceiver includes a transmitter and a receiver for transmitting and receiving wireless signals. An antenna (2340) may facilitate the transmission and reception of wireless signals. In some implementations, upon receiving a wireless signal, the transceiver may forward and convert the signal to a baseband frequency for processing by the processor. The processed signal may be processed by various techniques, such as being converted into audible or readable information for output through a speaker (2345). The transceiver of FIG. 21 may be the transceiver (106, 206) of FIG. 17.

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

[0466] Fig. 21 is only one implementation example for a terminal, and the implementation examples are not limited thereto. The terminal does not necessarily have to include all the elements of Fig. 21. For example, some components, such as a keypad (2320), a Global Positioning System (GPS) chip (2360), a sensor (2365), and a SIM card (2325), may not be essential elements, and in this case, may not be included in the terminal.

[0467] Fig. 22 illustrates a communication system (1) applicable to this specification.

[0468] Referring to FIG. 22, a communication system (1) applied to the present specification includes a wireless device, a base station, and a network. Here, the wireless device refers to a device that performs communication using a wireless access technology (e.g., 5G NR (New RAT), LTE (Long Term Evolution)) and may be referred to as a communication / wireless / 5G device. Although not limited thereto, the wireless device may include a robot (100a), a vehicle (100b-1, 100b-2), an XR (eXtended Reality) device (100c), a hand-held device (100d), a home appliance (100e), an IoT (Internet of Things) device (100f), and an AI device / server (400). For example, the vehicle may include a vehicle equipped with a wireless communication function, an autonomous vehicle, a vehicle capable of performing vehicle-to-vehicle communication, etc. Here, the vehicle may include an Unmanned Aerial Vehicle (UAV) (e.g., a drone). XR devices include AR (Augmented Reality) / VR (Virtual Reality) / MR (Mixed Reality) devices, and can be implemented in the form of HMD (Head-Mounted Device), HUD (Head-Up Display) installed in a vehicle, television, smartphone, computer, wearable device, home appliance, digital signage, vehicle, robot, etc. Mobile devices can include smartphone, smart pad, wearable device (e.g., smart watch, smart glass), computer (e.g., laptop, etc.), etc. Home appliances can include TV, refrigerator, washing machine, etc. IoT devices can include sensors, smart meters, etc. For example, base stations and networks can also be implemented as wireless devices, and a specific wireless device (200a) can act as a base station / network node to other wireless devices.

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

[0470] Wireless communication / connection (150a, 150b, 150c) can be established between wireless devices (100a~100f) / base stations (200), and base stations (200) / base stations (200). Here, wireless communication / connection can be achieved through various wireless access technologies (e.g., 5G NR) such as uplink / downlink communication (150a), sidelink communication (150b) (or, D2D communication), and communication between base stations (150c) (e.g., relay, IAB (Integrated Access Backhaul). Through wireless communication / connection (150a, 150b, 150c), wireless devices and base stations / wireless devices, and base stations and base stations can transmit / receive wireless signals to each other. For example, wireless communication / connection (150a, 150b, 150c) can transmit / receive signals through various physical channels. To this end, 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.), and resource allocation processes can be performed based on various proposals of the present specification.

[0471] Meanwhile, NR supports multiple numerologies (or subcarrier spacing (SCS)) to support various 5G services. For example, an SCS of 15 kHz supports a wide area in traditional cellular bands; an SCS of 30 kHz / 60 kHz supports dense urban areas, lower latency, and wider carrier bandwidth; and an SCS of 60 kHz or higher supports a bandwidth greater than 24.25 GHz to overcome phase noise.

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

[0473] [Table 7]

[0474]

[0475] As described above, the numerical value of the frequency range of the NR system can be changed. For example, FR1 may include a band from 410 MHz to 7125 MHz, as shown in Table 8 below. For example, FR1 may include a frequency band above 6 GHz (or 5850, 5900, 5925 MHz, etc.). For example, the frequency band above 6 GHz (or 5850, 5900, 5925 MHz, etc.) included within FR1 may include an unlicensed band. The unlicensed band may be used for various purposes, such as for vehicle communications (e.g., autonomous driving).

[0476] [Table 8]

[0477]

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

Claims

1. In the method, The terminal receives group information about a terminal group related to multi-UE scheduling from the base station, The terminal monitors PDCCH (physical downlink control channel) candidates for a specific DCI (downlink control information) format based on the group information, and The above terminal transmits or receives data based on the above specific DCI format, The above multi-terminal scheduling is a scheduling method that performs scheduling for multiple terminals through the same DCI format. A method characterized in that the terminal monitors the PDCCH candidates to detect the specific DCI format in a search space determined based on the group information.

2. A method characterized in that, in the first paragraph, the terminals included in the terminal group are terminals that receive data scheduling through the specific DCI format.

3. A method according to claim 1, wherein the group information includes information about the search space for detecting the specific DCI format.

4. A method according to claim 3, wherein the group information comprises at least one of: i) an identifier for the search space, ii) a period and offset related to the search space, iii) an ID of a control resource set (CORESET) related to the search space, or iv) a Transmission Configuration Indicator (TCI) state ID applied to the CORESET.

5. In the third paragraph, the group information is characterized in that it further includes at least one of i) a terminal group index for distinguishing a terminal group, ii) a terminal index for distinguishing a specific terminal within a terminal group, iii) information on the number of terminals within a terminal group, iv) a maximum number of data that can be scheduled in one DCI format, v) a multiplexing scheme between a plurality of physical channels scheduled by multi-terminal scheduling, vi) a DCI format for a terminal group, or vii) an RNTI (Radio Network Temporary Identifier) ​​for a terminal group.

6. A method according to claim 1, wherein the specific DCI format includes scheduling information for physical downlink shared channels (PDSCHs) or physical uplink shared channels (PUSCHs) for the plurality of terminals.

7. A method according to claim 1, wherein the specific DCI format includes a terminal information field indicating the terminal among the plurality of terminals, shared information fields including scheduling information commonly applied to the plurality of terminals, and individual information fields including scheduling information independently applied to the plurality of terminals.

8. A method according to claim 7, characterized in that the number of individual information fields is determined based on the maximum number of physical channels that can be scheduled through the specific DCI format.

9. A method according to claim 1, wherein the terminal receives a terminal information field indicating the terminal among the plurality of terminals through a first DCI format, and receives shared information fields including scheduling information commonly applied to the plurality of terminals and individual information fields including scheduling information independently applied to the plurality of terminals through a second DCI format.

10. A method according to claim 1, characterized in that it is determined whether the terminal is a target of the multi-terminal scheduling based on a specific bit value of a bitmap included in the specific DCI format.

11. The terminal is, At least one transceiver; At least one memory; and At least one processor operably coupled with said at least one memory and said at least one transceiver, wherein said at least one memory comprises instructions that are executed by said at least one processor to perform operations, The above actions are, Receive group information about a terminal group related to multi-UE scheduling from a base station, Monitor PDCCH (physical downlink control channel) candidates for a specific DCI (downlink control information) format based on the above group information, and Transmission or reception of data is performed based on the above specific DCI format, The above multi-terminal scheduling is a scheduling method that performs scheduling for multiple terminals through the same DCI format. A terminal characterized in that the terminal monitors the PDCCH candidates to detect the specific DCI format in a search space determined based on the group information.

12. A terminal according to claim 11, characterized in that the terminals included in the terminal group are terminals that receive data scheduling through the specific DCI format.

13. A terminal according to claim 11, wherein the group information includes information about the search space for detecting the specific DCI format.

14. A terminal according to claim 13, wherein the group information includes at least one of: i) an identifier for the search space, ii) a period and offset related to the search space, iii) an ID of a control resource set (CORESET) related to the search space, or iv) a Transmission Configuration Indicator (TCI) state ID applied to the CORESET.

15. In the 13th paragraph, the group information further includes at least one of: i) a terminal group index for distinguishing a terminal group, ii) a terminal index for distinguishing a specific terminal within a terminal group, iii) information on the number of terminals within a terminal group, iv) a maximum number of data that can be scheduled in one DCI format, v) a multiplexing scheme between a plurality of physical channels scheduled by multi-terminal scheduling, vi) a DCI format for a terminal group, or vii) an RNTI (Radio Network Temporary Identifier) ​​for a terminal group.

16. In the 11th paragraph, the specific DCI format is characterized in that it includes scheduling information for physical downlink shared channels (PDSCHs) or physical uplink shared channels (PUSCHs) for the plurality of terminals.

17. In the 11th paragraph, the specific DCI format is characterized in that it includes a terminal information field indicating the terminal among the plurality of terminals, shared information fields including scheduling information commonly applied to the plurality of terminals, and individual information fields including scheduling information independently applied to the plurality of terminals.

18. A terminal according to claim 17, wherein the number of individual information fields is determined based on the maximum number of physical channels that can be scheduled through the specific DCI format.

19. In the 11th paragraph, the terminal is characterized in that it receives a terminal information field indicating the terminal among the plurality of terminals through a first DCI format, and receives shared information fields including scheduling information commonly applied to the plurality of terminals and individual information fields including scheduling information independently applied to the plurality of terminals through a second DCI format.

20. A terminal characterized in that, in the first paragraph, it is determined whether the terminal is a target of the multi-terminal scheduling based on a specific bit value of a bitmap included in the specific DCI format.

21. The device, At least one memory; and At least one processor operably coupled to at least one memory, wherein said at least one memory comprises instructions that are executed by said at least one processor to perform operations, The above actions are, Receive group information about a terminal group related to multi-UE scheduling from a base station, Monitor PDCCH (physical downlink control channel) candidates for a specific DCI (downlink control information) format based on the above group information, and Including performing transmission or reception of data based on the above specific DCI format, The above multi-terminal scheduling is a scheduling method that performs scheduling for multiple terminals through the same DCI format. A device characterized in that the processor monitors the PDCCH candidates to detect the specific DCI format in a search space determined based on the group information.

22. At least one computer readable medium (CRM) containing instructions based on being executed by at least one processor, An operation of receiving group information about a group of terminals related to multi-UE scheduling from a base station, An operation of monitoring PDCCH (physical downlink control channel) candidates for a specific DCI (downlink control information) format based on the above group information, and Performing an operation of transmitting or receiving data based on the above specific DCI format, The above multi-terminal scheduling is a scheduling method that performs scheduling for multiple terminals through the same DCI format. A CRM characterized by monitoring the PDCCH candidates to detect the specific DCI format in a search space determined based on the group information.

Images