Method performed by terminal or base station in wireless communication system, and device therefor
The method optimizes DCI configuration for scheduling physical layer data channels by considering UE capability and DCI overhead, addressing inefficiencies in wireless signal transmission and reception.
Patent Information
- Application Number
- PCT/KR2026/096609
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Priority Date
- 2026-01-13
- Filing Date
- 2026-05-06
- Publication Date
- 2026-11-12
AI Technical Summary
Existing wireless communication systems face challenges in efficiently performing wireless signal transmission and reception, particularly in configuring Downlink Control Information (DCI) for scheduling physical layer data channels, considering UE capability and DCI overhead aspects.
A method and apparatus for configuring DCI that includes receiving information about the number of carriers and maximum physical layer data channels that can be scheduled, along with their mapping relationships, and utilizing specific fields in the DCI based on these parameters to optimize scheduling.
This approach enables efficient signal transmission and reception in wireless communication systems by optimizing DCI configuration for scheduling physical layer data channels, improving system performance.
Smart Images

Figure KR2026096609_12112026_PF_FP_ABST
Abstract
Description
A method performed by a terminal or base station in a wireless communication system and an apparatus for the same.
[0001] The present disclosure relates to a wireless communication system, and more specifically, to a method and apparatus for transmitting or receiving uplink or downlink signals between a terminal or a base station in a wireless communication system.
[0002] The 5G mobile communication system is a successor technology to LTE (Long Term Evolution) and is a new clean-slate type of mobile communication system characterized by high performance, low latency, and high availability. In the case of 5G NR, all available spectrum resources can be utilized, ranging 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 the underlying technology of 5G mobile communication, 6G mobile communication systems are being developed.
[0003] The technical problem to be solved in this disclosure is to provide a method for efficiently performing a wireless signal transmission and reception process and an apparatus for doing so.
[0004] The proposed embodiments can provide a method for configuring a DCI for scheduling physical layer data channels, taking into account UE capability and DCI overhead aspects.
[0005] In addition to the technical challenges described above, other technical challenges can be inferred from the description below.
[0006] A method performed by a terminal according to one embodiment comprises: receiving information regarding the number of carriers set within a cell and the maximum number of physical layer data channels that can be simultaneously scheduled in the frequency domain; receiving information regarding the mapping relationship between the carriers and the physical layer data channels that can be simultaneously scheduled; receiving Downlink Control Information (DCI) including scheduling information of one or more physical layer data channels; and receiving or transmitting one or more physical layer data channels based on the information regarding the mapping relationship, wherein a specific field included in the DCI may include a number of subfields determined based on the number of carriers or the maximum number of physical layer data channels.
[0007] A device according to one embodiment includes at least one processor and at least one memory configured to store instructions that cause at least one processor to perform operations by being executed by at least one processor, and the operations of the processor include receiving information regarding the number of carriers set in one cell and the maximum number of physical layer data channels that can be simultaneously scheduled in the frequency domain, receiving information regarding the mapping relationship between the carriers and the physical layer data channels, receiving Downlink Control Information (DCI) including scheduling information of one or more physical layer data channels, and receiving or transmitting one or more physical layer data channels based on the information regarding the mapping relationship, and a specific field included in the DCI may include a number of subfields determined based on the number of carriers or the maximum number of physical layer data channels.
[0008] A device according to one embodiment may include a terminal including a transceiver or a processing device configured to control the terminal.
[0009] A method performed by a base station according to one embodiment comprises the steps of: transmitting information to a terminal regarding the number of carriers set within a cell and the maximum number of physical layer data channels that can be simultaneously scheduled in a frequency domain; transmitting information to a terminal regarding the mapping relationship between the carriers and the physical layer data channels that can be simultaneously scheduled; transmitting Downlink Control Information (DCI) to a terminal that includes scheduling information of one or more physical layer data channels; and transmitting one or more physical layer data channels to a terminal or receiving them from a terminal based on the information regarding the mapping relationship, wherein a specific field included in the DCI may include a number of subfields determined based on the number of carriers or the maximum number of physical layer data channels.
[0010] A base station according to one embodiment includes at least one processor and at least one memory configured to store instructions that cause at least one processor to perform operations by being executed by at least one processor, and the operations of the processor include transmitting information to a terminal regarding the number of carriers set within a cell and the maximum number of physical layer data channels that can be simultaneously scheduled in the frequency domain, transmitting information to a terminal regarding the mapping relationship between the carriers and the physical layer data channels that can be simultaneously scheduled, transmitting Downlink Control Information (DCI) to a terminal including scheduling information of one or more physical layer data channels, and transmitting one or more physical layer data channels to a terminal or receiving them from a terminal based on the information regarding the mapping relationship, and a specific field included in the DCI may include a number of subfields determined based on the number of carriers or the maximum number of physical layer data channels.
[0011] According to one embodiment, the maximum number of physical layer data channels may be less than or equal to the number of carriers.
[0012] According to one embodiment, a specific field may include an NDI (New Data Indicator), RV (Redundancy Version), HPI (Hybrid Automatic Repeat Request Processing Index), FDRA (Frequency Domain Resource Assignment), or MCS (Modulation and Coding Scheme) field.
[0013] According to one embodiment, the NDI, RV, or HPI field may include a number of subfields equal to the maximum number of physical layer data channels.
[0014] According to one embodiment, based on the fact that for each simultaneously schedulable physical layer data channel, up to N_s physical layer data channels are configured to be transmitted via time division multiplexing, the NDI, RV, or HPI field may include a number of subfields equal to the maximum number of physical layer data channels multiplied by N_s, and based on the fact that for each simultaneously schedulable physical layer data channel, up to N_a physical layer data channels are configured to be transmitted via spatial division multiplexing, the NDI, RV, or HPI field may include a number of subfields equal to the maximum number of physical layer data channels multiplied by N_a.
[0015] According to one embodiment, the FDRA or MCS field may include a number of subfields equal to the number of carriers or the maximum number of physical layer data channels.
[0016] According to one embodiment, the DCI further includes a Time Domain Resource Assignment (TDRA) field composed of one field, and each row of the TDRA table associated with the TDRA field includes one or more parameter sets related to the allocation of time resources, and the number of parameter sets included in each row may be equal to the number of carriers or the maximum number of physical layer data channels.
[0017] According to one embodiment, at least one of the bandwidths of each carrier set within a cell, or the sum of the bandwidths of the carriers, may have a size less than or equal to a specific value.
[0018] According to one embodiment, the maximum number of physical layer data channels that can be simultaneously scheduled may include the maximum number of physical layer data channels that can be scheduled through a single DCI while being transmitted via frequency division multiplexing at a single time.
[0019] According to one embodiment, information regarding mapping relationships is composed of a bitmap containing a number of bits equal to the number of carriers, and each bit included in the bitmap can correspond to each of the carriers.
[0020] According to the present disclosure, signal transmission and reception can be performed efficiently in a wireless communication system.
[0021] According to one embodiment, in an environment where multiple carriers are configured within a single cell, a DCI for scheduling physical layer data channels can be efficiently configured.
[0022] In addition to the technical effects described above, other technical effects can be inferred from the description below.
[0023] FIG. 1 illustrates an exemplary flexible network topology to which some of the examples of the present specification may be applied.
[0024] FIG. 2 illustrates an example of a communication system applicable to the present disclosure.
[0025] FIG. 3 illustrates an example of a wireless device that can be applied to the present disclosure.
[0026] FIG. 4 illustrates a communication procedure between a first node (e.g., terminal) and a second node (e.g., base station) applicable to the present disclosure.
[0027] Figure 5 illustrates a general functional architecture for an AI / ML model.
[0028] FIG. 6 illustrates a communication procedure between a first node (e.g., terminal) and a second node (e.g., base station) to which an AI / ML model is applied.
[0029] FIG. 7 shows an electromagnetic spectrum according to one embodiment of the present disclosure.
[0030] FIG. 8 illustrates an example of a procedure for transmitting system information for THz communication to which the present disclosure applies.
[0031] FIG. 9 illustrates a beam management procedure applicable to the present disclosure.
[0032] FIG. 10 shows an example of a sensing operation according to one embodiment of the present disclosure.
[0033] FIG. 11 illustrates a time / frequency resource for a sensing operation according to one embodiment of the present specification.
[0034] FIG. 12 illustrates a procedure related to a sensing operation according to one embodiment of the present specification.
[0035] Figure 13 illustrates the process of receiving PDSCH in NR and transmitting ACK / NACK therefor.
[0036] Figure 14 illustrates the PUSCH transmission process in NR.
[0037] FIG. 15 is a diagram illustrating the operation of a terminal and a base station according to one embodiment.
[0038] FIG. 16 illustrates the flow of a method performed by a terminal according to one embodiment.
[0039] FIG. 17 illustrates the flow of a method performed by a base station according to one embodiment.
[0040] In this specification, "A or B" may mean "only A," "only B," or "both A and B." Alternatively, in this specification, "A or B" may be interpreted as "A and / or B." For example, in this specification, "A, B or C" may mean "only A," "only B," "only C," or "any combination of A, B and C."
[0041] A slash ( / ) or a comma used in this specification may mean "and / or." For example, "A / B" may mean "A and / or B." Accordingly, "A / B" may mean "only A," "only B," or "both A and B." For example, "A, B, C" may mean "A, B or C."
[0042] In this specification, "at least one of A and B" may mean "only A," "only B," or "both A and B." Additionally, in this specification, the expressions "at least one of A or B" or "at least one of A and / or B" may be interpreted as synonymous with "at least one of A and B."
[0043] Additionally, in this specification, "at least one of A, B and C" may mean "only A," "only B," "only C," or "any combination of A, B and C." Also, "at least one of A, B or C" or "at least one of A, B and / or C" may mean "at least one of A, B and C."
[0044] Additionally, parentheses used in this specification may mean "for example." Specifically, when indicated as "control information (ABC)," "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." Also, when indicated as "control information (i.e., ABC)," "ABC" may be described as an example of "control information."
[0045] In addition, terms such as "first," "second," etc. in this specification are used solely for the purpose of distinguishing one component from another and are not used to limit the components, nor are they used to limit the order or importance of 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 likewise, a second component in one embodiment may be referred to as a first component in another embodiment.
[0046] In the following explanation, 'when, if, in case of' can be replaced with 'based on'.
[0047] Technical features described individually within a single drawing in this specification may be implemented individually or simultaneously.
[0048] In this specification, a terminal is a user-side device (user equipment, UE) or a consumer-side device, and may also be referred to as a first node that receives / transmits signals from / to a base station / second node / IAB node / Transmission-Reception Point (TRP). A terminal may correspond to a physical node or a logical node. A terminal may correspond to a user-side endpoint or an intermediate point between other endpoints. In communication between two points 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 fixed-location node or a non-fixed-location (or mobile) node.
[0049] In this specification, a Base Station (BS) is a device on the network side and may also be referred to as a second node / IAB node / x-NodeB (x-NodeB, where x may be an abbreviation related to Radio Access Technology (RAT)) / Transmission-Reception Point (TRP). A Base Station may correspond to a physical node or a logical node. A Base Station may correspond to an endpoint on the network side or an intermediate point between other endpoints. In communication between two points not limited to endpoints (including one-to-one / many-to-one / one-to-many / many-to-many communication), a Base Station may correspond to a serving node. A Base Station may be a node with a fixed location or a node with an indefinite location.
[0050] In this specification, higher layer parameters may be set for the terminal, pre-set, or pre-defined. For example, a base station may transmit higher layer parameters to the terminal. For example, the terminal may transmit parameters such as capability to the base station as higher layer parameters. For example, higher layer parameters may be transmitted via RRC (radio resource control) signaling or MAC (medium access control) signaling.
[0051] In this specification, information / state / parameters being "configured" or "pre-configured" may be interpreted as the information / state / parameters being provided / pre-provided to the terminal through pre-defined signaling (e.g., SIB, MAC, RRC) from the base station. In this specification, information / state / parameters being "defined" or "pre-defined" may be interpreted as being known or stored in advance by the base station and the terminal without signaling between the base station and the terminal.
[0052] 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.
[0053] The technology described in this specification can be implemented as 6G wireless technology and applied to various 6G systems. For example, 6G systems may have key factors such as eMBB (enhanced mobile broadband), URLLC (ultra-reliable low latency communications), mMTC (massive machine-type communication), AI (artificial intelligence) integrated communication, tactile internet, high throughput, high network capacity, high energy efficiency, low backhaul and access network congestion, and enhanced data security.
[0054] For background technology, terms, abbreviations, etc. used in this specification, refer to the following standard documents.
[0055] - 38.211: Physical channels and modulation
[0056] - 38.212: Multiplexing and channel coding
[0057] - 38.213: Physical layer procedures for control
[0058] - 38.214: Physical layer procedures for data
[0059] - 38.300: NR and NG-RAN Overall Description
[0060] - 38.331: Radio Resource Control (RRC) protocol specification
[0061] - 37.213: Introduction of channel access procedures to unlicensed spectrum for NR-based access
[0062] <Symbols, Abbreviations, Terms>
[0063] - SSB: Synchronization Signal Block
[0064] - MIB: Master Information Block
[0065] - RMSI: Remaining Minimum System Information
[0066] - FR1: Frequency Range 1. 6GHz 이하(예, 450 MHz ~ 6000 MHz)의 주파수 영역을 지칭
[0067] - FR2: Frequency Range 2. 24GHz 이상의 millimeter wave (mmWave) 영역(예, 24250 MHz ~ 52600 MHz)을 지칭
[0068] - BW: Bandwidth
[0069] - BWP: Bandwidth Part
[0070] - RNTI: Radio Network Temporary Identifier
[0071] - SI-RNTI: System Information Radio-Network Temporary Identifier
[0072] - P-RNTI: Paging RNTI
[0073] - RAR-RNTI: Random Access Response RNTI
[0074] - TC-RNTI: Temporary C-RNTI
[0075] - C-RNTI: Cell RNTI
[0076] - CRC: Cyclic Redundancy Check
[0077] - SIB: System Information Block
[0078] - SIB1: SIB1 for NR devices (i.e., Remaining Minimum System Information (RMSI)). Broadcasts information necessary for cell connection of NR terminals.
[0079] - DCI: Downlink Control Information
[0080] - PDCCH: Physical Downlink Control CHannel
[0081] - PUCCH: Physical Uplink Control CHannel
[0082] - PDSCH: Physical Downlink Shared CHannel
[0083] - PUSCH: Physical Uplink Shared CHannel
[0084] - SS: Search Space
[0085] - SSS: Search Space Set
[0086] - CORESET: Control Resource Set. The time / frequency resource when the NR terminal attempts candidate PDCCH decoding.
[0087] - CORESET#0: CORESET for Type0-PDCCH CSS set for NR devices (configured in MIB)
[0088] - Type0-PDCCH CSS set: a search space set in which an NR UE monitors a set of PDCCH candidates for a DCI format with CRC scrambled by a SI-RNTI
[0089] - MO: PDCCH Monitoring Occasion
[0090] - Cell defining SSB (CD-SSB): An NR SSB that includes RMSI scheduling information
[0091] - Non-cell defining SSB (non-CD-SSB): Refers to an SSB deployed in an NR sync raster that does not include the corresponding cell's RMSI scheduling information for measurement purposes. However, it may include information indicating the location of the cell defining SSB.
[0092] - SCS: subcarrier spacing
[0093] - Camp on: "Camp on" is the UE state in which the UE stays on a cell and is ready to initiate a potential dedicated service or to receive an ongoing broadcast service.
[0094] - TB: Transport Block
[0095] - SIB1-PDSCH: PDSCH transmitting SIB1
[0096] - SIB1-DCI: DCI scheduling SIB1-PDSCH. DCI format 1_0 with CRC scrambled by SI-RNTI.
[0097] - SIB1-PDCCH: SIB1-DCI를 전송하는 PDCCH
[0098] - MCS: Modulation and Coding Scheme
[0099] - FDRA: Frequency Domain Resource Allocation
[0100] - TDRA: Time Domain Resource Allocation
[0101] - RA: Random Access
[0102] - MSGA: preamble and payload transmissions of the random access procedure for 2-step RA type.
[0103] - MSGB: response to MSGA in the 2-step random access procedure. MSGB may consist of response(s) for contention resolution, fallback indication(s), and backoff indication.
[0104] - RO: 4-step RACH and 2-step RACH(if configured)를 위한 RACH Occasion
[0105] - PG: MsgA-Preambles Group
[0106] - RAR: Randoma Access Response
[0107] - RAR window: the time window to monitor RA response(s)
[0108] - FH: Frequency Hopping
[0109] - DL: Downlink
[0110] - UL: Uplink
[0111] - iBWP: initial BWP
[0112] - iBWP-DL(-UL): initial DL(UL) BWP
[0113] - CS: Cyclic shift
[0114] - NB: Narrowband
[0115] - WB: Wideband
[0116] - TO: Traffic Offloading
[0117] - mMTC; massive Machine Type Communications
[0118] - eMBB: enhanced Mobile Broadband Communication
[0119] - URLLC: Ultra-Reliable and Low Latency Communication
[0120] - FDD: Frequency Division Duplex
[0121] - HD-FDD: Half-Duplex-FDD
[0122] - DRX: Discontinuous Reception
[0123] - MAC (CE): Medium Access Control (Control Element)
[0124] - MAC CE
[0125] - RRC: Radio Resource Control
[0126] - RRM: Radio Resource Management
[0127] - MM: Mobility Management
[0128] - IWSN: Industrial Wireless Sensor Network
[0129] - LPWA: Low Power Wide Area
[0130] - RB: Resource Block
[0131] - CCE: Control Channel Element
[0132] - AL: Aggregation Level
[0133] - PRG: Physical Resource-block Group
[0134] - DFT-s-OFDM: DFT-spread OFDM
[0135] - PBCH: Physical Broadcast Channel
[0136] - BD: blind detection
[0137] - EPRE: Energy Per RE
[0138] - SNR: Signal-to-Noise Ratio
[0139] - TDM: Time Division Multiplexing
[0140] - FDM: Frequency Division Multiplexing
[0141] - DMRS: DeModulation Reference Signal
[0142] - TDD: Time Division Duplex
[0143] - PCI: Physical layer Cell ID
[0144] - UE: User Equipment. In the case of LTE, NR, or next-generation communication systems, it refers to the LTE, NR, or next-generation communication system UE / terminal, respectively.
[0145] - F-gap: Frequency gap
[0146] - T-gap: Time gap
[0147] - TD: Time Domain
[0148] - FD: Frequency Domain
[0149] - PEI: Paging Early Indication
[0150] - LP-WUS: Low-Power Wake-Up Signal
[0151] - LP-SS: Low-Power Synchronization Signal
[0152] - RSRP: Reference Signal Received Power
[0153] - PRB: Physical Resource Block
[0154] - VRB: Virtual Resource Block
[0155] - PHR: Power Headroom Report
[0156] - BPF: Band-Pass Filter
[0157] - SFO: Sampling Frequency Offset
[0158] - ASK: Amplitude Shift Keying
[0159] - DSB-ASK: Double-SideBand ASK
[0160] - SSB-ASK: Single-SideBand ASK
[0161] - PR-ASK: Phase-Reversal ASK
[0162] - OOK: On-Off Keying
[0163] - PSK: Phase-Shift Keying
[0164] - BPSK: Binary-PSK
[0165] - FSK: Frequency-Shift Keying
[0166] - B-FSK: Binary FSK
[0167] - M-FSK: M-ary FSK
[0168] - Ncp-ofdm, Ncp, Nu: CP-OFDM symbol에서 각각 CP-OFDM symbol 구간, CP 구간, useful OFDM symbol 구간의 sample 단위의 길이. Ncp-ofdm=Ncp+Nu.
[0169] - ME: Manchester Encoding
[0170] - OH: Overhead
[0171] - HARQ: Hybrid Automatic Repeat Request
[0172] - DAI: Downlink Assignment Index
[0173] - RV: Redundancy Version
[0174] - NDI: New Data Indicator
[0175] - PRI: PUCCH Resource Indicator
[0176] - XR: eXtended Reality
[0177] - SR: Scheduling Request
[0178] - A / N: Ack / Nack
[0179] - NES: Network Energy Saving
[0180] - Floor(X): Floor function that takes as input a real number X and gives as output the greatest integer less than or equal to X.
[0181] - Ceil(X): Ceiling function that takes as input a real number X and gives as output the smallest integer greater than or equal to X.
[0182] FIG. 1 illustrates an exemplary flexible network topology to which some of the examples of the present specification may be applied.
[0183] To compensate for incomplete areas of network coverage, a network topology in which the Split Radio Access Network (RAN) is configured more flexibly and resiliently may be considered. To this end, various nodes such as IAB nodes, relays, and RF repeaters, as exemplified in Fig. 1, may be applied, and NTN may be integrated. For example, an IAB node may correspond to a node that provides wireless backhaul. For example, a relay may refer to any intermediate point, and 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. For example, an RF repeater may correspond to a node that performs simple signal amplification and forwarding functions, and in the case of a network-controlled repeater, it may adjust transmit / receive settings based on information provided by the network as well as signal amplification and forwarding. For example, an NTN node may correspond to a satellite or aircraft that provides NTN coverage that is difficult for a terrestrial network to provide. In addition to these examples, various intermediate points can be introduced to improve network topology.
[0184] Referring to FIG. 1, a split RAN can support the division of a base station into one centralized unit (CU) and one or more distributed units (DU). The CU and DU may correspond to logical units. The CU may be further divided 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 DU, various intermediate points may be introduced to compensate for this.
[0185] An intermediate point may correspond to a terminal or a base station depending on its relative relationship with other nodes. For example, an IAB node may include a mobile-termination (MT) portion and a DU. The MT can connect the IAB node to a donor node. The DU of the IAB node may serve other terminals or connect to other IAB nodes to provide multi-hop wireless backhaul to terminals. In other words, an IAB node may correspond to a base station in its relative relationship with user-side nodes and to a terminal in its relative relationship with network-side nodes.
[0186] In some examples of this specification, the description of a terminal may apply equally to an intermediate point corresponding to a terminal in relation to a network-side endpoint as well as to a user-side endpoint. Similarly, in some examples of this specification, the description of a base station may apply equally to an intermediate point corresponding to a base station in relation to a user-side endpoint as well as to a network-side endpoint. However, in most cases where there is no additional description of the operation of three or more entities, the communication entities in this specification are briefly described by the term terminal and / or base station (or first node and / or second node), wherein the term terminal and / or base station (or first node and / or second node) is interpreted to include or replace any endpoint or any intermediate point in relation to other nodes.
[0187] That is, for the sake of brevity of description in some examples of this specification, the subject of the operation may be referred to as a base station and / or terminal (or a first node and / or a second node). Additionally, the term base station and / or terminal (or a first node and / or a second node) may be interpreted or substituted as in the following examples: for example, the base station (or the first node) and the terminal (or the second node) may correspond to a first endpoint and a second endpoint, respectively; may correspond to an endpoint and an intermediate point, respectively; may correspond to an intermediate point and an endpoint, respectively; or may correspond to a first intermediate point and a second intermediate point, respectively.
[0188] In this specification, there may be no intermediate points between the base station and the terminal, or there may be one or more. If intermediate points exist, the intermediate points may correspond to IAB nodes, relays, RF repeaters, NTN (non-terrestrial network) nodes, or nodes supporting other functions. The intermediate points may be nodes with a fixed location or nodes with an indefinite location.
[0189] FIG. 2 illustrates a communication system applicable to the present disclosure.
[0190] The communication system (100) of FIG. 2 includes a wireless device (110), a network device (120), and a network (130). Here, the wireless device (110) refers to a device that performs communication using wireless access technology (e.g., LTE, LTE-A, LTE-A pro, NR, 5G, 5G-A, 6G) and may be referred to as a communication / wireless / 5G / 6G device. Although not limited thereto, the wireless device (110) may include a robot (110a), a vehicle (110b-1, 110b-2), an XR (extended reality) device (110c), a hand-held device (110d), a home appliance (110e), an IoT (Internet of Thing) device (110f), and an AI (artificial intelligence) device / server (110g). For example, the vehicle may include a vehicle equipped with wireless communication capabilities, an autonomous vehicle, a vehicle capable of performing inter-vehicle communication, etc. Here, the vehicle (110b-1, 110b-2) may include an unmanned aerial vehicle (UAV) (e.g., a drone). The XR device (110c) includes an augmented reality (AR) / virtual reality (VR) / mixed reality (MR) device and may be implemented in the form of a head-mounted device (HMD), a head-up display (HUD) equipped in a vehicle, a television, a smartphone, a computer, a wearable device, a home appliance, digital signage, a vehicle, a robot, etc. The portable device (110d) may include a smartphone, a smartpad, a wearable device (e.g., a smartwatch, smart glasses), a computer (e.g., a laptop, etc.). The home appliance (110e) may include a TV, a refrigerator, a washing machine, etc. The IoT device (110f) may include a sensor, a smart meter, etc. The wireless device (110) may correspond to a terminal (or first node) or an intermediate point.The network device (120) may correspond to a base station (or a second node) or another intermediate point. For example, the network device (120) may also be implemented as a wireless device (110), and a specific wireless device (120a) may operate as a network device (120) to another wireless device (110).
[0191] Wireless devices (110a to 110f) can be connected to a network (130) through a network device (120). AI technology may be applied to the wireless devices (110a to 110f), and the wireless devices (110a to 110f) can be connected to an AI server (110g) through the network (130). The network (130) can be configured using a 3G network, a 4G (e.g., LTE) network, a 5G (e.g., NR) network, or a 6G network. The wireless devices (110a to 110f) may communicate with each other through the network device (120) / network (130), but may also communicate directly (e.g., sidelink communication) without going through the network device (120) / network (130). For example, vehicles (110b-1, 110b-2) can communicate directly (e.g., V2V (vehicle to vehicle) / V2X (vehicle to everything) communication). Also, an IoT device (110f) (e.g., a sensor) can communicate directly with another IoT device (e.g., a sensor) or other wireless devices (110a to 110f).
[0192] Wireless communication / connection (150a, 150b, 150c) can be established between wireless devices (110a to 110f) / network devices (120) and between network devices (120). Here, wireless communication / connection can be established through various wireless access technologies such as uplink / downlink communication (150a), sidelink communication (150b) (or D2D communication), and communication between network devices (150c) (e.g., relay, IAB (integrated access backhaul)). Through wireless communication / connection (150a, 150b, 150c), wireless devices and network devices / wireless devices, and network devices and network devices can transmit / receive wireless signals to / from each other. For example, wireless communication / connection (150a, 150b, 150c) can transmit / receive signals through various physical channels. To this end, based on the various descriptions of the present disclosure, at least some of the following may be performed: a process for setting various configuration information for the transmission / reception of a wireless signal, a process for various signal processing (e.g., channel encoding / decoding, modulation / demodulation, resource mapping / demapping, etc.), a resource allocation process, etc.
[0193] FIG. 3 illustrates an example of a wireless device that can be applied to the present disclosure.
[0194] Referring to FIG. 3, the wireless device (200) can transmit and receive wireless signals through various wireless access technologies (e.g., LTE, LTE-A, LTE-A pro, NR, 5G, 5G-A, 6G). The wireless device (200) includes at least one processor (202) and at least one memory (204), and may additionally include at least one transceiver (206) and / or at least one antenna (208).
[0195] 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 sequences of operation disclosed in this document. For example, the processor (202) may process information within the memory (204) to generate a first information / signal and then transmit a wireless signal containing the first information / signal through the transceiver (206). Additionally, the processor (202) may receive a wireless signal containing a second information / signal through the transceiver (206) and then store information obtained from the signal processing of the second 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, memory (204) may store software code containing instructions for performing some or all of the processes controlled by the processor (202) or for performing the descriptions, functions, procedures, proposals, methods, and / or sequences of operations disclosed in this document. Here, the processor (202) and memory (204) may be part of a communication modem / circuit / chip designed to implement wireless communication technology. A transceiver (206) may be connected to the processor (202) and may transmit and / or receive wireless signals through at least one antenna (208). The transceiver (206) may include a transmitter and / or receiver. The transceiver (206) may be interchangeably used with an RF (radio frequency) unit. In this disclosure, a wireless device may mean a communication modem / circuit / chip.
[0196] Hereinafter, hardware elements of the wireless device (200) will be described in more detail. Although not limited thereto, at least one protocol layer may be implemented by at least one processor (202). For example, at least one processor (202) may implement at least one layer (e.g., functional layers such as PHY (physical), MAC (media access control), RLC (radio link control), PDCP (packet data convergence protocol), RRC (radio resource control), and SDAP (service data adaptation protocol). At least one processor (202) may generate at least one PDU (Protocol Data Unit) and / or at least one SDU (service data unit) according to the descriptions, functions, procedures, proposals, methods and / or operation sequences disclosed in this document. At least one processor (202) may generate messages, control information, data, or information according to the descriptions, functions, procedures, proposals, methods and / or operation sequences disclosed in this document. At least one processor (202) may generate a signal (e.g., baseband signal) including a PDU, SDU, message, control information, data, or information according to the functions, procedures, proposals, and / or methods disclosed in this document and provide it to at least one transceiver (206). At least one processor (202) may receive a signal (e.g., baseband signal) from at least one transceiver (206) and may obtain a PDU, SDU, message, control information, data, or information according to the descriptions, functions, procedures, proposals, methods, and / or operation sequences disclosed in this document.
[0197] At least one processor (202) may be referred to as a controller, microcontroller, microprocessor, or microcomputer. At least one processor (202) may be implemented by hardware, firmware, software, or a combination thereof. For example, at least one application-specific integrated circuit (ASIC), at least one digital signal processor (DSP), at least one digital signal processing device (DSPD), at least one programmable logic device (PLD), or at least one field programmable gate array (FPGA) may be included in at least one processor (202). The descriptions, functions, procedures, proposals, methods, and / or operation sequences disclosed in this document may be implemented using firmware or software, and the firmware or software may be implemented to include modules, procedures, functions, etc. Firmware or software configured to perform the descriptions, functions, procedures, proposals, methods, and / or operation sequences disclosed in this document may be included in at least one processor (202) or stored in at least one memory (204) and driven by at least one processor (202). The descriptions, functions, procedures, proposals, methods, and / or flowcharts disclosed in this document may be implemented using firmware or software in the form of code, instructions, and / or sets of instructions.
[0198] At least one memory (204) may be connected to at least one processor (202) and may store various forms of data, signals, messages, information, programs, codes, instructions, and / or commands. At least one memory (204) may be composed of ROM (read-only memory), RAM (random access memory), EPROM (erasable programmable read-only memory), flash memory, hard drive, registers, cache memory, computer read storage media, and / or combinations thereof. At least one memory (204) may be located inside and / or outside of at least one processor (202). Additionally, at least one memory (204) may be connected to at least one processor (202) via various technologies, such as wired or wireless connections.
[0199] At least one transceiver (206) may transmit user data, control information, wireless signals / channels, etc., as mentioned in the methods and / or operation flowcharts, etc. of this document to at least one other device. At least one transceiver (206) may receive user data, control information, wireless signals / channels, etc., as mentioned in the descriptions, functions, procedures, proposals, methods and / or operation flowcharts, etc. disclosed in this document from at least one other device. For example, at least one transceiver (206) may be connected to at least one processor (202) and may transmit and receive wireless signals. For example, at least one processor (202) may control at least one transceiver (206) to transmit user data, control information, or wireless signals to at least one other device. Additionally, at least one processor (202) may control at least one transceiver (206) to receive user data, control information, or wireless signals from at least one other device. Additionally, at least one transceiver (206) may be connected to at least one antenna (208), and at least one transceiver (206) may be configured to transmit and receive user data, control information, wireless signals / channels, etc., as described in the descriptions, functions, procedures, proposals, methods, and / or operation sequence diagrams disclosed in this document through at least one antenna (208). In this document, at least one antenna may be a plurality of physical antennas or a plurality of logical antennas (e.g., antenna ports). At least one transceiver (206) may convert the received 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 at least one processor (202). At least one transceiver (206) may convert the processed user data, control information, wireless signals / channels, etc., from baseband signals to RF band signals using at least one processor (202).To this end, at least one transceiver (206) may include an (analog) oscillator and / or filter.
[0200] The components of the wireless device described with reference to FIG. 3 may be referred to by other terms in terms of their function. For example, the processor (202) may be referred to as the control unit, the transceiver (206) as the communication unit, and the memory (204) as the storage unit. In some cases, the communication unit may be used to mean at least a part of the processor (202) and the transceiver (206).
[0201] The structure of the wireless device described with reference to FIG. 3 can be understood as the structure of at least part of various devices. For example, the structure of the wireless device illustrated in FIG. 3 may be at least part of the various devices described with reference to FIG. 2 (e.g., robot (110a), vehicle (110b-1, 110b-2), XR device (110c), portable device (110d), home appliance (110e), IoT device (110f), AI device / server (110g)). Furthermore, according to various embodiments, the device may include other components in addition to the components illustrated in FIG. 3.
[0202] For example, the device may be a portable device such as a smartphone, smartpad, wearable device (e.g., smart watch, smart glasses), or portable computer (e.g., laptop, etc.). In this case, the device may further include at least one of a power supply unit that supplies power and includes a wired / wireless charging circuit, a battery, etc., an interface unit that includes at least one port for connection with another device (e.g., audio input / output port, video input / output port), and an input / output unit for inputting and outputting video information / signals, audio information / signals, data, and / or information input by a user.
[0203] For example, the device may be a mobile device such as a mobile robot, vehicle, train, manned / unmanned aerial vehicle (AV), or ship. In this case, the device may further include at least one of a drive unit comprising at least one of an engine, motor, power train, wheel, brake, and steering device of the device; a power supply unit that supplies power and includes a wired / wireless charging circuit, battery, etc.; a sensor unit that senses state information, environmental information, and user information of the device or its surroundings; an autonomous driving unit that performs functions such as path maintenance, speed control, and destination setting; and a position measurement unit that acquires position information of the moving body through a GPS (global positioning system) and various sensors.
[0204] For example, the device may be an XR device such as an HMD, a HUD (head-up display) equipped in a vehicle, a television, a smartphone, a computer, a wearable device, a home appliance, digital signage, a vehicle, a robot, etc. In this case, the device may further include at least one of a power supply unit that supplies power and includes a wired / wireless charging circuit, a battery, etc., an input / output unit that acquires control information, data, etc. from the outside and outputs a generated XR object, and a sensor unit that senses state information, environment information, and user information of the device or the surroundings of the device.
[0205] For example, the device may be a robot that can be classified into industrial, medical, household, military, etc., depending on the purpose or field of use. In this case, the device may further include at least one of a sensor unit that senses state information, environmental information, and user information of the device or its surroundings, and a drive unit that performs various physical actions, such as moving robot joints.
[0206] For example, the device may be an AI device such as a TV, projector, smartphone, PC, laptop, digital broadcasting terminal, tablet PC, wearable device, set-top box (STB), radio, washing machine, refrigerator, digital signage, robot, vehicle, etc. In this case, the device may further include at least one of an input unit that acquires various types of data from the outside, an output unit that generates output related to sight, hearing, or touch, a sensor unit that senses state information, environmental information, and user information of the device or its surroundings, and a training unit that learns a model composed of an artificial neural network using training data.
[0207] The structure of the wireless device exemplified in FIG. 3 may be understood as part of a terminal (or first node), or part of an intermediate point, or part of a base station (or second node). If the device exemplified in FIG. 3 is a base station (or second node), the device may further include a wired transceiver for front haul and / or back haul communication. However, if the front haul and / or back haul communication is based on wireless communication, at least one transceiver (206) exemplified in FIG. 3 is used for front haul and / or back haul communication, and the wired transceiver may not be included.
[0208] FIG. 4 illustrates a communication procedure between a first node (e.g., terminal) and a second node (e.g., base station) applicable to the present disclosure.
[0209] The second node of FIG. 4 supports dynamic spectrum sharing (DSS) and can provide connectivity to both nodes where 6G technology is implemented and nodes where pre-6G wireless communication technology (e.g., 5G, 4G) is implemented. That is, the first node of FIG. 4 may have 6G technology implemented or pre-6G wireless communication technology (e.g., 5G, 4G) implemented. Additionally, the first node and / or the second node may support full duplex mode as well as non-overlapping full duplex mode.
[0210] In FIG. 4, for the sake of simplicity of explanation, the first node and the second node are assumed to be a terminal and a base station, respectively, and the operation of the terminal (110) and the base station (120) transmitting and / or receiving data, and the operation performed prior to this, are illustrated. However, the operation of FIG. 4 is not limited to the operation between the terminal and the base station, but can be interpreted as the operation between the first node and the second node. Additionally, FIG. 4 illustrates the operation of direct transmission and reception of wireless signals between the terminal (110) and the base station (120), but there may be one or more intermediate points between the terminal (110) and the base station (120), and wireless signals may be transmitted and received via one or more intermediate points.
[0211] Referring to FIG. 4, the terminal (110) and the base station (120) can perform synchronization (401). For example, the terminal (110) performs an initial cell search operation. Specifically, the terminal (110) can detect a synchronization signal for at least one base station connection transmitted from the base station (120) according to a predefined rule. Here, the synchronization signal may include a plurality of synchronization signals classified according to structure or use (e.g., a first synchronization signal (e.g., a primary synchronization signal), a second synchronization signal (e.g., a secondary synchronization signal), etc.). Through this, the terminal (110) can identify the boundary of the unit (e.g., frame, subframe, slot and / or symbol) constituting the wireless signal transmission of the base station (120) and obtain information about the base station (120) (e.g., cell identifier).
[0212] The terminal (110) can obtain system information transmitted from the base station (120) (403). System information is information related to the attributes, characteristics, and / or capabilities of the base station (120) required to connect to the base station (120) and use the service, and can be classified according to content (e.g., whether it is essential for connection), transmission structure (e.g., channel used, whether it is provided on-demand), etc., and can be classified, for example, into first system information (e.g., MIB (master information block), primary system information), second system information (e.g., SIB (system information block), secondary system information), etc. If necessary, the terminal (110) may transmit a signal requesting system information prior to receiving the system information. However, the request and provision of system information may be performed after the random access procedure described later.
[0213] A terminal (110) and a base station (120) can perform a random access procedure (405). The terminal (110) can transmit and / or receive at least one message for a random access procedure (e.g., random access preamble, RAR (random access response) message, etc.) based on information related to the channel for the random access procedure of the base station (120) obtained through system information (e.g., channel location, channel structure, structure of supported preamble, etc.). For example, the terminal (110) can transmit a first message (e.g., preamble, MSG1) through the channel for the random access procedure, receive a second message (e.g., RAR message, MSG2), transmit a third message (e.g., MSG3) containing information related to the terminal (110) (e.g., identification information) to the base station (120) using scheduling information included in the second message, and receive a fourth message (e.g., MSG4) for contention resolution and / or connection establishment. As another example, the first message and the third message can be transmitted and received as a single message, or the second message and the fourth message can be transmitted and received as a single message.
[0214] The terminal (110) and the base station (120) can perform signaling of control information (407). Here, the control information can be defined in various layers, such as a layer that controls the connection (e.g., a radio resource control (RRC) layer), a layer that handles mapping between logical channels and transmission channels (e.g., a media access control (MAC) layer), and a layer that handles physical channels (e.g., a physical (PHY) layer). For example, the terminal (110) and the base station (120) can perform at least one of signaling to establish a connection, signaling to determine settings related to communication, and signaling to indicate allocated resources.
[0215] The terminal (110) and the base station (120) can transmit and / or receive data (409). In other words, the terminal (110) and the base station (120) can process, transmit and / or receive data based on the signaling of control information. For example, when transmitting data, the terminal (110) or the base station (120) can perform at least one of channel encoding, rate matching, scrambling, constellation mapping, layer mapping, waveform modulation, antenna mapping, and resource mapping on the information bits. Conversely, when receiving data, the terminal (110) or the base station (120) can perform at least one of signal extraction from resources, antenna-specific waveform demodulation, signal placement considering layer mapping, constellation demapping, descrambling, and channel decoding.
[0216] 6G System Core Technology
[0217] The 6G (wireless communication) system aims for (i) very high data rates per device, (ii) a very large number of connected devices, (iii) global connectivity, (iv) very low latency, (v) reduced energy consumption of battery-free IoT (internet of things) devices, (vi) ultra-reliable connectivity, and (vii) connected intelligence with machine learning capabilities. The vision of the 6G system can be four aspects: intelligent connectivity, deep connectivity, holographic connectivity, and ubiquitous connectivity.
[0218] As core implementation technologies for 6G systems, technologies such as artificial intelligence (AI), THz (Terahertz) communication, optical wireless technology, FSO backhaul network, massive MIMO (Multiple Input Multiple Output) technology, blockchain, 3D networking, quantum communication, unmanned aerial vehicles, cell-free communication, wireless information and energy transfer (WIET), integration of sensing and communication, integration of access backhaul networks, holographic beamforming, big data analysis, and large intelligent surface (LIS) can be adopted.
[0219] artificial intelligence
[0220] The introduction of AI into communications can streamline and enhance real-time data transmission. AI can determine how complex target tasks are performed using numerous analyses. In other words, AI can increase efficiency and reduce processing latency. Time-consuming tasks such as handover, network selection, and resource scheduling can be performed instantly using AI. AI can also play a significant role in M2M, machine-to-human, and human-to-machine communication. Furthermore, AI can enable rapid communication in Brain-Computer Interfaces (BCI). AI-based communication systems can be supported by metamaterials, intelligent structures, intelligent networks, intelligent devices, intelligent cognitive radios, self-sustaining wireless networks, and machine learning.
[0221] The following describes a functional framework for AI / ML operations.
[0222] Below, to provide a more specific explanation of AI (or AI / ML), terms may be defined as follows.
[0223] - Data collection: Data collected from network nodes, management entities, or terminals, serving as a basis for AI model training, data analysis, and inference.
[0224] - AI Model: A data-driven algorithm that applies AI technology to generate a set of outputs containing predictive information and / or decision parameters based on a set of inputs.
[0225] - AI / ML Training: An online or offline process of training an AI model by learning features and patterns that best represent data and acquire an AI / ML model trained for inference.
[0226] - AI / ML Inference: A process of making predictions or deriving decisions based on collected data and AI models using trained AI models.
[0227] Life Cycle Management (LCM) procedures for AI / ML models (i.e., model training, model deployment, model inference, model monitoring, model updating, etc.) can be classified into functionality-based LCM and model-based LCM. In functionality-based LCM, AI / ML models may not be identifiable within the network, and the network can direct the activation, deactivation, fallback, or switching of AI / ML functionality. In model-ID (identifier)-based LCM, AI / ML models can be identified within the network, and the network or terminal can activate, deactivate, select, or switch AI / ML models via the model ID.
[0228] Figure 5 illustrates a general functional architecture for an AI / ML model.
[0229] In particular, Figure 5 illustrates a general functional architecture related to both Functionality-based LCM and Model-based LCM. Some functions or some data / information / command flows (i.e., arrows) illustrated in Figure 5 may be omitted.
[0230] Referring to FIG. 5, a general functional framework may be configured to include a data collection function (10), a model training function (20), a management function (30), an inference function (40), and a model storage function (50).
[0231] The Data Collection function (10) is a function that provides input data to the Model Training function (20), Management function (30), and Inference function (40). The Data Collection function (10) performs data preparation based on raw data and can provide input data processed through data preparation. Examples of raw data may include received data / measurement data from terminals or other network entities, inference / output of AI / ML models, etc. The Data Collection function (10) may be performed by a single entity (e.g., terminal, network node, etc.) but may also be performed by multiple entities.
[0232] Here, training data (11) refers to data required as input for the AI / ML model training function (20). monitoring data (12) refers to data required as input for the management (30) of the AI / ML model or AI / ML function. inference data (13) refers to data required as input for the AI / ML inference function (30).
[0233] The Model Training function (20) is a function that performs AI / ML model training, validation, and testing, which can generate model performance metrics that can be used as part of the AI / ML model testing procedure. If necessary, the Model Training function (20) can perform data preparation (e.g., data pre-processing and cleaning, forming and transformation) based on the Training Data (11) delivered from the Data Collection function (10).
[0234] Trained / Updated Model (21): If there is a Model Storage function (50), it is used to transfer trained, validated, and tested AI / ML models to the Model Storage function (50) or to transfer updated versions of the models to the Model Storage function (50).
[0235] The Management function (30) is a function that supervises the operation of an AI / ML model or an AI / ML function. Additionally, the Management function (30) may make decisions to ensure appropriate inference operations based on data received from the Data Collection function (10) (i.e., Monitoring Data (12)) and / or data received from the Inference function (40) (i.e., Inference Output (41)).
[0236] Management Instruction (32) is information required as input to manage the Inference function (40). The relevant information may include the selection / (de)activation / switching of an AI / ML model or an AI / ML-based function, and may also include a fallback to a non-AI / ML operation (i.e., not relying on the inference process).
[0237] A Model Transfer / Delivery Request (33) can be used to request model(s) from Model Storage (50).
[0238] Performance Feedback / Retraining Request (31) refers to information required as input to Model Training function (20) (e.g., for the purpose of retraining or updating the model).
[0239] The inference function (40) is a function that provides output from the process of applying an AI / ML model or AI / ML function using data (i.e., inference data (13)) provided by the data collection (10) as input. Data preparation (e.g., data preprocessing and cleaning, formatting and transformation) may also be performed based on the inference data (13) delivered by the data collection (10). If necessary, the inference function (40) may also perform data preparation (e.g., data pre-processing and cleaning, forming and transformation) based on the inference data (13) provided by the data collection function (10).
[0240] Inference Output (41) is data used in the Management function (30) to monitor the performance of an AI / ML model or AI / ML function. Inference Output (41) may include the inference output of an AI / ML model generated by the Inference function (30), and the details of the inference output may vary depending on the use case.
[0241] The Model Storage function (50) is a function that stores a trained / updated model that can be used to perform the Inference function (40). The Model Storage function (50) exemplified in FIG. 5 can be used as a reference point (if any) applicable to protocol termination, model transmission / delivery, and related processes. Additionally, the Model Storage function (50) is an example and is not intended to restrict the storage location of the actual AI / ML model and may be omitted.
[0242] Model Transfer / Delivery (51) is used to transfer an AI / ML model to an inference function.
[0243] Cooperation levels can be defined as follows based on the capability of AI / ML functions among multiple nodes, and variations resulting from the combination of multiple levels or the separation of any one level are also possible.
[0244] Cat 0a) No collaboration framework: AI / ML algorithms are based on pure implementation and do not require changes to the wireless interface.
[0245] Cat 0b) This level corresponds to a framework that involves a wireless interface modified to fit efficient implementation-based AI / ML algorithms but without cooperation.
[0246] Cat 1) Inter-node support is involved to improve the AI / ML algorithms of each node. For example, this applies when a specific node receives support from other nodes (for training, adaptation, etc.) and vice versa. At this level, model exchange between network nodes is not required.
[0247] Cat 2) Collaborative AI / ML tasks can be performed among multiple nodes. This level requires the exchange of AI / ML model commands or network nodes.
[0248] FIG. 5 is a diagram illustrating an overall functional framework for an AI / ML model, and all functions and / or all data / information / command signals illustrated in FIG. 5 may not be performed within a specific node, and only some may be performed.
[0249] AI / ML models can be classified into one-side models and two-side models depending on whether training and / or inference are performed on a single node or jointly / sequentially on multiple nodes.
[0250] A one-side model can refer to an AI / ML model where inference is performed entirely by a single node (e.g., a terminal or a network). Here, the training of the AI / ML model can also be performed entirely by a single node. The training and inference of the AI / ML model may be performed by the same node, or they may be performed by different nodes.
[0251] A two-side model can refer to an AI / ML model in which joint inference is performed across multiple nodes (e.g., terminals and networks). Joint inference means that inference is performed collaboratively across multiple nodes; for example, the first part of the inference may be performed by the first node, and the remainder by the second node. Two-side models can be classified into various types as follows, depending on the training method of the AI / ML model.
[0252] - First type: An AI / ML model can be trained on a single node. In this case, joint training can be performed. The trained model can then be distributed to other nodes / entities.
[0253] - Second type: Joint training of AI / ML models can be performed on multiple nodes / entities (e.g., networks and terminals). Joint training can mean that model generation (e.g., CSI generation) and model reconstruction (CSI compression by sub-use cases) are trained in the same loop for forward activation and backward gradient. In this type, joint training can include both simultaneous training (i.e., model generation training and model reconstruction training are performed simultaneously) and sequential training (i.e., model reconstruction training is performed after model generation training).
[0254] - Third Type: Separate training of AI / ML models can be performed at multiple nodes (e.g., networks and terminals). Separate training may mean that training starts sequentially at one node and continues at another node. In this case, if the first node performs the AI / ML model first and shares the training data with the second node, the second node can perform the AI / ML model using the shared training data. For example, training for the CSI generation part may be performed by the terminal, while CSI reconstruction may be performed by the network.
[0255] FIG. 6 illustrates a communication procedure between a first node (e.g., terminal) and a second node (e.g., base station) to which an AI / ML model is applied.
[0256] The operations described below may be explained / interpreted based on an AI / ML model as shown in FIG. 6 below, even without separate mention (i.e., without explicit mention of being by / based on / for an AI / ML model). Furthermore, unless specifically limited, the AI / ML model may correspond to a one-side model in which inference is performed entirely by a single node or a two-side model in which joint inference is performed by multiple nodes.
[0257] First signaling (601): In the following description, the signaling (e.g., information / data / channel / signal, etc.) or set of signaling between a specific node (e.g., terminal, network, etc.) and another node may be interpreted as the signaling or set of signaling of the first signaling (601) used to perform an operation based on an AI / ML model, even if not otherwise mentioned. For example, it may correspond to training data for training (i.e., creation and / or reconstruction) of the AI / ML model of FIG. 5, or to inference data used for inference of the AI / ML model, or to feedback for the AI / ML model. If, in this specification, signaling between nodes is not required prior to an operation based on an AI / ML model, the first signaling (601) may be omitted. In this specification, if a one-side model is used, the unidirectional / bidirectional signaling (set) in this specification may correspond to the signaling of the first signaling (601). Additionally, when a two-side model is used in the present specification, unidirectional / bidirectional signaling in the present specification may correspond to the first signaling (601), and repetitive signaling operation may also correspond to the first signaling (601).
[0258] For example, in AI / ML model-based beam management, when a base station predicts (i.e., infers) high-quality beam(s) based on an AI / ML model, the base station can receive quality / intensity information for multiple beams from the terminal. Additionally, when a terminal predicts (i.e., infers) high-quality beam(s) based on an AI / ML model, the terminal can receive multiple beams from the base station.
[0259] AI / ML model-based operation (602): In the following description, an operation (e.g., computation, selection, prediction, etc.) at a specific node (e.g., terminal, network, etc.) or a common operation (e.g., computation, selection, prediction, etc.) at multiple nodes (e.g., terminal, network, etc.) may correspond to an AI / ML model-based operation (602) based on one or more functions in the functional framework of the AI / ML model, even without separate mention. For example, it may correspond to the training (i.e., creation and / or reconstruction) of the AI / ML model of FIG. 5 or to the inference of the AI / ML model. When a one-side model is used, an operation performed by a single node in this specification may correspond to an AI / ML model-based operation (602), and when a two-side model is used, a common operation performed by multiple nodes in this specification may correspond to an AI / ML model-based operation (602).
[0260] For example, in an AI / ML model-based BM, a base station can predict (i.e., infer) high-quality beam(s) based on an AI / ML model by using quality / intensity information for multiple beams received from a terminal as inference data. Additionally, a terminal can measure multiple beams received from a base station and predict (i.e., infer) high-quality beam(s) based on an AI / ML model by using the measurement results as inference data.
[0261] Second signaling (603): In the following description, signaling (e.g., information / data / channel / signal, etc.) or a set of signaling between a specific node (e.g., terminal, network, etc.) and another node may be interpreted as the second signaling (603) or a set of signaling generated as a result of an operation based on an AI / ML model, even without separate mention. For example, it may correspond to the output resulting from the inference of the AI / ML model of FIG. 5. If signaling between nodes is not required as a result of an operation based on an AI / ML model in this specification, the second signaling (603) may be omitted. If a one-side model is used in this specification, the unidirectional / bidirectional signaling (set) in this specification may correspond to the second signaling (603). Additionally, when a two-side model is used in this specification, unidirectional / bidirectional signaling in this specification may correspond to the second signaling (603), and repetitive signaling operation may also correspond to the second signaling (603).
[0262] For example, in an AI / ML model-based BM, the base station may transmit beam(s) predicted based on the AI / ML model as candidates to the terminal so that the terminal can determine the optimal beam. Additionally, the terminal may report the beam(s) predicted based on the AI / ML model to the base station to request the base station to transmit candidate beams as candidates for determining the optimal beam.
[0263] THz communication
[0264] Data transmission rates can be increased by expanding bandwidth. This can be achieved by using sub-THz communication with wide bandwidth and applying advanced large-scale MIMO technology. THz waves, also known as sub-millimeter radiation, generally refer to a frequency band between 0.1 THz and 10 THz with corresponding wavelengths ranging from 0.03 mm to 3 mm. The 100 GHz–300 GHz band range (Sub-THz band) is considered the primary portion of the THz band for cellular communication. Adding the Sub-THz band to the mmWave band increases 6G cellular communication capacity. Among the defined THz bands, the 300 GHz–3 THz band is located in the far-infrared (IR) frequency band. Although the 300 GHz–3 THz band is part of the broadband, it lies at the boundary of the broadband and immediately following the RF band. Therefore, this 300 GHz–3 THz band exhibits similarities to RF.
[0265] FIG. 7 illustrates an electromagnetic spectrum according to one embodiment of the present disclosure. The embodiment of FIG. 7 may be combined with various embodiments of the present disclosure. Key characteristics of THz communication include (i) a widely available bandwidth to support very high data transmission rates, and (ii) high path loss occurring at high frequencies (highly directional antennas are indispensable). The narrow beam width generated by highly directional antennas reduces interference. The small wavelength of THz signals allows a much larger number of antenna elements to be integrated into devices and BSs operating in this band. This enables the use of advanced adaptive array techniques that can overcome range limitations.
[0266] Transmitting system information (i.e., information related to the attributes, characteristics, and / or capabilities of the BS required to use the service, etc.) (e.g., MIB, SIB, etc.) in the THz frequency band can be inefficient because, in the case of high frequency bands, beam sweeping must be performed more frequently to cover the entire area of the cell as the beam width becomes narrow. In particular, transmitting system information in this manner is even more inefficient when there are not many users in the cell. Accordingly, a system information transmission procedure as shown in FIG. 8 below may be used.
[0267] FIG. 8 illustrates an example of a procedure for transmitting system information for THz communication to which the present disclosure applies. Although this example is written with THz conditions in mind, it is also applicable to 6G communication environments where THz is not applied. Furthermore, the procedure exemplified in FIG. 8 can be combined with various embodiments of the present disclosure described below. For example, the embodiments described below may be performed based on the system information obtained by the procedure exemplified in FIG. 8.
[0268] Referring to FIG. 8, the base station can transmit system information of cell #1 through cell #2 (801). That is, the base station provides at least two cells, cell #1 uses the THz frequency band, and cell #2 uses a frequency band other than the THz frequency band. Here, the system information may include at least one piece of information / state / parameter / setting generated at the higher layer and the physical layer, respectively. For example, at least one piece of information / state / parameter / setting generated at the higher layer may include at least one of SFN, control information setting for SIB1 (e.g., PDCCH configuration for SIB1, etc.), information related to cell selection / entry (e.g., cell barring, cell re-selection, etc.), and subcarrier spacing, and at least one piece of information / state / parameter / setting generated at the physical layer may include at least one of SFN, half frame indicator, and SSB index. However, this is merely an example, and system information may include information, status, parameters, and settings related to Cell #1 / Cell #2 generated at various types of physical layers / upper layers. To this end, as an example, Cell #1 and Cell #2 may have a secondary cell and primary cell relationship.
[0269] The UE can obtain synchronization for cell #1 (803). Synchronization can be obtained by detecting a synchronization signal. Generally, synchronization is obtained prior to receiving system information, but since the system information for cell #1 is received in cell #2, synchronization for cell #1 can be obtained after receiving system information. For example, the UE can obtain synchronization based on system information. However, unlike FIG. 8, synchronization may be obtained before step 801 according to other examples.
[0270] The UE can transmit a signal to connect to Cell #1 (805). For example, the signal may include information for connecting to Cell #1 (e.g., a random access preamble). The structure of the signal and the resources for transmitting the signal (e.g., a channel) can be identified through system information. Subsequently, the UE and the base station can perform a connection procedure to Cell #1 and perform communication (807). In this process, operations according to various embodiments described below may be performed.
[0271] The procedure described with reference to FIG. 8 may be performed when the UE (801) first connects to cell #1 of the base station. Alternatively, a similar procedure may be performed when the UE (801) handovers to cell #1 of the base station. However, in the case of a handover, the system information of cell #1 may be received from a cell of a different base station rather than cell #2 of the base station.
[0272] Communication in the THz band is expected to experience severe path loss, and to overcome this, terminals and base stations must use very sharp beams. The use of sharp beams means that terminals and base stations must perform beam control along with beamforming, and the number of beams used becomes very large. Therefore, it takes a very long time to align the transmit and receive beams between the base station and the terminal. In addition, if the beam alignment between the base station and the terminal is misaligned due to the movement of the terminal, time is frequently required to realign the beams, which may result in an unstable link. Accordingly, a beam management procedure as shown in Fig. 9 below may be used.
[0273] FIG. 9 illustrates a beam management procedure applicable to the present disclosure. FIG. 9 illustrates an example of a procedure for searching and / or selecting beams for THz communication, but is not limited to a THz environment and is applicable to a 6G communication environment. Additionally, the procedure exemplified in FIG. 9 may be combined with various embodiments of the present disclosure described below. Here, a beam may be interpreted as 'spatial (configuration) information', 'spatial domain filter', 'spatial domain transmission filter', 'spatial domain reception filter', or / and a term having an equivalent technical meaning capable of distinguishing a beam (e.g., Reference signal, SSB (Synchronization Signal Block) Index, TRP (transmission reception point), panel, cell, TP (transmission point), base station, control resource-related information (e.g., CORESET (control resource set)-related information, etc.).
[0274] Referring to FIG. 9, the base station can configure resources for beam management (901). Here, the resources may include at least one of time-frequency resources, channels, and spatial resources (e.g., antenna ports). For example, the base station may utilize a beam search signal (BSS) that is spatially separated from existing downlink signals / channels for beam search. Here, the BSS may be transmitted based on a dedicated port for beam search. The dedicated port may be a port different from the port for transmitting existing downlink signals / channels (e.g., synchronization signals (e.g., SSB, etc.), data channels (e.g., PDSCH, etc.)). BSS is a term defined for convenience of explanation, and the technical concept according to the present embodiment is not limited to the term BSS itself. That is, a signal transmitted based on a dedicated port defined / configured for beam search may be included in the technical concept according to the present embodiment.
[0275] The base station can transmit measurement signals using multiple transmission beams (903). For example, the measurement signals may include at least one of a reference signal and a synchronization signal. At this time, the measurement signals may be transmitted as many times as the number of beams required for measurement, and may be transmitted using a multi-beam transmission method that forms multiple beams simultaneously to reduce sweeping time. Here, multi-beam transmission may be performed based on at least one of a multi-panel, a sub-array, and a true time delay (TTD).
[0276] The UE can transmit a feedback signal to the base station (905). The feedback signal indicates at least one beam selected by the UE. The UE can select at least one preferred beam based on the received measurement signals. The UE and the base station can perform communication (907). At this time, the UE and the base station can perform communication using the previously selected beam. If channel reciprocity is established, the UE's transmission beam can also be determined through operations 903 and 905, so the UE's transmission can also be performed using the beam selected in operation 905. If channel reciprocity is not established, a procedure including the transmission of the UE's measurement signals and the transmission of the base station's feedback signal may be performed first to determine the UE's transmission beam. In operation 907, operations according to various embodiments described below may be performed.
[0277] Integrated Sensing and Communication (ISAC)
[0278] Wireless sensing is a technology that utilizes radio frequencies to determine the instantaneous linear velocity, angle, and distance (range) of an object, thereby obtaining information about the characteristics of the environment and / or objects within that environment. Since radio frequency sensing capabilities do not require connecting to objects via devices within a network, they can provide services for determining object locations without the need for devices. The ability to obtain range, velocity, and angle information from radio frequency signals can provide a wide range of new functions, such as various object detection, object recognition (e.g., vehicles, humans, animals, UAVs), and high-precision localization, tracking, and activity recognition. Wireless sensing services can provide information to various industries (e.g., unmanned aerial vehicles, smart homes, V2X, factories, railways, public safety, etc.) that enable applications such as intruder detection, assisted vehicle steering and navigation, trajectory tracking, collision avoidance, traffic management, and health and traffic management. In some cases, wireless sensing may utilize non-3GPP type sensors (e.g., radar, cameras) to further support 3GPP-based sensing. For example, the operation of a wireless sensing service, that is, the sensing operation, may depend on the transmission, reflection, and scattering processing of wireless sensing signals. Therefore, wireless sensing can provide an opportunity to enhance existing communication systems from communication networks into wireless communication and sensing networks.
[0279] FIG. 10 illustrates an example of a sensing operation according to an embodiment of the present disclosure. The embodiment of FIG. 10 may be combined with various embodiments of the present disclosure. Specifically, FIG. 10(a) illustrates an example of sensing using a sensing receiver and a sensing transmitter located at the same position (e.g., monostatic sensing), and FIG. 10(b) illustrates an example of sensing using a separated sensing receiver and a sensing transmitter (e.g., bistatic sensing).
[0280] For example, in a wireless communication system based on a 6G network of the present specification, referring to FIG. 10(a), the sensing transmitter and the sensing receiver may be configured to be included in a single base station (i.e., the same base station) or a single terminal (i.e., the same terminal). Alternatively, referring to FIG. 10(b), the sensing transmitter and the sensing receiver may be configured to be included in different base stations, in different terminals, or in a terminal and a base station, respectively.
[0281] In this regard, based on whether the sensing transmitter and the sensing receiver are each included in a base station or a terminal, the following six types of sensing modes can be defined.
[0282] - Mode 1: A mode in which the sensing transmitter and sensing receiver are included in a single base station (e.g., base station-based sensing mode in monostatic mode)
[0283] - Second mode: A mode in which the sensing transmitter is included in the first base station and the sensing receiver is included in a second base station different from the first base station (e.g., base station-based sensing mode in bistatic mode)
[0284] - 3rd Mode: A mode in which the sensing transmitter is included in the base station and the sensing receiver is included in the terminal (e.g., base station-terminal sensing mode)
[0285] - 4th Mode: A mode in which the sensing transmitter is included in the terminal and the sensing receiver is included in the base station (e.g., terminal-base station sensing mode)
[0286] - 5th Mode: A mode in which the sensing transmitter and the sensing receiver are contained in a single terminal (e.g., terminal-based sensing mode in monostatic mode)
[0287] - 6th mode: A mode in which the sensing transmitter is included in the first terminal and the sensing receiver is included in a second terminal different from the first terminal (e.g., terminal-based sensing mode in bistatic mode)
[0288] In a wireless communication system based on a 6G network of the present specification, one or more of the six types of sensing modes described above may be utilized independently or in combination.
[0289] In relation to the sensing operation in FIG. 10, the sensing transmitter may transmit a sensing signal for sensing one or more objects (and / or the environment surrounding the objects). For example, the sensing signal may correspond to a radio (frequency) signal defined to be transmittable by a base station / terminal in a wireless communication system based on a 6G network of the present specification. The sensing receiver may receive a signal that is scattered / reflected by one or more objects (and / or the environment surrounding the objects) from the sensing signal transmitted from the sensing transmitter. In the sensing receiver, sensing data may be derived from the scattered / reflected signal, and sensing results may be generated / obtained through processing of the sensing data. Here, the sensing result may include characteristic information (e.g., location, distance, speed, angle, etc.) about one or more objects (and / or the environment surrounding the objects). The sensing result thus generated / acquired may be utilized for wireless sensing services (e.g., detection, tracking, etc. of objects and / or environments) provided by a wireless communication system based on a 6G network of the present specification, or may be provided / disclosed to a trusted third party.
[0290] Additionally, the sensing operation in FIG. 10 is described using a representative example of operation in a wireless communication system based on a 6G network, but it can be extended and applied to cases where terminals / base stations / signals based on previous generations (e.g., 4G, 5G, etc.) networks are utilized.
[0291] Additionally, with respect to the wireless sensing described in this specification, in a wireless communication system based on a 6G network of this specification, time / frequency resources for sensing operations and time / frequency resources for general communication (e.g., UL / DL / sidelink-based communication, etc.) may be scheduled / configured separately.
[0292] FIG. 11 illustrates a time / frequency resource for a sensing operation according to one embodiment of the present specification. The embodiment of FIG. 11 may be combined with various embodiments of the present disclosure.
[0293] Referring to FIG. 11, the time / frequency resources (hereinafter, sensing resources) for the aforementioned sensing operation (e.g., sensing operation based on FIG. 10) can be set / assigned separately from the time / frequency resources (hereinafter, communication resources) for general communication.
[0294] For example, as illustrated in FIG. 11, sensing resources may be configured / assigned in units of symbols in the time domain and / or in units of resource blocks in the frequency domain. Resources other than those configured / assigned to the sensing resources may be utilized as resources for general communication. That is, sensing resources and communication resources may be configured / assigned based on time-division multiplexing (TDM) and / or frequency-division multiplexing (FDM) methods in terms of base station / terminal operation. Additionally or alternatively, unlike that illustrated in FIG. 10, sensing resources may be configured / assigned based on other units in the time domain (e.g., slot, frame, absolute time (ms, us), etc.) and / or other units in the frequency domain (e.g., subcarrier, carrier, absolute frequency (MHz, GHz), etc.).
[0295] Additionally or alternatively, in relation to the setup / allocation / scheduling of resources for general communication described herein, it may be necessary to consider the relationship between said resources and the aforementioned sensing resources. For example, when setting / allocating resources for general communication according to the embodiments of the present disclosure, said resources may be set / allocated to rate-match or puncturing resource areas corresponding to the sensing resources. For example, when scheduling resources for general communication according to the embodiments of the present disclosure, said resources may be scheduled so as not to overlap with resource areas corresponding to the sensing resources. If resources for general communication and resource areas corresponding to the sensing resources are set / allocated / scheduled to overlap according to the embodiments of the present disclosure, either one or both operations may be dropped, skipped, or postponed based on priority, predefined rules, etc. That is, in the embodiments of this specification, resources related to general communication (e.g., resources for signals / channels related to UL / DL / Sidelink-based data / control, etc.) may be configured / assigned / scheduled so as not to overlap with the aforementioned sensing resources.
[0296] Additionally, various channel modeling methods may be applied in relation to the wireless sensing described herein. Channel modeling related to sensing may mean constructing a path for transmitting and receiving sensing signals and / or scattered / reflected signals by considering the object to be sensed and / or the environment to which the object belongs. Since channel modeling may be related to the performance / requirements of sensing in a wireless communication system, it may be an important matter for verifying the validity of the sensing function.
[0297] Channels related to sensing can be classified into channels between an object (e.g., target of interest) and a sensing transmitter / receiver, and channels between the environment to which the object belongs and a sensing transmitter / receiver. In this regard, channel modeling related to sensing can be classified based on the sensing mode (e.g., the six types of modes mentioned above), whether it is an object or an environment, and / or sensing scenarios. For example, channel modeling for a target in a base station / terminal-based monostatic sensing mode, channel modeling for a target in a base station / terminal-based bistatic sensing mode, channel modeling for an environment in a base station / terminal-based monostatic sensing mode, and channel modeling for an environment in a base station / terminal-based bistatic sensing mode can be optimized and configured differently. For example, when various sensing scenarios are classified, they can be divided into channel modeling for detection, location, and tracking scenarios, channel modeling for motion recognition, and channel modeling for imaging / environment reconstruction scenarios. Additionally, channel modeling related to sensing may be based on statistical channel modeling techniques and / or deterministic channel modeling techniques. For example, modeling for sensing in a wireless communication system based on a 6G network of this specification may be based on stochastic geometry channel modeling techniques and / or hybrid with ray tracing channel modeling techniques. Here, the stochastic geometry channel model may be based on various statistical characteristics of the channel state. Furthermore, the hybrid channel model may be based on both ray tracing techniques and stochastic techniques.In the case of a hybrid approach, channels for objects requiring high accuracy and consistency (e.g., targets of interest) can be modeled using ray tracing techniques, while channels for the environment can be modeled using probabilistic techniques.
[0298] FIG. 12 illustrates a procedure related to a sensing operation according to one embodiment of the present specification. The embodiment of FIG. 12 may be combined with various embodiments of the present disclosure.
[0299] For example, in a wireless communication system based on a 6G network of the present specification, in the case of a sensing operation in which a terminal participates, the base station may need to verify (1205) the terminal's capability for the sensing operation. In this regard, the terminal may be configured to report capability information to the base station regarding whether it supports the sensing operation. Additionally, or alternatively, if the terminal is defined in advance in the specification as supporting the sensing operation, the procedure may be omitted. Furthermore, in the case of a sensing operation in which only the base station participates, the base station may be configured to report capability information regarding whether it supports the sensing operation to the entity setting / controlling its sensing operation (e.g., a network entity at the upper level / layer of the base station).
[0300] For example, a base station may perform signaling with a terminal to exchange configuration information related to a sensing operation. For example, the base station may set / instruct the terminal information regarding the mode of the sensing operation (e.g., based on the six types of modes mentioned above), the subject of the sensing operation (e.g., a sensing transmitter, a sensing receiver), the resource of the sensing operation (e.g., a sensing resource as shown in FIG. 11), the target of utilization of the sensing result (e.g., a type of wireless sensing service based on a 6G network, a trusted third party), and channel modeling for sensing (e.g., a channel between the base station / terminal and an object / environment) (1210). For example, the base station may receive such information from a network entity at the upper level / layer of the base station.
[0301] For example, a base station and / or terminal may perform a sensing operation on information set / instructed (1215). For example, the base station and / or terminal may perform procedures such as transmitting a sensing signal as in FIG. 9 described above, receiving scattered / reflected signals, deriving sensing data, obtaining a sensing result through processing the sensing data, and providing the sensing result, as a role of a sensing transmitter and / or sensing receiver. For example, in the operation of the base station / terminal described in this specification, the sensing result provided through the sensing operation may be utilized.
[0302] Data transmission and HARQ-ACK process
[0303] FIG. 13 illustrates the process of receiving a PDSCH and transmitting an ACK / NACK therefor. Referring to FIG. 13, the terminal can detect a PDCCH in slot #n. Here, the PDCCH includes downlink scheduling information (e.g., DCI format 1_0, 1_1), and the PDCCH represents a DL assignment-to-PDSCH offset (K0) and a PDSCH-HARQ-ACK reporting offset (K1). For example, DCI format 1_0, 1_1 may include the following information.
[0304] - Frequency domain resource assignment: Represents the set of RBs assigned to PDSCH
[0305] - Time domain resource assignment: Indicates K0 (e.g., slot offset), the starting position of the PDSCH within slot #n+K0 (e.g., OFDM symbol index), and the length of the PDSCH (e.g., number of OFDM symbols). As described above, the row index of the pdsch-TimeDomainAllocationList provided common to the terminal or specific to the terminal may be indicated through the TDRA field.
[0306] - PDSCH-to-HARQ_feedback timing indicator: Indicates K1
[0307] - HARQ process number (4 bits): Represents the HARQ process ID (Identity) for data (e.g., PDSCH, TB)
[0308] - PUCCH resource indicator (PRI): Indicates the PUCCH resource to be used for UCI transmission among multiple PUCCH resources within the PUCCH resource set.
[0309] Subsequently, the terminal receives a PDSCH from slot #(n+K0) according to the scheduling information of slot #n, and when the reception of the PDSCH ends in slot #n1 (where, n+K0 ≤ n1), it can transmit a UCI via a PUCCH in slot #(n1+K1). Here, the UCI may include a HARQ-ACK response to the PDSCH. In FIG. 13, for convenience, it was assumed that the SCS for the PDSCH and the SCS for the PUCCH are identical and that slot #n1 = slot #n+K0, but the present invention is not limited thereto. If the SCSs are different, K1 may be indicated / interpreted based on the SCS of the PUCCH.
[0310] If the PDSCH is configured to transmit up to 1 TB, the HARQ-ACK response may consist of 1 bit. If the PDSCH is configured to transmit up to 2 TB, the HARQ-ACK response may consist of 2 bits if spatial bundling is not configured, and 1 bit if spatial bundling is configured. If the time for transmitting HARQ-ACKs for multiple PDSCHs is specified as slot #(n+K1), the UCI transmitted at slot #(n+K1) includes HARQ-ACK responses for multiple PDSCHs.
[0311] Whether a terminal must perform spatial bundling for a HARQ-ACK response can be configured per cell group (e.g., RRC / upper layer signaling). For example, spatial bundling can be configured individually for each HARQ-ACK response transmitted via PUCCH and / or HARQ-ACK response transmitted via PUSCH.
[0312] Spatial bundling may be supported when the maximum number of TBs (or codewords) that can be received (or scheduled via 1 DCI) at once in the corresponding serving cell is 2 (or more than 2) (e.g., when the upper layer parameter maxNrofCodeWordsScheduledByDCI corresponds to 2-TB). Meanwhile, more than 4 layers may be used for 2-TB transmission, and up to 4 layers may be used for 1-TB transmission. Consequently, if spatial bundling is configured in the corresponding cell group, spatial bundling may be performed on serving cells within the cell group for which more than 4 layers are scheduleable. On the corresponding serving cell, a terminal that intends to transmit a HARQ-ACK response via spatial bundling may generate a HARQ-ACK response by performing a (bit-wise) logical AND operation on the A / N bits of multiple TBs.
[0313] For example, assuming that a terminal receives a DCI scheduling 2-TB and receives 2-TB through a PDSCH based on the said DCI, the terminal performing spatial bundling can generate a single A / N bit by performing a logical AND operation on the first A / N bit for the first TB and the second A / N bit for the second TB. Consequently, if both the first TB and the second TB are ACK, the terminal reports the ACK bit value to the base station, and if either TB is NACK, the terminal reports the NACK bit value to the base station.
[0314] For example, if only 1-TB is actually scheduled on a serving cell configured to receive 2-TB, the terminal can generate a single A / N bit by performing a logical AND operation between the A / N bit for the 1-TB and the bit value 1. As a result, the terminal reports the A / N bit for the 1-TB to the base station as is.
[0315] Multiple parallel DL HARQ processes exist in the base station / terminal for DL transmission. These multiple parallel HARQ processes enable DL transmission to be performed continuously while waiting for HARQ feedback regarding the successful or unsuccessful reception of the previous DL transmission. Each HARQ process is associated with a HARQ buffer of the MAC (Medium Access Control) layer. Each DL HARQ process manages state variables regarding the number of transmissions of MAC PDUs (Physical Data Blocks) in the buffer, HARQ feedback for MAC PDUs in the buffer, and the current redundancy version. Each HARQ process is distinguished by its HARQ process ID.
[0316] FIG. 14 illustrates a PUSCH transmission process. Referring to FIG. 14, the terminal can detect PDCCH in slot #n. Here, PDCCH includes uplink scheduling information (e.g., DCI format 0_0, 0_1). DCI format 0_0, 0_1 may include the following information.
[0317] - Frequency domain resource assignment: Indicates the set of RBs assigned to PUSCH
[0318] - Time domain resource assignment: Indicates slot offset K2, the starting position (e.g., symbol index) and length (e.g., number of OFDM symbols) of PUSCH within the slot. The starting symbol and length can be indicated via SLIV (Start and Length Indicator Value).
[0319] Subsequently, the terminal can transmit PUSCH at slot #(n+K2) according to the scheduling information of slot #n. Here, PUSCH includes UL-SCH TB.
[0320]
[0321] In the existing system, a single (serving) cell consists of only one carrier (in the case of FDD, it consists of a single carrier pair consisting of one DL carrier and one UL carrier), and for a single cell at a single time (e.g., one symbol or one slot interval), only one PDSCH in the case of DL and one PUSCH in the case of UL can be scheduled.
[0322] Meanwhile, in future 6G systems, a multi-carrier serving cell structure comprising a single (serving) cell with multiple carriers (e.g., N_c) may be considered for the purpose of reducing the DCI overhead required for PDSCH / PUSCH (referred to as "PXSCH" for convenience) scheduling and processing, and reducing the capability of terminals, by minimizing the energy saving effect of the base station by minimizing UE-common signal / channel transmission that is periodically broadcast (for each cell), and reducing the capability of terminals. Hereinafter, the multi-carrier serving cell is referred to as an "MC (multi-carrier) cell" for convenience, but is not limited thereto.
[0323] However, not all terminals supporting such MC cell-based operations may be implemented to simultaneously process N_c carrier PXSCH (or TB) (on the MC cell) (e.g., channel coding, channel estimation, etc.), and configuring to always schedule N_c carrier PXSCH (or TB) through a single DCI may increase unnecessary DCI overhead.
[0324] In particular, as the bandwidth of the carriers constituting the MC cell decreases (below a certain level), the aforementioned terminal capability and DCI overhead issues may become more pronounced. For example, if a terminal capable of processing one PXSCH (or TB) across a frequency on a single (wideband) carrier with a maximum bandwidth of 80 MHz requires the capability to simultaneously process two PXSCHs (or TBs) to perform data transmission and reception through an MC cell composed of two (narrowband) carriers with a bandwidth of 40 MHz, higher processing complexity may be incurred in data transmission and reception through the MC cell from the terminal's perspective, even though the total bandwidth remains the same. Additionally, from the base station's perspective, greater DCI overhead may be incurred in data scheduling on the MC cell.
[0325] Therefore, taking this into account, it may be necessary to limit the number of PXSCH (or TB) that can be simultaneously scheduled through MC cells (in the form of FDM at a single time point (e.g., symbol or slot)) to a maximum of N_t (≤ N_c).
[0326] In the following, a method for configuring a DCI for scheduling PXSCH transmission on an MC cell as described above and related terminal operations are proposed. Within the DCI payload, a specific DCI field may be composed of N_t sub-fields or N_c sub-fields. When a specific DCI field is composed of N_t sub-fields, each sub-field may correspond to / apply to each (different) PXSCH (or TB), and when a specific DCI field is composed of N_c sub-fields, each sub-field may correspond to / apply to each (different) carrier.
[0327] Meanwhile, according to the proposed embodiments, N_c may mean the total number of carriers set within one MC cell (via RRC, etc.), the maximum number of carriers that can be simultaneously activated within one MC cell, or the maximum number of carriers that can be simultaneously scheduled within one MC cell (in the form of FDM at one time point (e.g., symbol or slot)). Additionally, in the proposed embodiments, a carrier may mean a carrier subgroup (composed of one or more carriers belonging to the same MC cell) set so that information / values indicated through the same FDRA subfield and / or the same MCS subfield (and / or the same TDRA parameter set defined below) are (commonly) applied.
[0328] Meanwhile, for a specific carrier subgroup, applying an FDRA value indicated by the same single FDRA subfield may mean applying the single FDRA value while continuously indexing all frequency resources (e.g., PRBs) within multiple carriers belonging to the carrier subgroup. Additionally, for a specific carrier subgroup, applying MCS (or TDRA) information / values indicated by the same single MCS subfield (or TDRA parameter set) may mean applying a single MCS (or TDRA) information / value in the same way to multiple carriers belonging to the carrier subgroup.
[0329] Basically, information regarding the number of carriers configured within the MC cell (e.g., N_c) and BW / SCS for each carrier, and information regarding the maximum number of PXSCH (or TB) that can be simultaneously scheduled on the MC cell (e.g., N_t) (so that they can be simultaneously transmitted and received in FDM form at one time) can be configured from the base station to the terminal. In this case, one time may mean one symbol or one slot, but is not limited thereto. Based on the information including the configured N_c and N_t values, a DCI payload for scheduling PXSCH transmission on the MC cell can be configured, and the size of the payload can be determined accordingly. For example, the DCI payload may include fields such as NDI / RV / HPI (HARQ process index) and FDRA / MCS / TDRA, but is not limited thereto.
[0330] Additionally, in the proposed embodiments, a plurality of carriers constituting a single MC cell based on a multi-carrier single (serving) cell structure may be replaced with a plurality of sub-bands or a plurality of (sub) BWPs configured within a single cell, a single carrier, a single system BW, or a single channel BW. Accordingly, in the proposed embodiments, a carrier (in the MCSC-based MC cell) may be replaced with a sub-band or a (sub) BWP (in the cell, carrier, system BW, or channel BW). Additionally, in the proposed embodiments, each of the plurality of carriers (in the MCSC-based MC cell), the plurality of sub-bands (in the cell, carrier, system BW, or channel BW), or the plurality of (sub) BWPs may be defined / configured / instructed to operate as an individual / independent RF chain and / or an individual / independent baseband processor / module, or defined / configured / instructed to operate as an individual / independent duplexing scheme and / or an individual / independent DL / UL symbol / slot type.
[0331]
[0332] NDI / RV / HPI Field
[0333] In the case of NDI / RV / HPI fields, each field within the DCI may consist of N_t subfields, and each of the N_t subfields in each NDI / RV / HPI field may individually indicate NDI / RV / HPI information / values for each of the N_t PXSCH (or TB). For example, the nth (indexed) subfield within each NDI / RV / HPI field may correspond to / apply to the nth (indexed) PXSCH (or TB) (among the total N_t PXSCH (or TB)).
[0334] If, for each PXSCH (or TB) index, one or more (e.g., up to N_s) PXSCH (or TB) are configured to be schedulable in TDM form (across multiple slots), each NDI / RV / HPI field within the DCI may be composed of N_s subfields for each PXSCH (or TB) index, and may be composed of a total of {N_t x N_s} subfields (for N_t PXSCH (or TB)).
[0335] In addition, when one or more (e.g., up to N_a) TBs are configured to be transmitted via SDM (Spatial Division Multiplexing) MIMO through a single PXSCH, each NDI / RV / HPI field within the DCI may be composed of N_a subfields for each PXSCH (index) and may be composed of a total of {N_t x N_a} subfields (for N_t PXSCHs).
[0336] In addition, for each PXSCH (also TB) index, up to N_s PXSCHs (or TBs) are configured to be scheduled in TDM form, and up to N_a TBs are configured to be transmitted via MIMO in SDM form through a single PXSCH, then each NDI / RV / HPI field within the DCI may have {N_s x N_a} subfields configured for each PXSCH (index), and (for N_t PXSCHs) may have a total of {N_t x N_s x N_a} subfields configured.
[0337]
[0338] FDRA / MCS field
[0339] For FDRA / MCS fields, within the DCI, Alt 1) each field may consist of N_t subfields, or Alt 2) each field may consist of N_c subfields. For example, if each field consists of N_t subfields, the nth (indexed) subfield within each FDRA / MCS field may correspond to / apply to the nth (indexed) PXSCH (or TB) (of the total N_t PXSCH (or TB)). Or, if each field consists of N_c subfields, the nth (indexed) subfield within each FDRA / MCS field may correspond to / apply to the nth (indexed) carrier (of the total N_c carriers). Additionally, the same or different Alt) methods may be applied between the FDRA field and the MCS field. When different Alt) methods are applied between the FDRA field and the MCS field, for example, Alt 1) may be applied to the FDRA field and Alt 2 to the MCS field, or vice versa.
[0340] In the case of Alt 1), specifically, information regarding the carrier (or carrier subgroup) to which each subfield within the FDRA / MCS field is applied may be indicated through the DCI (e.g., a specific field of the DCI) or pre-set through RRC, etc. The carrier to which each subfield is applied may refer to the carrier to which the FDRA / MCS information / value indicated through each subfield is applied. Additionally, since each subfield corresponds to / applies to each PXSCH (or TB), the carrier to which each subfield is applied may refer to the carrier corresponding to each PXSCH (or TB) index (i.e., to which each PXSCH (or TB) index signal is mapped). At this time, the information regarding the carrier (or carrier subgroup) may include, for example, the index of the carrier (or carrier subgroup), but is not limited thereto. The information regarding the carrier (or carrier subgroup) may be indicated through the DCI (e.g., a specific field of the DCI) or pre-set through RRC, etc.
[0341] For example, information regarding the carrier (or carrier subgroup) corresponding to / mapped for each PXSCH (or TB) index (i.e., to which each FDRA / MCS subfield applies) may be indicated via DCI. In this case, if an invalid or inapplicable carrier index / value is indicated for a specific PXSCH (or TB) index, or if no carrier index / value is indicated, the PXSCH (or TB) index may be treated / considered as unscheduled.
[0342] As another example, correspondence / mapping relationships between a PXSCH (or TB) index and a carrier (subgroup) index may be set in advance via RRC, and one of these correspondence / mapping relationships may be indicated via DCI. For convenience, the correspondence / mapping relationships between a PXSCH (or TB) index and a carrier (subgroup) index may be referred to as PXSCH-to-carrier mapping relationships, and multiple PXSCH-to-carrier mapping relationships may be set via RRC. A single PXSCH-to-carrier mapping relationship may be structured such that a corresponding carrier (subgroup) index is directly set for each PXSCH (or TB) index. Alternatively, depending on the embodiment, it may be structured such that it is set only in the form of a set of one or more carrier (subgroup) indexes, and a corresponding PXSCH (or TB) index is determined sequentially according to the size of each carrier (subgroup) index. Even in this case, if an invalid or inapplicable carrier index / value is specified for a specific PXSCH (or TB) index, or if no carrier index / value is specified, the PXSCH (or TB) index may be treated / considered as unscheduled.
[0343] As another example, the carrier (subgroup) index corresponding to each PXSCH (or TB) index may be indicated via DCI in the form of a bitmap consisting of N_c bits corresponding to each of the N_c carriers, and the corresponding PXSCH (or TB) index may be determined sequentially according to the size of the indicated carrier (subgroup) index. For example, the lowest carrier (subgroup) index indicated via the bitmap may correspond to the lowest PXSCH (or TB) index, and the second lowest carrier (subgroup) index may correspond to the second lowest PXSCH (or TB) index. In this case, among the N_c bits, the bit indicated as corresponding to the carrier mapped to PXSCH may be set to '1', and the number of bits set to '1' may be N_t or less. Accordingly, a carrier corresponding to each PXSCH (or TB) can be determined based on the positions of the bits set to '1' in the bitmap.
[0344] As another example, information regarding a carrier (subgroup) corresponding to / mapped to each of N_t PXSCH (or TB) indices (i.e., to which each of N_t FDRA / MCS subfields within DCI applies) can be semi-statically pre-configured via RRC, etc., and the information regarding the carrier (subgroup) may include the index of the carrier (subgroup). Additionally, as previously mentioned, information regarding a carrier (subgroup) corresponding to / mapped to each of N_t PXSCH (or TB) indices can be referred to as a PXSCH-to-carrier mapping relationship.
[0345] When the above-described Alt 1) method is applied, if an invalid FDRA value is indicated through the FDRA subfield corresponding to a specific PXSCH (or TB) index, or if the PXSCH (or TB) index is not indicated as a scheduling target through a specific field of DCI, the PXSCH (or TB) index may be treated / considered as not scheduled.
[0346] Meanwhile, in the case of Alt 2), PXSCH (or TB) related information mapped to / corresponding to each subfield within the FDRA / MCS field may be indicated via DCI (e.g., a specific field of DCI) or pre-set via RRC, etc. According to Alt 2), since each subfield corresponds to / maps to each carrier index, the PXSCH (or TB) mapped to / corresponding to each subfield may mean the PXSCH corresponding to each carrier index, that is, the PXSCH to which the signal generated by the FDRA / MCS information / value indicated through each subfield is mapped. At this time, the PXSCH (or TB) related information may include, for example, a PXSCH (or TB) index, but is not limited thereto.
[0347] For example, PXSCH (or TB) information corresponding to / mapped for each carrier index (i.e., to which each FDRA / MCS subfield applies) may be indicated via DCI. In this case, if a PXSCH (or TB) index / value that is invalid or inapplicable to a specific carrier index is indicated, or if no PXSCH (or TB) index is indicated, the carrier index may be treated / considered not to be used for PXSCH scheduling.
[0348] As another example, correspondence / mapping relationships between a carrier (subgroup) index and a PXSCH (or TB) index may be established in advance via RRC, and one of the correspondence / mapping relationships may be indicated via DCI. For convenience, the correspondence / mapping relationship between a carrier (subgroup) index and a PXSCH (or TB) index may be referred to as a "carrier-to-PXSCH mapping" relationship, and multiple carrier-to-PXSCH mapping relationships may be established via RRC, and one of the multiple carrier-to-PXSCH mappings may be indicated via DCI. A single carrier-to-PXSCH mapping may be structured such that a PXSCH (or TB) index corresponding to each carrier index is directly established. Alternatively, depending on the embodiment, it may be structured such that it is established only in the form of a set of one or more carrier indices, and a corresponding PXSCH (or TB) index is determined sequentially according to the size of each carrier index. Even in this case, if an invalid or inapplicable PXSCH (or TB) index / value is indicated for a specific carrier index, or if no PXSCH (or TB) index is indicated, the carrier index may be treated / considered not to be used for PXSCH scheduling.
[0349] As another example, the carrier (subgroup) index corresponding to each PXSCH (or TB) index can be indicated via DCI in the form of a bitmap consisting of N_c bits corresponding to each of the N_c carriers, and the corresponding PXSCH (or TB) index can be determined sequentially according to the size of the indicated carrier (subgroup) index. For example, the lowest carrier (subgroup) index indicated via the bitmap can be determined to correspond to the lowest PXSCH (or TB) index, and the second lowest carrier (subgroup) index can be determined to correspond to the second lowest PXSCH (or TB) index.
[0350] As another example, PXSCH (or TB) information corresponding to / mapped to each of N_c carrier indices (i.e., to each of N_c FDRA / MCS subfields within the DCI) can be semi-statically pre-configured through RRC, etc., and the PXSCH (or TB) information may include PXSCH (or TB) index information. Additionally, as described above, the PXSCH (or TB) information corresponding to / mapped to each of N_c carrier indices may be referred to as a carrier-to-PXSCH mapping.
[0351] Meanwhile, when the Alt 2) method is applied, if (all) invalid FDRA values are indicated through one or more FDRA subfields corresponding to a specific PXSCH (or TB) index, or if the PXSCH (or TB) index is not indicated as a scheduling target through a specific field of DCI, the PXSCH (or TB) index may be treated / considered as not scheduled.
[0352]
[0353] TDRA Field
[0354] In the case of TDRA fields, similar to existing methods, they may be composed of a single field within DCI without distinction of subfields. The number of combinations {K0 or K2, PXSCH SLIV, PXSCH mapping type} constituting each row in the TDRA table associated with the field may be Alt A) N_t. For convenience of explanation, the combinations {K0 or K2, PXSCH SLIV, PXSCH mapping type} will be referred to as "TDRA parameter sets" below. For example, among the N_t TDRA parameter sets constituting each row of the TDRA table, the nth TDRA parameter set may correspond to / apply to the nth PXSCH (or TB) (among the total N_t PXSCH (or TB)). At this time, the nth TDRA parameter set and the nth PXSCH (or TB) may each refer to the TDRA parameter set having the nth index and the PXSCH (or TB) having the nth index. Alternatively, according to an embodiment, the TDRA parameter sets constituting each row in the TDRA table may consist of Alt B) N_c. For example, among the N_c TDRA parameter sets constituting each row of the TDRA table, the nth TDRA parameter set may correspond to / apply to the nth carrier (among the total N_c carriers). As described above, the nth TDRA parameter set and the nth carrier may each refer to the TDRA parameter set having the nth index and the carrier having the nth index.
[0355] In the case of Alt A), specifically, in the TDRA table, information regarding the carrier (or carrier subgroup) to which the TDRA parameter set is applied in each row may be indicated through the DCI (e.g., a specific field of the DCI), pre-set through RRC, etc., or the information regarding the carrier (subgroup) indicated / set in Alt 1) may be applied in the same way. The carrier to which the TDRA parameter set is applied may refer to a carrier to which the information / value {K0 or K2, PXSCH SLIV, PXSCH mapping type} indicated through the TDRA parameter set is applied. Additionally, according to the method of Alt A), since the TDRA parameter set included in each row corresponds to each PXSCH, the carrier to which the TDRA parameter set is applied may refer to a carrier to which each PXSCH index signal is mapped. In addition, the carrier indicated / set in the above Alt 1) method may refer to a carrier corresponding / mapped to each PXSCH (or TB) index indicated / mapped in the above Alt 1) method, or a carrier applied to each FDRA / MCS subfield. For example, information regarding the carrier (subgroup) corresponding / mapped to the nth (indexed) PXSCH (or TB) may be applied to the nth (indexed) TDRA parameter set among the rows constituting the TDRA table.
[0356] Additionally, when the Alt A) method is applied, if invalid information / values are indicated through the TDRA parameter set corresponding to a specific PXSCH (or TB) index, the PXSCH (or TB) index may be treated / considered as not scheduled.
[0357] Additionally, in the case of the Alt B) method, specifically, for each row of the TDRA table, for the TDRA parameter set(s) constituting the row of the TDRA table, information related to the PXSCH (or TB) to which each TDRA parameter set is mapped / corresponding may be indicated via DCI, pre-set via RRC, etc., or the PXSCH (or TB) information indicated / set in the above Alt 2) may be applied in the same way. The PXSCH (or TB) to which each TDRA parameter set is mapped / corresponding may mean the PXSCH (or TB) to which the signal to which the information / value indicated via each TDRA parameter set is applied is mapped. Additionally, according to the Alt B) method, since each TDRA parameter set corresponds to each carrier index, the PXSCH (or TB) to which each TDRA parameter set is mapped / corresponding may mean the PXSCH (or TB) corresponding to each carrier index, or the PXSCH (or TB) to which the signal generated on each carrier index is mapped. Additionally, the PXSCH (or TB) indicated / set in the above Alt 2) method may refer to the PXSCH (or TB) indicated / set in the above Alt 2) method that corresponds / maps to each carrier index or is applied to each FDRA / MCS subfield. In this case, the PXSCH (or TB) related information may include, but is not limited to, a PXSCH (or TB) index. For example, the PXSCH (or TB) related information corresponding / mapped to the nth carrier (having an index) may be applied to the nth TDRA parameter set (having an index) within each row included in the TDRA table.
[0358] Additionally, when the Alt B) method is applied, if (all or part) invalid information / values are indicated through one or more TDRA parameter sets corresponding to a specific PXSCH (or TB) index, the PXSCH (or TB) index may be treated / considered as not scheduled.
[0359] In addition, if one or more (e.g., up to N_s) PXSCH (or TB) are configured to be schedulable in TDM form (across multiple slots) for each PXSCH (or TB) index, each TDRA parameter set (corresponding to each PXSCH (or TB) index or each carrier index) can be configured / set with N_s combinations of {K0 or K2, PXSCH SLIV, PXSCH mapping type}.
[0360] According to the proposed embodiments, when scheduling PXSCH transmission on an MC cell, a flexible and efficient PXSCH scheduling DCI (payload) can be configured by taking into account UE capability and / or DCI overhead, etc.
[0361] FIG. 15 is a flowchart illustrating the operation between a terminal and a base station according to one embodiment. FIG. 15 is an embodiment relating to at least some of the proposals described above, and the description of the proposals may be referenced even without separate mention.
[0362] Referring to FIG. 15, a terminal according to one embodiment may receive information regarding N_c and N_t from a base station (S1500). N_c may represent the number of carriers set within a cell. A cell may represent the aforementioned MC cell, and the MC cell may be composed of N_c carriers. In this case, the N_c carriers may include a plurality of subbands or a plurality of (sub) BWPs configured within a cell, a carrier, a system BW, or a channel BW, as described above. Additionally, at least one of the respective bandwidths or the sum of the total bandwidths of the N_c carriers may have a size less than or equal to a specific value. N_t may represent the maximum number of PXSCHs (e.g., PDSCH or PUSCH) that can be simultaneously scheduled in the frequency domain. In this case, PXSCH may be replaced with a TB (Transport Block), and PXSCH may represent PXSCH or TB below.
[0363] As described above, even if an MC cell is composed of N_c carriers, not all terminals may be implemented to be able to process N_c PXSCHs simultaneously on the MC cell, and configuring the DCI to always schedule N_c PXSCHs may be inefficient in terms of DCI overhead. In particular, when an MC cell is composed of N_c carriers (e.g., narrowband carriers) in which at least one of the individual bandwidths or the sum of the total bandwidths has a size of less than or equal to a specific value, in order to transmit and receive PXSCHs through the MC cell, even a terminal capable of processing PXSCHs mapped to a single carrier with a relatively wide bandwidth (e.g., wideband carrier) may be required to simultaneously process N_c PXSCHs mapped to N_c carriers in which at least one of the individual bandwidths or the sum of the total bandwidths has a size of less than or equal to a specific value. In this case, from the perspective of the terminal, transmitting and receiving PXSCH through the MC cell may cause higher processing complexity, and from the perspective of the base station, scheduling PXSCH on the MC cell may result in greater DCI overhead. Accordingly, in the proposed embodiment, the number of PXSCHs that can be simultaneously scheduled through the MC cell can be limited to N_t, and N_t may have a value less than or equal to N_c.
[0364] A terminal according to one embodiment may receive information regarding a mapping relationship between N_c carriers and N_t simultaneously schedulable PXSCHs from a base station (S1510). For example, the information regarding the mapping relationship may include information regarding a carrier corresponding to each of the N_t PXSCHs. The information regarding a carrier corresponding to each of the N_t PXSCHs may correspond to the aforementioned "PXSCH-to-carrier mapping" information. The N_t PXSCHs may be identified by N_t indices, and if the information regarding the mapping relationship includes information regarding a carrier corresponding to each of the N_t PXSCHs, the carrier corresponding to each of the N_t PXSCHs may mean a carrier corresponding to (or mapped to) each of the N_t PXSCH indices. Additionally, as described above, the carrier corresponding to each of the N_t PXSCHs may include one carrier or carrier subgroup, and the information regarding the carrier may include an index of the carrier or carrier subgroup, but is not limited thereto.
[0365] According to an embodiment, information regarding a mapping relationship may include information regarding a PXSCH corresponding to each of N_c carriers. The information regarding a PXSCH corresponding to each of N_c carriers may correspond to the aforementioned "carrier-to-PXSCH mapping" information.
[0366] Information regarding mapping relationships may be indicated through a specific field of the DCI or set through the RRC, etc. According to one embodiment, information regarding a carrier corresponding to each of N_t PXSCHs or a PXSCH corresponding to each of N_c carriers may be set semi-statically through the RRC. Alternatively, according to an embodiment, a plurality of mapping relationships may be pre-set through the RRC, and one of the plurality of mapping relationships may be indicated to the terminal through the DCI. Alternatively, according to an embodiment, the DCI may include a bitmap for indicating a carrier corresponding to each of N_t PXSCHs or a PXSCH corresponding to each of N_c carriers, and may transmit information regarding mapping relationships to the terminal through the bitmap. For example, if the information regarding mapping relationships includes information regarding a carrier corresponding to each of N_t PXSCHs, the bitmap may be composed of N_t bits, and each bit constituting the bitmap may correspond to each of N_t PXSCHs. In contrast, if the information regarding the mapping relationship includes information regarding PXSCH corresponding to each of N_c carriers, the bitmap may be composed of N_c bits, and each bit constituting the bitmap may correspond to each of N_c carriers.
[0367] A terminal according to one embodiment can receive Downlink Control Information (DCI) containing scheduling information for one or more PXSCHs (S1520). According to the proposed embodiment, as the number of PXSCHs that can be scheduled simultaneously is limited to N_t, a specific field of the DCI that schedules one or more PXSCHs on an MC cell can be configured differently from the existing one, and accordingly, the size of the DCI payload can be determined.
[0368] According to one embodiment, the NDI (New Data Indicator), RV (Redundancy Version), or HPI (HARQ Process Index) fields included in the DCI may include N_t subfields, and each of the N_t subfields may individually indicate NDI, RV, and HPI-related information for each of the N_t PXSCHs. Additionally, for a single PXSCH, if up to N_s PXSCHs can be scheduled in a TDM format, the NDI, RV, or HPI fields may include N_t*N_s subfields, and if up to N_a PXSCHs can be scheduled in an SDM format through a single PXSCH, the NDI, RV, or HPI fields may include N_t*N_a subfields. Additionally, if, through a single PXSCH, up to N_s PXSCHs can be transmitted in TDM form and up to N_a PXSCHs can be transmitted in SDM form, the NDI, RV, or HPI fields may include N_t*N_s*N_a subfields.
[0369] The FDRA (Frequency Domain Resource Assignment) / MCS (Modulation and Coding Scheme) fields included in the DCI may, depending on the embodiment, include Alt 1) N_t subfields or Alt 2) N_c subfields. If the FDRA / MCS fields include N_t subfields according to Alt 1), each subfield included in the FDRA / MCS fields may correspond to each of the N_t PXSCHs. For example, the nth subfield among the N_t subfields may correspond to the nth PXSCH among the N_t PXSCHs. Or, if the FDRA / MCS fields include N_c subfields according to Alt 2), each subfield included in the FDRA / MCS fields may correspond to each of the N_c carriers. For example, the nth subfield among the N_c subfields may correspond to the nth carrier among the N_c carriers. At this time, the number of subfields of the FDRA field and the MCS field can be determined independently according to Alt 1) or Alt 2), respectively.
[0370] Unlike the MCS, RV, HPI, FDRA, and MCS fields, the TDRA (Time Domain Resource Assignment) field included in the DCI can be composed of a single field without distinction of subfields. However, in the case of the TDRA field, the configuration of the TDRA table associated with the TDRA field can be determined based on N_c or N_t. Each row of the TDRA table is composed of a combination of {K0, K2, PXSCH SLIV, PXSCH mapping type}, and one of the multiple rows can be indicated to the terminal through the DCI. As previously mentioned, the combination of {K0, K2, PXSCH SLIV, PXSCH mapping type} may be referred to as the "TDRA parameter set" for convenience. Each row of a conventional TDRA table may consist of one set of parameters, but according to the proposed embodiment, each row may consist of Alt 1) N_t sets of TDRA parameters or Alt 2) N_c sets of TDRA parameters. For example, if each row consists of N_t sets of TDRA parameters according to Alt 1), among the N_t sets of TDRA parameters constituting each row, the nth set of TDRA parameters may correspond to the nth PXSCH among N_t PXSCHs. Or, if each row consists of N_c sets of TDRA parameters according to Alt 2), among the N_c sets of TDRA parameters constituting each row, the nth set of TDRA parameters may correspond to the nth carrier among N_c carriers.
[0371] The TDRA table according to the proposed embodiment maintains the same number of rows as the conventional TDRA table, and when a specific row of the TDRA table is indicated through a single DCI, a plurality of TDRA parameter sets included in the indicated row may be indicated together. At this time, according to Alt 1), the plurality of TDRA parameter sets included in the indicated row and N_t PXSCHs may have a sequential one-to-one correspondence relationship, and according to Alt 2), the plurality of TDRA parameter sets included in the indicated row and N_c carriers may have a sequential one-to-one correspondence relationship.
[0372] Additionally, for each PXSCH, if up to N_s PXSCHs can be scheduled in TDM form, the TDRA parameter set corresponding to each PXSCH or each carrier may include N_s combinations of {K0, K2, PXSCH SLIV, PXSCH mapping type}.
[0373] In addition, if each row of the TDRA table is composed of N_t sets of TDRA parameters according to the method of Alt 1), if invalid information is indicated through the set of TDRA parameters corresponding to a specific PXSCH, the PXSCH may be treated or considered as not scheduled. Or, if each row of the TDRA table is composed of N_c sets of TDRA parameters according to the method of Alt 2), if invalid information is indicated through at least some of the sets of TDRA parameters corresponding to a specific PXSCH, the PXSCH may be treated or considered as not scheduled.
[0374] A terminal according to one embodiment may receive or transmit one or more PXSCHs based on information regarding mapping relationships (S1530). Specifically, the PXSCH may include PDSCH or PUSCH, and the terminal may receive one or more PDSCHs or transmit one or more PUSCHs based on information regarding mapping relationships. For example, the terminal may identify a carrier (or carrier index) corresponding to each of one or more scheduled PXSCHs based on information regarding mapping relationships, and may receive or transmit one or more scheduled PXSCHs through the identified one or more carriers.
[0375] FIG. 16 illustrates the flow of a method performed by a terminal according to one embodiment.
[0376] FIG. 16 is an embodiment relating to at least some of the aforementioned proposals, and the description of the aforementioned proposals may be referenced even without separate mention.
[0377] Referring to FIG. 16, a terminal according to one embodiment may receive information regarding the number of carriers set within a cell and the maximum number of physical layer data channels that can be simultaneously scheduled in the frequency domain (S1600). At this time, the cell may refer to a multi-carrier (serving) cell in which a plurality of carriers constitute a cell, and may correspond to the MC cell described above. In addition, the number of carriers set within a cell may correspond to the N_c described above, and the maximum number of physical layer data channels that can be simultaneously scheduled in the frequency domain may correspond to N_t. The physical layer data channels may include PDSCH and PUSCH, and as described above, may be referred to as PXSCH for convenience. In addition, the carriers set within a cell may have a size of at least one of their respective bandwidths or the sum of their total bandwidths, which may be less than or equal to a specific value.
[0378] Simultaneous scheduling in the frequency domain may mean that multiple physical layer data channels can be transmitted in FDM form at the same time, and may also mean that multiple physical layer data channels distributed in the frequency domain can be simultaneously scheduled through a single DCI. The maximum number of physical layer data channels that can be simultaneously scheduled in the frequency domain may include a value less than or equal to the number of carriers set within a cell (i.e., N_t ≤ N_c).
[0379] A terminal according to one embodiment may receive information regarding a mapping relationship between a physical layer data channel that can be simultaneously scheduled with carriers (set within a single cell) (S1610). For example, the information regarding the mapping relationship may include information regarding a carrier corresponding to each of N_t physical layer data channels. The information regarding a carrier corresponding to each of N_t physical layer data channels may correspond to the aforementioned "PXSCH-to-carrier mapping" information. Alternatively, according to an embodiment, the information regarding the mapping relationship may include information regarding a physical layer data channel corresponding to each of N_c carriers. The information regarding a physical layer data channel corresponding to each of N_c carriers may correspond to the aforementioned "carrier-to-PXSCH mapping" information. In this case, the information regarding the mapping relationship may be indicated through a specific field of DCI or set through RRC, etc.
[0380] A terminal according to one embodiment may receive a DCI containing scheduling information for one or more physical layer data channels (S1620). One or more physical layer data channels may refer to N_t or fewer physical layer data channels and may be scheduled simultaneously through a single DCI. At this time, a specific field included in the DCI may include a number of subfields determined based on the number of carriers set within a cell (e.g., N_c) or the maximum number of physical layer data channels that can be scheduled simultaneously (e.g., N_t). For example, the number of subfields constituting a specific field included in the DCI may be determined to be the same value as N_c or N_t, and according to an embodiment, may be determined to be a value obtained by multiplying N_c or N_t by a specific parameter.
[0381] Specific fields included in DCI may include NDI, RV, HPI, FDRA, or MCS fields. In the case of NDI, RV, or HPI fields, they may be composed of a number of subfields equal to the maximum number of simultaneously schedulable physical layer data channels (e.g., N_t). In this case, based on the fact that for each physical layer data channel, up to N_s physical layer data channels are configured to be transmitted via Time Division Multiplexing (TDM), the NDI, RV, or HPI fields may include a number of subfields equal to the maximum number of simultaneously schedulable physical layer data channels multiplied by N_s (e.g., N_t*N_s). Additionally, based on the configuration that for each physical layer data channel, up to N_a physical layer data channels are transmitted via Spatial Division Multiplexing (SDM), the NDI, RV, or HPI fields may include a number of subfields equal to the maximum number of simultaneously schedulable physical layer data channels multiplied by N_a (e.g., N_t * N_a). Furthermore, based on the configuration that for each physical layer data channel, up to N_s physical layer data channels are transmitted via TDM and up to N_a physical layer data channels are transmitted via SDM, the NDI, RV, or HPI fields may be configured with N_s * N_a subfields for each of the N_t physical layer data channels. Accordingly, the NDI, RV, or HPI fields may be configured with N_t * N_s * N_a subfields for all N_t physical layer data channels.
[0382] Additionally, the FDRA or MCS field may include a number of subfields equal to the number of carriers set within a cell (e.g., N_c) or the maximum number of physical layer data channels that can be simultaneously scheduled (in the frequency domain) (e.g., N_t). The FDRA or MCS field including N_c subfields corresponds to the method described above Alt 1), and the FDRA or MCS field including N_t subfields corresponds to the method described above Alt 2).
[0383] Additionally, the DCI may further include a TDRA field composed of a single field. That is, the TDRA field may be composed of a single field without distinction of subfields. Each row of the TDRA table associated with the TDRA field may include one or more parameter sets related to the allocation of time resources for physical layer data channels, and the number of parameter sets included in each row may have a value equal to the number of carriers set within a cell (e.g., N_c) or the maximum number of physical layer data channels that can be simultaneously scheduled (in the frequency domain) (e.g., N_t). As described above, each parameter set may include a combination of {K0, K2, PXSCH SLIV, PXSCH mapping type}.
[0384] In addition, for each physical layer data channel, if up to N_s physical layer data channels are configured to be TDM-transmitted, the TDRA parameter set corresponding to each physical layer data channel or each carrier may include N_s TDRA parameter sets.
[0385] A terminal according to one embodiment can receive or transmit one or more physical layer data channels based on information regarding a mapping relationship (between carriers set within a cell and physical layer data channels that can be simultaneously scheduled in the frequency domain) (S1630). Specifically, the physical layer data channels may include a downlink physical layer data channel (e.g., PDSCH) or an uplink physical layer data channel (e.g., PUSCH), and the terminal can receive one or more PDSCH or transmit one or more PUSCH based on information regarding the mapping relationship. A terminal according to one embodiment can identify a carrier (or carrier index) corresponding to each of the one or more scheduled physical layer data channels based on information regarding the mapping relationship. Accordingly, the terminal can receive or transmit one or more scheduled physical layer data channels through the identified one or more carriers.
[0386] FIG. 17 illustrates the flow of a method performed by a base station according to one embodiment. FIG. 17 is an embodiment relating to at least some of the aforementioned proposals, and the description of the aforementioned proposals may be referenced even without separate mention.
[0387] A base station according to one embodiment may transmit information to a terminal regarding the number of carriers set within a cell and the maximum number of physical layer data channels that can be simultaneously scheduled in the frequency domain (S1700). A cell may refer to a multi-carrier (serving) cell in which a plurality of carriers constitute a cell, and may correspond to the MC cell described above. In addition, the number of carriers set within a cell may correspond to the N_c described above, and the maximum number of physical layer data channels that can be simultaneously scheduled in the frequency domain may correspond to N_t, and the physical layer data channels may include PDSCH and PUSCH, and as described above, may be referred to as PXSCH for convenience.
[0388] According to one embodiment, the maximum number of physical layer data channels that can be simultaneously scheduled in the frequency domain may include a value less than or equal to the number of carriers set within a cell (i.e., N_t ≤ N_c).
[0389] A base station according to one embodiment may transmit information regarding a mapping relationship between a physical layer data channel that can be simultaneously scheduled with carriers (set within a single cell) to a terminal (S1710). According to an embodiment, the information regarding the mapping relationship may include information regarding a carrier corresponding to each of N_t physical layer data channels, or information regarding a physical layer data channel corresponding to each of N_c carriers. The information regarding the mapping relationship may be indicated through a specific field of DCI or set through RRC, etc.
[0390] A base station according to one embodiment may transmit a DCI containing scheduling information for one or more physical layer data channels to a terminal (S1720). One or more physical layer data channels may refer to N_t or fewer physical layer data channels, and may be scheduled simultaneously through a single DCI. At this time, a specific field included in the DCI may include a number of subfields determined based on the number of carriers set within a cell (e.g., N_c) or the maximum number of physical layer data channels that can be scheduled simultaneously (e.g., N_t).
[0391] Specific fields included in DCI may include NDI, RV, HPI, FDRA, or MCS fields. In the case of NDI, RV, or HPI fields, they may be composed of a number of subfields equal to the maximum number of simultaneously schedulable physical layer data channels (e.g., N_t). In this case, based on the fact that for each physical layer data channel, up to N_s physical layer data channels are configured to be transmitted via Time Division Multiplexing (TDM), the NDI, RV, or HPI fields may include a number of subfields equal to the maximum number of simultaneously schedulable physical layer data channels multiplied by N_s (e.g., N_t*N_s). Additionally, based on the configuration that for each physical layer data channel, up to N_a physical layer data channels are transmitted via Spatial Division Multiplexing (SDM), the NDI, RV, or HPI fields may include a number of subfields equal to the maximum number of simultaneously schedulable physical layer data channels multiplied by N_a (e.g., N_t * N_a). Furthermore, based on the configuration that for each physical layer data channel, up to N_s physical layer data channels are transmitted via TDM and up to N_a physical layer data channels are transmitted via SDM, the NDI, RV, or HPI fields may be configured with N_s * N_a subfields for each of the N_t physical layer data channels. Accordingly, the NDI, RV, or HPI fields may be configured with N_t * N_s * N_a subfields for all N_t physical layer data channels.
[0392] Additionally, the FDRA or MCS field may include a number of subfields equal to the number of carriers set within a cell (e.g., N_c) or the maximum number of physical layer data channels that can be simultaneously scheduled (in the frequency domain) (e.g., N_t).
[0393] Additionally, DCI may further include a TDRA field composed of a single field. That is, the TDRA field may be composed of a single field without distinction of subfields. Each row of the TDRA table associated with the TDRA field may include one or more parameter sets related to the allocation of time resources for physical layer data channels, and the number of parameter sets included in each row may have a value equal to the number of carriers set within a cell (e.g., N_c) or the maximum number of physical layer data channels that can be simultaneously scheduled (in the frequency domain) (e.g., N_t).
[0394] A base station according to one embodiment may transmit one or more physical layer data channels to a terminal or receive from a terminal based on information regarding a mapping relationship (between carriers set within a cell and physical layer data channels that can be simultaneously scheduled in a frequency domain) (S1730). Specifically, the base station may transmit one or more downlink physical layer data channels (e.g., PDSCH) to a terminal or receive an uplink physical layer data channel (e.g., PUSCH) from a terminal based on information regarding a mapping relationship.
[0395] The embodiments described above are combinations of the components and features of the present disclosure in a specific form. Each component or feature should be considered optional unless otherwise explicitly stated. Each component or feature may be implemented in a form not combined with other components or features. Additionally, it is possible to construct embodiments of the present disclosure by combining some components and / or features. The order of operations described in the embodiments of the present disclosure may be changed. Some components or features of one embodiment may be included in another embodiment, or may be replaced with corresponding components or features of another embodiment. It is obvious that embodiments may be constructed by combining claims that are not explicitly related in the claims, or that they may be included as new claims by amendment after filing.
[0396] It is obvious to those skilled in the art that the present disclosure may be embodied in other specific forms without departing from the features of the present disclosure. Accordingly, the foregoing detailed description should not be interpreted restrictively in all respects and should be considered exemplary. The scope of the present disclosure shall be determined by a reasonable interpretation of the appended claims, and all modifications within the equivalent scope of the present disclosure are included within the scope of the present disclosure.
[0397] The present disclosure may be used in a terminal, base station, or other equipment of a wireless mobile communication system.
Claims
1. In a method performed by a terminal, A step of receiving information regarding the number of carriers set within a single cell and the maximum number of physical layer data channels that can be simultaneously scheduled in the frequency domain; A step of receiving information regarding the mapping relationship between the carriers and the simultaneously schedulable physical layer data channels; A step of receiving Downlink Control Information (DCI) containing scheduling information for one or more physical layer data channels; and Based on information regarding the mapping relationship above, the method includes the step of receiving or transmitting one or more physical layer data channels; and A method in which a specific field included in the above DCI comprises a number of subfields determined based on the number of carriers or the maximum number of physical layer data channels.
2. In Paragraph 1, A method in which the maximum number of simultaneously schedulable physical layer data channels includes a number less than or equal to the number of set carriers.
3. In Paragraph 1, A method in which the specific field above includes an NDI (New Data Indicator), RV (Redundancy Version), HPI (Hybrid Automatic Repeat Request Processing Index), FDRA (Frequency Domain Resource Assignment), or MCS (Modulation and Coding Scheme) field.
4. In Paragraph 3, A method in which the NDI, RV, or HPI fields each include a number of subfields equal to the maximum number of simultaneously schedulable physical layer data channels.
5. In Paragraph 4, Based on the fact that for each of the above simultaneously schedulable physical layer data channels, up to N_s physical layer data channels are configured to be transmitted via time division multiplexing, the NDI, the RV, or the HPI field includes a number of subfields equal to the maximum number of physical layer data channels multiplied by N_s. A method in which, for each of the above simultaneously schedulable physical layer data channels, up to N_a physical layer data channels are configured to be transmitted via spatial division multiplexing, wherein the NDI, the RV, or the HPI field comprises a number of subfields equal to the maximum number of physical layer data channels multiplied by N_a.
6. In Paragraph 3, A method in which the FDRA or MCS field comprises a number of subfields equal to the number of carriers or the maximum number of physical layer data channels.
7. In Paragraph 3, The above DCI further includes a TDRA (Time Domain Resource Assignment) field composed of a single field, and Each row of the TDRA table associated with the above TDRA field includes one or more parameter sets related to the allocation of time resources, and A method in which the number of parameter sets included in each of the above rows is equal to the number of carriers or the maximum number of physical layer data channels.
8. In Paragraph 1, A method in which at least one of the bandwidths of each of the carriers set within the cell, or the sum of the bandwidths of the carriers, has a size less than or equal to a specific value.
9. In Paragraph 1, A method wherein the maximum number of simultaneously schedulable physical layer data channels includes the maximum number of physical layer data channels that are transmitted via frequency division multiplexing at one time and can be scheduled through a single DCI.
10. In Paragraph 1, Information regarding the above mapping relationship is composed of a bitmap containing a number of bits equal to the number of the carriers, and A method in which each bit included in the bitmap corresponds to each of the carriers.
11. A computer-readable non-transitory recording medium storing a program for performing the method described in claim 1.
12. Regarding the device, At least one processor; and It includes at least one memory configured to store instructions that cause the at least one processor to perform operations by being executed by the at least one processor, and The operations of the above processor are, Receive information regarding the number of carriers configured within a single cell and the maximum number of physical layer data channels that can be simultaneously scheduled in the frequency domain, and Receive information regarding the mapping relationship between the above carriers and the above simultaneously scheduleable physical layer data channels, and Receive Downlink Control Information (DCI) containing scheduling information for one or more physical layer data channels, and Based on information regarding the above mapping relationship, the operation of receiving or transmitting one or more physical layer data channels is included. A device in which a specific field included in the above DCI comprises a number of subfields determined based on the number of carriers or the maximum number of physical layer data channels.
13. In Paragraph 12, The above device is a device that is a terminal including a transceiver or a processing device configured to control the terminal.
14. In a method performed by a base station, A step of transmitting to a terminal information regarding the number of carriers set within a single cell and the maximum number of physical layer data channels that can be simultaneously scheduled in the frequency domain; A step of transmitting to the terminal information regarding the mapping relationship between the carriers and the simultaneously schedulable physical layer data channels; A step of transmitting Downlink Control Information (DCI) containing scheduling information of one or more physical layer data channels to the terminal; and Based on information regarding the above mapping relationship, the method includes the step of transmitting one or more physical layer data channels to the terminal or receiving them from the terminal; A method in which a specific field included in the above DCI comprises a number of subfields determined based on the number of carriers or the maximum number of physical layer data channels.
15. Regarding base stations, At least one processor; and It includes at least one memory configured to store instructions that cause the at least one processor to perform operations by being executed by the at least one processor, and The operations of the above processor are, Transmit information to the terminal regarding the number of carriers configured within a single cell and the maximum number of physical layer data channels that can be simultaneously scheduled in the frequency domain, and Information regarding the mapping relationship between the above carriers and the above simultaneously schedulable physical layer data channels is transmitted to the terminal, and Transmit Downlink Control Information (DCI) containing scheduling information for one or more physical layer data channels to the terminal, and Based on information regarding the above mapping relationship, the operation includes transmitting one or more physical layer data channels to the terminal or receiving them from the terminal. A base station in which a specific field included in the above DCI comprises a number of subfields determined based on the number of carriers or the maximum number of physical layer data channels.
