Method performed by terminal or network in wireless communication system, and device therefor

Abstract

A method performed by a terminal according to one embodiment of the present disclosure may comprise: receiving a plurality of configured grant (CG) configurations for uplink transmission through higher layer signaling; and transmitting a CG physical uplink shared channel (PUSCH) on the basis of a first CG configuration among the plurality of CG configurations, wherein the CG PUSCH includes unused transmission occasion (UTO) information about whether subsequent CG PUSCH transmission occasions (TOs) will not be used by the terminal, the subsequent CG PUSCH TOs are related to at least two CG configurations, and the UTO information may include first information indicating which CG configurations the at least two CG configurations related to the subsequent CG PUSCH TOs are.

Description

Method performed by a terminal or network in a wireless communication system and device therefor

[0001] The present disclosure relates to a wireless communication system, and more particularly, to a method and device for performing wireless communication between terminals or networks in a wireless communication system.

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

[0003] The existing NR standard (Rel-18) introduced Unused Transmission Occasion-Uplink Control Information (UTO-UCI), which indicates whether CG-PUSCH resources allocated semi-statically through CG-PUSCH configuration will not be used. UTO-UCI is a bitmap with N bits that indicates whether N future (valid) CG-PUSCH transmission occasions (TOs) will be (un)used.

[0004] By including UTO-UCI when transmitting CG-PUSCH, the terminal can report to the network whether or not it will use future CG-PUSCH TOs, thereby increasing the possibility of utilizing unused resources.

[0005] The existing UTO-UCI has limitations in that it can only notify the use of CG-PUSCH TOs belonging to the same CG-PUSCH configuration. Furthermore, if the UE does not transmit the CG-PUSCH, the UTO-UCI transmission itself is omitted.

[0006] The technical task to be achieved in the present disclosure is to provide a method and device for efficiently performing a wireless signal transmission and reception process. As an example, a method is provided that can signal whether (subsequent) UL transmission resources belonging to the same CG (configured grant) configuration as well as other CG configurations are (un)used.

[0007] In addition to the technical challenges described above, other technical challenges can be inferred from the description below.

[0008] According to one aspect of the present disclosure, a method performed by a terminal includes receiving a plurality of configured grant (CG) configurations for uplink transmission through higher layer signaling; and transmitting a CG PUSCH (physical uplink shared channel) based on a first CG configuration among the plurality of CG configurations, wherein the CG PUSCH includes unused TO (UTO) information indicating whether subsequent CG PUSCH TOs (transmission occasions) will not be used by the terminal, wherein the subsequent CG PUSCH TOs are related to at least two CG configurations, and the UTO information may include first information indicating which CG configurations the at least two CG configurations related to the subsequent CG PUSCH TOs are.

[0009] The above first information is a first bitmap including a plurality of bits, and each of the plurality of bits of the first bitmap can be associated with a CG setting.

[0010] The at least two CG settings include the first CG setting, and a plurality of bits of the first bitmap can be respectively associated with CG settings other than the first CG setting.

[0011] The above UTO information may include second information indicating whether subsequent CG PUSCH TOs will not be used individually for each of the at least two CG settings.

[0012] The second information may be a second bitmap, and the second bitmap for the first CG configuration among the at least two CG configurations may include first bits for first subsequent CG PUSCH TOs based on the first CG configuration, and the second bitmap for the second CG configuration among the at least two CG configurations may include second bits for second subsequent CG PUSCH TOs based on the second CG configuration.

[0013] The UTO information may include second information indicating whether subsequent CG PUSCH TOs common to the at least two CG configurations will not be used. For example, the at least two CG configurations include a first CG configuration and a second CG configuration, and the second information is a second bitmap, and a first bit of the second bitmap may indicate whether first sets of subsequent CG PUSCH TOs of the second CG configuration determined based on a first subsequent CG PUSCH TO of the first CG configuration and the first subsequent CG PUSCH TO of the first CG configuration will not be used by the terminal, and a second bit of the second bitmap may indicate whether second sets of subsequent CG PUSCH TOs of the second CG configuration determined based on a second subsequent CG PUSCH TO of the first CG configuration and the second subsequent CG PUSCH TO of the first CG configuration will not be used by the terminal.

[0014] The above UTO information may include second information indicating at least one of a start point or an end point of subsequent CG PUSCH TOs used by the terminal, or a start point or an end point of subsequent CG PUSCH TOs not used by the terminal.

[0015] The above CG PUSCH may include information about at least one of a modulation and coding scheme (MCS) for the subsequent CG PUSCH TOs, frequency resource allocation, time resource allocation, CG-PUSCH period, or the number of CG PUSCH TOs per each CG-PUSCH period.

[0016] According to another aspect of the present disclosure, a non-transitory computer-readable recording medium having recorded thereon a program for performing the method described above may be provided.

[0017] According to another aspect of the present disclosure, a device comprises at least one processor; and at least one memory configured to store instructions that are executed by the at least one processor to cause the at least one processor to perform operations, wherein the operations of the processor include receiving a plurality of configured grant (CG) configurations for uplink transmission through higher layer signaling; and transmitting a CG PUSCH (physical uplink shared channel) based on a first CG configuration among the plurality of CG configurations, wherein the CG PUSCH includes unused TO (UTO) information indicating whether subsequent CG PUSCH TOs (transmission occasions) will not be used by the terminal, and the subsequent CG PUSCH TOs are related to at least two or more CG configurations, and the UTO information may include first information indicating which CG configurations the at least two or more CG configurations related to the subsequent CG PUSCH TOs are.

[0018] The above device may further include a transmitter and receiver.

[0019] The above device may be a terminal operating in a wireless communication system.

[0020] The above device may be a processing device configured to control a terminal operating in a wireless communication system.

[0021] According to another aspect of the present disclosure, a method performed by a base station includes transmitting a plurality of configured grant (CG) configurations for uplink transmission of a terminal through upper layer signaling; and receiving a CG PUSCH (physical uplink shared channel) from the terminal based on a first CG configuration among the plurality of CG configurations, wherein the CG PUSCH includes unused TO (UTO) information indicating whether subsequent CG PUSCH TOs (transmission occasions) will not be used by the terminal, and the subsequent CG PUSCH TOs are related to at least two or more CG configurations, and the UTO information may include first information indicating which CG configurations the at least two or more CG configurations related to the subsequent CG PUSCH TOs are.

[0022] According to another aspect of the present disclosure, a base station comprises at least one processor; and at least one memory configured to store instructions that are executed by the at least one processor to cause the at least one processor to perform operations, wherein the operations of the processor include transmitting a plurality of configured grant (CG) configurations for uplink transmission of a terminal through higher layer signaling; and receiving a CG PUSCH (physical uplink shared channel) from the terminal based on a first CG configuration among the plurality of CG configurations, wherein the CG PUSCH includes unused TO (UTO) information indicating whether subsequent CG PUSCH TOs (transmission occasions) will not be used by the terminal, and the subsequent CG PUSCH TOs are related to at least two or more CG configurations, and the UTO information may include first information indicating which CG configurations the at least two or more CG configurations related to the subsequent CG PUSCH TOs are.

[0023] According to the present disclosure, signal transmission and reception can be efficiently performed in a wireless communication system. According to one embodiment, information regarding the (un)used or unused status of UL resources belonging to multiple CG configurations is provided through a single reception of UTO information, thereby not only improving the potential usability of unused resources but also reducing signaling overhead compared to providing UTO information for each CG configuration.

[0024] In addition to the technical effects described above, other technical effects can be inferred from the description below.

[0025] Figure 1 illustrates a flexible network topology to which some examples of this specification may be applied.

[0026] FIG. 2 illustrates an example of a communication system applicable to the present disclosure.

[0027] FIG. 3 illustrates an example of a wireless device applicable to the present disclosure.

[0028] FIG. 4 illustrates a communication procedure between a first node (e.g., a terminal) and a second node (e.g., a base station) applicable to the present disclosure.

[0029] Figure 5 illustrates a general functional architecture for an AI / ML model.

[0030] Figure 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.

[0031] FIG. 7 illustrates an electromagnetic spectrum according to one embodiment of the present disclosure.

[0032] FIG. 8 illustrates an example of a procedure for transmitting system information for THz communication to which the present disclosure applies.

[0033] Figure 9 illustrates a beam management procedure applicable to the present disclosure.

[0034] FIG. 10 illustrates an example of a sensing operation according to one embodiment of the present disclosure.

[0035] FIG. 11 illustrates time / frequency resources for sensing operations according to one embodiment of the present specification.

[0036] FIG. 12 illustrates a procedure related to a sensing operation according to one embodiment of the present specification.

[0037] Figure 13 illustrates an example of the operation procedure of a base station supporting NES technology.

[0038] Figure 14 illustrates an example of a procedure for cell DTX / DRX operation.

[0039] Figure 15 illustrates an example of a procedure for CA operation using SSB-less SCell.

[0040] Figure 16 illustrates an example of a conditional handover (CHO) procedure.

[0041] Figure 17 illustrates an example of on-demand SSB transmission.

[0042] Figure 18 illustrates an example of an (un)used TO report via UTO UCI.

[0043] Figure 19 is a drawing for explaining an example of commonly applying / configuring bitmap information representing (un)used TO to multiple CG-confs.

[0044] Figure 20 is a drawing for explaining an example of applying / configuring bitmap information representing (un)used TO to another CG-conf.

[0045] FIG. 21 is a diagram illustrating an example of reporting (un)used TO using PUCCH.

[0046] FIG. 22 is a diagram for explaining the operation of a terminal and a base station according to one embodiment.

[0047] Figure 23 illustrates a flow of a method performed in a terminal according to one embodiment.

[0048] Figure 24 illustrates a flow of a method performed at a base station according to one embodiment.

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

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

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

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

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

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

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

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

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

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

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

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

[0061] 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.

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

[0063] <Symbols, Abbreviations, Terms>

[0064] - PDCCH: Physical Downlink Control CHannel

[0065] - DCI: Downlink Control Information

[0066] - PDSCH: Physical Downlink Shared CHannel

[0067] - PUSCH: Physical Uplink Shared CHannel

[0068] - CSI: Channel state information

[0069] - RRM: Radio resource management

[0070] - SCS: Sub-carrier spacing

[0071] - RLM: Radio link monitoring

[0072] - DCI: Downlink Control Information

[0073] - CAP: Channel Access Procedure

[0074] - Ucell: Unlicensed cell

[0075] - TBS: Transport Block Size

[0076] - TDRA: Time Domain Resource Allocation

[0077] - SLIV: Starting and Length Indicator Value (This is an indicator value for the starting symbol index and number of symbols within the slot of the PDSCH and / or PUSCH, and can be set as a component of the entry that constitutes the TDRA field within the PDCCH that schedules the corresponding PDSCH and / or PUSCH.)

[0078] - BWP: BandWidth Part (can be composed of consecutive resource blocks (RBs) on the frequency axis and can correspond to one numerology (e.g., sub-carrier spacing, CP length, slot / mini-slot duration). In addition, multiple BWPs can be configured on one carrier (the number of BWPs per carrier can also be limited), but the number of activated BWPs can be limited to a part of it (e.g., 1) per carrier.)

[0079] - CORESET: COntrol REsourse SET (refers to the time-frequency resource area where PDCCH can be transmitted, and the number of CORESETs per BWP may be limited.)

[0080] - REG: Resource element group

[0081] - SFI: Slot Format Indicator (An indicator indicating the symbol level DL / UL direction within a specific slot(s), transmitted through the group common PDCCH.)

[0082] - COT: Channel occupancy time

[0083] - SPS: Semi-persistent scheduling

[0084] - QCL: Quasi-Co-Location (QCL relationship between two reference signals means that QCL parameters such as Doppler shift, Doppler spread, average delay, delay spread, and Spatial Rx parameter obtained from one reference signal can be applied to another reference signal (or antenna port(s) of the corresponding RS). In the NR system, four QCL types are defined as follows. 'typeA': {Doppler shift, Doppler spread, average delay, delay spread}, 'typeB': {Doppler shift, Doppler spread}, 'typeC': {Doppler shift, average delay}, 'typeD': {Spatial Rx parameter} For any DL RS antenna port(s), the first DL RS is set as a reference for QCL type X (X=A, B, C, or D), and additionally, the second DL RS is set as a reference for QCL type Y (Y=A, B, C, or D but X≠Y) ) can be set as a reference to

[0085] - TCI: Transmission Configuration Indication (A TCI state includes the QCL relationship between one or more DL RSs, such as DM-RS ports of the PDSCH, the DM-RS port of PDCCH, or the CSI-RS port(s) of a CSI-RS resource. For the 'Transmission Configuration Indication' field in the DCI that schedules the PDSCH, the TCI state index corresponding to each code point that constitutes the field is activated by the MAC CE, and the TCI state setting for each TCI state index is set through RRC signaling. In the Rel-16 NR system, the TCI state is set between DL RSs, but in future releases, setting between DL RS and UL RS or UL RS and UL RS may be allowed. Examples of UL RSs include SRS, PUSCH DM-RS, and PUCCH DM-RS.)

[0086] - SRI: SRS resource indicator (Indicates one of the SRS resource index values ​​set in the 'SRS resource indicator' among the fields in the DCI that schedules the PUSCH. When transmitting a PUSCH, the UE can transmit the PUSCH using the same spatial domain transmission filter used for transmitting and receiving the reference signal linked to the corresponding SRS resource. At this time, the reference RS is set by RRC signaling through the SRS-SpatialRelationInfo parameter for each SRS resource, and SS / PBCH block, CSI-RS, or SRS can be set as the reference RS.)

[0087] - TRP: Transmission and Reception Point

[0088] - TAG: Timing advance group

[0089] - PLMN: Public Land Mobile Network

[0090] Figure 1 illustrates a flexible network topology to which some examples of this specification may be applied.

[0091] To compensate for incomplete network coverage areas, a network topology that allows for more flexible and resilient split radio access networks (RANs) may be considered. For this purpose, various nodes, such as IAB nodes, relays, and RF repeaters, as illustrated in the example in Figure 1, may be applied, or NTNs 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, or in the case of a sidelink relay where a terminal functions as a relay, it may collectively refer to a terminal-to-network (U2N) relay and a terminal-to-terminal (U2U) relay. For example, an RF repeater may correspond to a node that simply performs the function of signal amplification and forwarding, while a network-controlled repeater may not only amplify and forward signals but also adjust transmission and reception settings based on information provided by the network. For example, an NTN node may correspond to a satellite or aircraft that provides NTN coverage that is difficult for terrestrial networks to provide. In addition to these examples, various intermediate points can be introduced to improve the network topology.

[0092] Referring to Figure 1, a split RAN can support the division of a base station into a centralized unit (CU) and one or more distributed units (DUs). The CU and DU can correspond to logical units. The CU can be further 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 DUs, various intermediate points can be introduced to compensate for this.

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

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

[0095] That is, in some examples of this specification, for the sake of simplicity of explanation, the subjects of the operation may be referred to as a base station and / or a terminal (or a first node and / or a second node). In addition, the terms base station and / or terminal (or a first node and / or a second node) may also be interpreted / replaced as in the following examples: For example, the base station (or a first node) and the terminal (or a second node) may respectively correspond to the first endpoint and the second endpoint; may respectively correspond to the endpoint and the intermediate point; may respectively correspond to the intermediate point and the endpoint; or may respectively correspond to the first intermediate point and the second intermediate point.

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

[0097] Figure 2 illustrates a communication system applicable to the present disclosure.

[0098] 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 a 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 Things) device (110f), and an AI (artificial intelligence) device / server (110g). For example, the vehicle may include a vehicle equipped with a wireless communication function, an autonomous vehicle, a vehicle capable of performing vehicle-to-vehicle communication, etc. Here, the vehicle (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, a digital signage, a vehicle, a robot, etc. The portable device (110d) may include a smartphone, a smart pad, a wearable device (e.g., a smart watch, smart glasses), a computer (e.g., a laptop, etc.), 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 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 act as a network device (120) to another wireless device (110).

[0099] Wireless devices (110a to 110f) can be connected to a network (130) via a network device (120). AI technology can be applied to the wireless devices (110a to 110f), and the wireless devices (110a to 110f) can be connected to an AI server (110g) via a network (130). The network (130) can be configured using a 3G network, a 4G (e.g., LTE) network, a 5G (e.g., NR), or a 6G network. The wireless devices (110a to 110f) can communicate with each other via the network device (120) / network (130), but can 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). Additionally, IoT devices (110f) (e.g., sensors) can communicate directly with other IoT devices (e.g., sensors) or other wireless devices (110a to 110f).

[0100] Wireless communication / connection (150a, 150b, 150c) can be established between wireless devices (110a to 110f) / network devices (120), network devices (120) / network devices (120). Here, the 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 the wireless communication / connection (150a, 150b, 150c), the wireless device and the network device / wireless device, and the network device and the network device can transmit / receive wireless signals to each other. For example, the wireless communication / connection (150a, 150b, 150c) can transmit / receive signals through various physical channels. To this end, based on various descriptions of the present disclosure, at least some of various configuration information setting processes for transmitting / receiving wireless signals, various signal processing processes (e.g., channel encoding / decoding, modulation / demodulation, resource mapping / demapping, etc.), resource allocation processes, etc. may be performed.

[0101] FIG. 3 illustrates an example of a wireless device applicable to the present disclosure.

[0102] Referring to FIG. 3, the wireless device (200) can transmit and receive wireless signals via 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).

[0103] The processor (202) controls the memory (204) and / or the transceiver (206), and may be configured to implement the descriptions, functions, procedures, proposals, methods, and / or operational flowcharts disclosed in this document. For example, the processor (202) may process information in the memory (204) to generate first information / signal, and then transmit a wireless signal including the first information / signal via the transceiver (206). In addition, the processor (202) may receive a wireless signal including second information / signal via the transceiver (206), and then store information obtained from 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, the memory (204) may store software code including 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 operational flowcharts disclosed herein. Here, the processor (202) and the memory (204) may be part of a communication modem / circuit / chip designed to implement wireless communication technology. The transceiver (206) may be connected to the processor (202) and may transmit and / or receive wireless signals via at least one antenna (208). The transceiver (206) may include a transmitter and / or a receiver. The transceiver (206) may be used interchangeably with an RF (radio frequency) unit. In the present disclosure, a wireless device may also mean a communication modem / circuit / chip.

[0104] Hereinafter, the 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., a functional layer such as physical (PHY), media access control (MAC), radio link control (RLC), packet data convergence protocol (PDCP), radio resource control (RRC), and service data adaptation protocol (SDAP)). At least one processor (202) may generate at least one Protocol Data Unit (PDU) and / or at least one Service Data Unit (SDU) according to the descriptions, functions, procedures, proposals, methods, and / or operation flowcharts disclosed in this document. At least one processor (202) may generate a message, control information, data, or information according to the descriptions, functions, procedures, proposals, methods, and / or operation flowcharts disclosed in this document. At least one processor (202) can generate a signal (e.g., a baseband signal) including a PDU, an SDU, a message, control information, data or information according to the functions, procedures, proposals and / or methods disclosed in this document, and provide the signal to at least one transceiver (206). At least one processor (202) can receive a signal (e.g., a baseband signal) from at least one transceiver (206) and obtain the PDU, SDU, message, control information, data or information according to the descriptions, functions, procedures, proposals, methods and / or operational flowcharts disclosed in this document.

[0105] At least one processor (202) may be referred to as a controller, a microcontroller, a microprocessor, or a microcomputer. The 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 the at least one processor (202). The descriptions, functions, procedures, proposals, methods, and / or operation flowcharts disclosed in this document may be implemented using firmware or software, and the firmware or software may be implemented to include modules, procedures, functions, etc. The descriptions, functions, procedures, proposals, methods, and / or operation flowcharts disclosed in this document may be included in the at least one processor (202), or may be stored in at least one memory (204) and executed by the at least one processor (202). The descriptions, functions, procedures, suggestions, 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.

[0106] At least one memory (204) can be connected to at least one processor (202) and can store various forms of data, signals, messages, information, programs, codes, instructions and / or commands. The at least one memory (204) can be configured as a read only memory (ROM), a random access memory (RAM), an erasable programmable read only memory (EPROM), a flash memory, a hard drive, a register, a cache memory, a computer readable storage medium and / or a combination thereof. The at least one memory (204) can be located internally and / or externally to the at least one processor (202). In addition, the at least one memory (204) can be connected to the at least one processor (202) via various technologies such as a wired or wireless connection.

[0107] At least one transceiver (206) can transmit user data, control information, wireless signals / channels, etc., mentioned in the methods and / or flowcharts of this document to at least one other device. At least one transceiver (206) can receive user data, control information, wireless signals / channels, etc. mentioned in the descriptions, functions, procedures, proposals, methods and / or flowcharts disclosed in this document from at least one other device. For example, at least one transceiver (206) can be connected to at least one processor (202) and can transmit and receive wireless signals. For example, at least one processor (202) can control at least one transceiver (206) to transmit user data, control information, or wireless signals to at least one other device. Furthermore, at least one processor (202) can control at least one transceiver (206) to receive user data, control information, or wireless signals from at least one other device. In addition, 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. mentioned in the descriptions, functions, procedures, proposals, methods and / or operation flowcharts 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).For this purpose, at least one transceiver (206) may include an (analog) oscillator and / or filter.

[0108] The components of the wireless device described with reference to FIG. 3 may be referred to by different terms in terms of functionality. For example, the processor (202) may be referred to as a control unit, the transceiver (206) as a communication unit, and the memory (204) as a storage unit. In some cases, the communication unit may be used to mean at least a portion of the processor (202) and the transceiver (206).

[0109] The structure of the wireless device described with reference to FIG. 3 can be understood as the structure of at least a portion of various devices. For example, the structure of the wireless device illustrated in FIG. 3 can be at least a portion of various devices described with reference to FIG. 2 (e.g., a robot (110a), a vehicle (110b-1, 110b-2), an XR device (110c), a portable device (110d), a home appliance (110e), an IoT device (110f), an AI device / server (110g)). Furthermore, according to various embodiments, in addition to the components illustrated in FIG. 3, the device may further include other components.

[0110] For example, the device may be a portable device such as a smartphone, a smart pad, a wearable device (e.g., a smart watch, smart glasses), or a portable computer (e.g., a 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., an audio input / output port, a video input / output port), and an input / output unit for inputting and outputting image information / signals, audio information / signals, data, and / or information input from a user.

[0111] For example, the device may be a mobile device such as a mobile robot, a vehicle, a train, an aerial vehicle (AV), a ship, etc. In this case, the device may further include at least one of a driving unit including at least one of an engine, a motor, a power train, wheels, brakes, and a steering unit of the device, a power supply unit including a wired / wireless charging circuit, a battery, etc. that supplies power, a sensor unit that senses status 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 obtains location information of the mobile device through a global positioning system (GPS) and various sensors.

[0112] For example, the device may be an XR device such as an HMD, a head-up display (HUD) installed in a vehicle, a television, a smartphone, a computer, a wearable device, a home appliance, a 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 obtains control information, data, etc. from the outside and outputs the generated XR object, and a sensor unit that senses status information, environmental information, and user information of the device or the surroundings of the device.

[0113] For example, the device may be a robot that can be classified into industrial, medical, household, military, etc. types 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 status information, environmental information, and user information of the device or its surroundings, and a driving unit that performs various physical actions, such as moving the robot joints.

[0114] For example, the device may be an AI device such as a TV, a projector, a smartphone, a PC, a laptop, a digital broadcasting terminal, a tablet PC, a wearable device, a set-top box (STB), a radio, a washing machine, a refrigerator, digital signage, a robot, a 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 status information, environmental information, and user information of the device or its surroundings, and a training unit that trains a model composed of an artificial neural network using learning data.

[0115] The structure of the wireless device illustrated in FIG. 3 may be understood as a part of a terminal (or first node), or as a part of an intermediate point, or as a part of a base station (or second node). If the device illustrated 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 communications. However, if the front haul and / or back haul communications are based on wireless communications, at least one transceiver (206) illustrated in FIG. 3 may be used for front haul and / or back haul communications, and a wired transceiver may not be included.

[0116] FIG. 4 illustrates a communication procedure between a first node (e.g., a terminal) and a second node (e.g., a base station) applicable to the present disclosure.

[0117] The second node of FIG. 4 supports dynamic spectrum sharing (DSS), which can provide connectivity to both nodes implementing 6G technology and nodes implementing pre-6G wireless communication technologies (e.g., 5G, 4G). That is, the first node of FIG. 4 can implement either 6G technology or pre-6G wireless communication technologies (e.g., 5G, 4G). Furthermore, the first node and / or the second node can support full duplex mode as well as non-overlapping full duplex mode.

[0118] 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 operations of the terminal (110) and the base station (120) transmitting and / or receiving data and operations performed prior thereto are illustrated. However, the operations of Fig. 4 are not limited to operations between the terminal and the base station, and may be interpreted as operations between the first node and the second node. In addition, although Fig. 4 illustrates direct wireless signal transmission and reception operations between the terminal (110) and the base station (120), one or more intermediate points may exist between the terminal (110) and the base station (120), and wireless signals may be transmitted and received via one or more intermediate points.

[0119] 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 connection to at least one base station transmitted from the base station (120) according to a predefined rule. Here, the synchronization signal can include a plurality of synchronization signals classified according to structure or purpose (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 confirm the boundary of a unit (e.g., a frame, a subframe, a slot, and / or a symbol) constituting a wireless signal transmission of the base station (120) and obtain information (e.g., a cell identifier) ​​about the base station (120).

[0120] The terminal (110) can obtain system information transmitted from the base station (120) (403). The system information is information related to the properties, characteristics, and / or capabilities of the base station (120) required to access the base station (120) and use the service, and can be classified according to the content (e.g., whether it is essential for access), transmission structure (e.g., channel used, whether provided on-demand), etc., and can be classified into, for example, first system information (e.g., master information block (MIB), primary system information), second system information (e.g., system information block (SIB), secondary system information), etc. If necessary, the terminal (110) can transmit a signal requesting system information before receiving the system information. However, the request and provision of system information can be performed after the random access procedure described below.

[0121] The terminal (110) and the base station (120) can perform a random access procedure (405). The terminal (110) can transmit and / or receive at least one message (e.g., a random access preamble, a random access response (RAR) message, etc.) for the random access procedure based on information related to a channel for the random access procedure of the base station (120) obtained through system information (e.g., channel location, channel structure, structure of a supported preamble, etc.). For example, the terminal (110) can transmit a first message (e.g., a preamble, MSG1) through the channel for the random access procedure, receive a second message (e.g., an RAR message, MSG2), transmit a third message (e.g., MSG3) including 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 and third messages may be sent and received as one message, or the second and fourth messages may be sent and received as one message.

[0122] 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 a connection (e.g., a radio resource control (RRC) layer), a layer that handles mapping between logical channels and transport 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 for establishing a connection, signaling for determining settings related to communication, and signaling for indicating allocated resources.

[0123] 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 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, waveform demodulation for each antenna, signal arrangement considering layer mapping, constellation demapping, descrambling, and channel decoding.

[0124] <6G System Core Technologies>

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

[0126] As core implementation technologies of the 6G system, technologies such as artificial intelligence (AI), THz (terahertz) communication, optical wireless technology, FSO backhaul network, massive MIMO 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.

[0127] artificial intelligence

[0128] Incorporating AI into communications can streamline and improve real-time data transmission. AI can use numerous analytics to determine how complex target tasks should be performed. This means AI can increase efficiency and reduce processing delays. Time-consuming tasks such as handovers, network selection, and resource scheduling can be performed instantly using AI. AI can also play a crucial role in machine-to-machine (M2M), machine-to-human, and human-to-machine communications. Furthermore, AI can facilitate rapid communication in brain-computer interfaces (BCIs). 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.

[0129] The following describes a functional framework for AI / ML operations.

[0130] Below, to explain AI (or AI / ML) more specifically, the terms can be defined as follows.

[0131] - Data collection: Data collected from network nodes, management entities, or terminals as a basis for AI model training, data analysis, and inference.

[0132] - 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.

[0133] - AI / ML Training: An online or offline process of training an AI model by learning features and patterns that best represent the data and obtain a trained AI / ML model for inference.

[0134] - AI / ML Inference: The process of making predictions or inducing decisions based on collected data and the AI ​​model using a trained AI model.

[0135] Life Cycle Management (LCM) procedures for AI / ML models (i.e., model training, model deployment, model inference, model monitoring, model updates, etc.) can be divided into functionality-based LCM and model-based LCM. In functionality-based LCM, AI / ML models may not be identified by the network, and the network can direct the activation / deactivation / fallback / switching of AI / ML functionality. In model-ID (identifier)-based LCM, AI / ML models can be identified by the network, and the network / terminal can activate / deactivate / select / switch AI / ML models based on the model ID.

[0136] Figure 5 illustrates a general functional architecture for an AI / ML model.

[0137] In particular, Figure 5 illustrates a general functional architecture relevant to both Functionality-based LCM and Model-based LCM. Some of the functions or some of the data / information / command flows (i.e., arrows) illustrated in Figure 5 may be omitted.

[0138] Referring to FIG. 5, a general functional framework can 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).

[0139] 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) can perform data preparation based on raw data and 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., a terminal, a network node, etc.) or may be performed by multiple entities.

[0140] 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).

[0141] 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. 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) transferred from the Data Collection function (10), if necessary.

[0142] Trained / Updated Model (21): If there is a Model Storage function (50), it is used to pass a trained, validated and tested AI / ML model to the Model Storage function (50) or to pass an updated version of the model to the Model Storage function (50).

[0143] The Management function (30) is a function that supervises the operation of the AI / ML model or AI / ML function. In addition, the Management function (30) may perform 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)).

[0144] Management Instruction (32) is information required as input to manage the Inference function (40). The relevant information may include selection / (de)activation / switching of an AI / ML model or AI / ML-based function, and may also include fallback to non-AI / ML operations (i.e., not relying on the inference process).

[0145] A Model Transfer / Delivery Request (33) can be used to request model(s) from Model Storage (50).

[0146] A Performance Feedback / Retraining Request (31) refers to information required as input to the Model Training function (20) (e.g., for the purpose of (re)training or updating the model).

[0147] 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 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 Data Collection (10). If necessary, the Inference function (40) may also perform data preparation (e.g., data preprocessing and cleaning, forming, and transformation) based on the Inference Data (13) provided by Data Collection function (10).

[0148] 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 the AI / ML model generated by the Inference function (30), and the details of the inference output may vary depending on the use case.

[0149] The Model Storage function (50) stores a learned / updated model that can be used to perform the Inference function (40). The Model Storage function (50) illustrated in FIG. 5 can be used as a reference point (if any) when applicable to protocol termination, model transmission / delivery, and related processes. Furthermore, the Model Storage function (50) is merely an example and is not intended to limit the storage location of actual AI / ML models, and may be omitted.

[0150] Model Transfer / Delivery (51) is used to transfer AI / ML models to inference functions.

[0151] The level of cooperation can be defined as follows depending on the capability of AI / ML functions between multiple nodes, and variations due to combination of multiple levels or separation of any one level are also possible.

[0152] Cat 0a) No collaboration framework: AI / ML algorithms are purely implementation-based and do not require any changes to the wireless interface.

[0153] Cat 0b) This level corresponds to a framework with a modified wireless interface tailored to efficient implementation-based AI / ML algorithms, but without collaboration.

[0154] Category 1) involves inter-node support to improve the AI / ML algorithms of each node. For example, this applies when a specific node receives support from another node (for training, adaptation, etc.) and vice versa. At this level, model exchange between network nodes is not required.

[0155] Category 2) Joint AI / ML tasks can be performed across multiple nodes. This level requires the exchange of AI / ML model commands or network nodes.

[0156] FIG. 5 is a diagram illustrating an overall functional framework for an AI / ML model, and not all functions and / or all data / information / command signals illustrated in FIG. 5 may be performed within a specific node, but only some of them may be performed.

[0157] AI / ML models can be divided 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.

[0158] A one-side model can refer to an AI / ML model in which inference is performed entirely by a single node (e.g., a terminal or network). Here, AI / ML model training can also be performed entirely by a single node. AI / ML model training and inference can be performed by the same node, or they can be performed by separate nodes.

[0159] 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 refers to inference being performed jointly across multiple nodes. For example, the first part of the inference may be performed by a first node, and the remaining part by a second node. Two-side models can be categorized into several types depending on the training method of the AI / ML model, as follows:

[0160] - First type: AI / ML models 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 / objects.

[0161] - 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 part) and model reconstruction (CSI compression by sub-use case) 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).

[0162] - Third type: Separate training of AI / ML models can be performed on multiple nodes (e.g., networks and terminals). Separate training may mean that training begins sequentially on one node and continues on other nodes. In this case, the first node first performs the AI / ML model and shares the training data with the second node. The second node can then use the shared training data to perform the AI / ML model. For example, training for the CSI generation part may be performed by the terminal, while CSI reconstruction may be performed by the network.

[0163] Figure 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.

[0164] The operations described below can be described / interpreted based on the AI / ML model proposed in this specification, as shown in Fig. 6 below, even without separate mention (i.e., without explicit mention of being by / based on / for the AI / ML model). In addition, unless specifically limited, the AI / ML model can correspond to a one-side model in which inference is entirely performed by a single node, or a two-side model in which joint inference is performed by multiple nodes.

[0165] First signaling (601): In the description below, 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., generation and / or reconstruction) the AI / ML model of FIG. 5, or correspond to inference data used for inference of the AI / ML model, or correspond to feedback for the AI / ML model, etc. If signaling between nodes is not required prior to an operation based on an AI / ML model in the present specification, the first signaling (601) may be omitted. If a one-side model is used in the present specification, the one-way / two-way signaling (set) in the present specification may correspond to the signaling of the first signaling (601). In addition, when a two-side model is used in this specification, the one-way / two-way signaling in this specification may correspond to the first signaling (601), and also, a repetitive signaling operation may correspond to the first signaling (601).

[0166] For example, in AI / ML model-based beam management (BM), if a base station predicts (i.e., infers) beam(s) with good quality based on an AI / ML model, the base station can receive quality / intensity information for multiple beams from a terminal. Furthermore, if a terminal predicts (i.e., infers) beam(s) with good quality based on an AI / ML model, the terminal can receive multiple beams from the base station.

[0167] AI / ML model-based operation (602): In the description below, an operation (e.g., calculation, selection, prediction, etc.) in a specific node (e.g., terminal, network, etc.) or a joint operation (e.g., calculation, selection, prediction, etc.) in 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 if not mentioned separately. For example, it may correspond to training (i.e., generation and / or reconstruction) of the AI / ML model of FIG. 5 or inference of the AI / ML model, etc. When a one-side model is used, an operation performed by a single node in the present specification may correspond to an AI / ML model-based operation (602), and also, when a two-side model is used, a joint operation performed by multiple nodes in the present specification may correspond to an AI / ML model-based operation (602).

[0168] For example, in an AI / ML model-based BM, the base station can use quality / intensity information for multiple beams received from the terminal as inference data to predict (i.e., infer) beam(s) with good quality based on the AI / ML model. Furthermore, the terminal can measure multiple beams received from the base station and use the measurement results as inference data to predict (i.e., infer) beam(s) with good quality based on the AI / ML model.

[0169] Second signaling (603): In the description below, 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 a second signaling (603) or a set of signaling generated due to (as a result of) an operation based on an AI / ML model, even if not otherwise mentioned. For example, it may correspond to an output resulting from inference of the AI / ML model in 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, a one-way / two-way signaling (set) in this specification may correspond to the second signaling (603). In addition, when a two-side model is used in this specification, the one-way / two-way signaling in this specification may correspond to the second signaling (603), and also, a repetitive signaling operation may correspond to the second signaling (603).

[0170] For example, in an AI / ML model-based BM, the base station can transmit to the terminal the beam(s) predicted based on the AI / ML model as candidates so that the terminal can determine the optimal beam. Furthermore, the terminal can report to the base station the beam(s) predicted based on the AI / ML model to request the base station to transmit the candidate beams as candidates for determining the optimal beam.

[0171] THz communication (terahertz communication)

[0172] Data rates can be increased by increasing bandwidth. This can be achieved by utilizing sub-THz communications with wide bandwidths and applying advanced massive MIMO technology. THz waves, also known as sub-millimeter waves, typically refer to the frequency range between 0.1 THz and 10 THz, with corresponding wavelengths ranging from 0.03 mm to 3 mm. The 100 GHz to 300 GHz band (sub-THz band) is considered a key part of the THz spectrum for cellular communications. Adding the sub-THz band to the mmWave band will increase the capacity of 6G cellular communications. Among the defined THz bands, 300 GHz to 3 THz lies in the far infrared (IR) frequency band. While part of the optical band, the 300 GHz to 3 THz band lies at the boundary of the optical band, immediately following the RF band. Therefore, this 300 GHz to 3 THz band exhibits similarities to RF.

[0173] Figure 7 illustrates the electromagnetic spectrum according to one embodiment of the present disclosure. The embodiment of Figure 7 can be combined with various embodiments of the present disclosure. Key characteristics of THz communications include (i) a widely available bandwidth to support very high data rates, and (ii) high path loss at high frequencies (highly directional antennas are essential). The narrow beamwidth generated by the highly directional antenna reduces interference. The small wavelength of THz signals allows for a much larger number of antenna elements to be integrated into devices and base stations operating in this band. This enables the use of advanced adaptive array techniques to overcome range limitations.

[0174] Transmitting system information (i.e., information related to the properties, characteristics, and / or capabilities of a BS required to use a service, such as MIB, SIB, etc.) in the THz frequency band may be inefficient because, as the beam width becomes narrower in high frequency bands, more beam sweeps must be performed to cover the entire area of ​​the cell. 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 such as that illustrated in FIG. 8 may be used.

[0175] Figure 8 illustrates an example of a procedure for transmitting system information for THz communications to which the present disclosure applies. While this example was developed with THz in mind, it is also applicable to 6G communication environments where THz is not applicable. Furthermore, the procedure illustrated in Figure 8 can be combined with various embodiments of the present disclosure described below. For example, the embodiments described below can be performed based on system information acquired through the procedure illustrated in Figure 8.

[0176] 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 a THz frequency band, and cell #2 uses a non-THz frequency band. Here, the system information can include at least one information / state / parameter / setting generated in each of a higher layer and a physical layer. For example, the at least one information / state / parameter / setting generated in the higher layer can include at least one of an 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 the at least one information / state / parameter / setting generated in the physical layer can include at least one of an SFN, a half frame indicator, and an SSB index. However, this is merely an example, and system information may include information / status / parameters / settings related to Cell #1 / Cell #2 generated from various types of physical layers / upper layers. For this purpose, as an example, Cell #1 and Cell #2 may have a relationship as a secondary cell and a primary cell.

[0177] The UE can acquire synchronization for cell #1 (803). Synchronization can be acquired by detecting a synchronization signal. Typically, synchronization is acquired before receiving system information. However, since the system information for cell #1 is received from cell #2, synchronization acquisition for cell #1 can be performed after receiving the system information. For example, the UE can acquire synchronization based on the system information. However, unlike FIG. 8, in another example, synchronization acquisition can be performed before step 801.

[0178] The UE may transmit a signal for accessing cell #1 (805). For example, the signal may include information for accessing cell #1 (e.g., a random access preamble). The structure of the signal and the resources for transmitting the signal (e.g., a channel) may be identified through system information. Thereafter, the UE and the base station may perform an access procedure for cell #1 and communicate (807). During this process, operations according to various embodiments described below may be performed.

[0179] The procedure described with reference to FIG. 8 may be performed when UE (801) first accesses cell #1 of the base station. Alternatively, a similar procedure may be performed when UE (801) hands over to cell #1 of the base station. However, in the case of handover, the system information of cell #1 may be received from a cell of a base station other than cell #2 of the base station.

[0180] Communications in the THz band are expected to experience extremely severe path loss, and to overcome this, terminals and base stations must use extremely sharp beams. The use of sharp beams means that terminals and base stations must perform beam control in addition to beamforming, and the number of beams used increases significantly. Consequently, it takes a very long time to align the transmit and receive beams between the base station and terminals. Furthermore, if the beam alignment between the base station and terminals is misaligned due to the movement or movement of the terminals, frequent re-alignment of the beams is required, which can lead to link instability. Accordingly, a beam management procedure, as illustrated in FIG. 9 below, may be employed.

[0181] 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 the present disclosure is applicable to a 6G communication environment. In addition, the procedure illustrated in FIG. 9 can be combined with various embodiments of the present disclosure described below. Here, a beam may be interpreted as 'spatial (setting) information', 'spatial domain filter', 'spatial domain transmission filter', 'spatial domain reception filter', or / and a term having an equivalent technical meaning that can distinguish the 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.).

[0182] Referring to FIG. 9, a base station can configure resources for beam management (901). Here, the resources can include at least one of time-frequency resources, channels, and spatial resources (e.g., antenna ports). For example, the base station can utilize a beam search signal (BSS) that is transmitted spatially separated from existing downlink signals / channels for beam search. Here, the BSS can be transmitted based on a dedicated port for beam search. The dedicated port can be a different port from a 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 can be included in the technical concept according to the present embodiment.

[0183] The base station can transmit measurement signals using multiple transmission beams (903). For example, the measurement signals can include at least one of a reference signal and a synchronization signal. At this time, the measurement signals can be transmitted as many times as the number of beams that require measurement, and can be transmitted using a multi-beam transmission method that forms multiple beams simultaneously to reduce sweeping time. Here, the multi-beam transmission can be performed based on at least one of a multi-panel, a sub-array, and a true time delay (TTD).

[0184] The UE may transmit a feedback signal to the base station (905). The feedback signal indicates at least one beam selected by the UE. The UE may select at least one preferred beam based on the received measurement signals. The UE and the base station may communicate (907). At this time, the UE and the base station may communicate using the previously selected beam. If channel reciprocity is established, the transmission beam of the UE may also be determined through operations 903 and 905, and thus the transmission of the UE may also be performed using the beam selected in operation 905. If channel reciprocity is not established, a procedure including transmission of measurement signals by the UE and transmission of a feedback signal by the base station may be performed first to determine the transmission beam of the UE. In operation 907, operations according to various embodiments described below may be performed.

[0185] Integrated Sensing and Communication (ISAC)

[0186] Wireless sensing is a technology that uses radio frequencies to determine the instantaneous linear velocity, angle, distance (range), etc. of an object, thereby obtaining information about the characteristics of the environment and / or objects within the environment. Because radio frequency sensing does not require a networked device to connect to the object, it can provide a service for object positioning without a device. The ability to obtain range, velocity, and angle information from radio frequency signals can enable a wide range of new capabilities, 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 a variety of industries (e.g., drones, smart homes, V2X, factories, railways, public safety, etc.), enabling 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 can utilize non-3GPP type sensors (e.g., radar, cameras) to further support 3GPP-based sensing. For example, the operation of wireless sensing services, i.e., sensing operations, may depend on the transmission, reflection, and scattering of wireless sensing signals. Therefore, wireless sensing offers an opportunity to enhance existing communication systems from a communication network to a wireless communication and sensing network.

[0187] FIG. 10 illustrates an example of a sensing operation according to an embodiment of the present disclosure. The embodiment of FIG. 10 can 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 location (e.g., monostatic sensing), and FIG. 10(b) illustrates an example of sensing using a separated sensing receiver and sensing transmitter (e.g., bistatic sensing).

[0188] 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, different terminals, or each terminal and base station.

[0189] In this regard, the following six types of sensing modes can be defined based on whether the sensing transmitter and sensing receiver are included in the base station or the terminal, respectively.

[0190] - Mode 1: A mode in which the sensing transmitter and sensing receiver are contained in a single base station (e.g., base station-based sensing mode in monostatic mode).

[0191] - Second mode: A mode in which the sensing transmitter is included in a 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).

[0192] - Mode 3: 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).

[0193] - Mode 4: 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).

[0194] - Mode 5: A mode in which the sensing transmitter and sensing receiver are contained in a single terminal (e.g., terminal-based sensing mode in monostatic mode).

[0195] - 6th mode: A mode in which the sensing transmitter is included in a 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).

[0196] 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 / in combination.

[0197] 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 an environment around 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 scattered / reflected by one or more objects (and / or an environment around the objects) from a sensing signal transmitted from the sensing transmitter. In the sensing receiver, sensing data may be derived from the scattered / reflected signals, and sensing results may be generated / obtained through processing of the sensing data. Here, the sensing results may include characteristic information (e.g., location, distance, speed, angle, etc.) about one or more objects (and / or the environment around the objects). The sensing results generated / obtained in this way may be utilized for wireless sensing services (e.g., detection, tracking, etc. of objects and / or environments) provided in the wireless communication system based on the 6G network of the present specification, or may be provided / disclosed to a trusted third party.

[0198] Additionally, the sensing operation in FIG. 10 is described as a representative example of the operation in a wireless communication system based on a 6G network, but can be extended and applied to cases where terminals / base stations / signals based on networks of previous generations (e.g., 4G, 5G, etc.) are utilized.

[0199] Additionally, with respect to the wireless sensing described herein, in a wireless communication system based on a 6G network of the present specification, time / frequency resources for sensing operations and time / frequency resources for general communications (e.g., UL / DL / sidelink-based communications, etc.) may be scheduled / configured separately.

[0200] FIG. 11 illustrates time / frequency resources for sensing operations according to one embodiment of the present disclosure. The embodiment of FIG. 11 may be combined with various embodiments of the present disclosure.

[0201] Referring to FIG. 11, time / frequency resources (hereinafter, sensing resources) for the aforementioned sensing operation (e.g., sensing operation based on FIG. 10) can be set / allocated separately from time / frequency resources (hereinafter, communication resources) for general communication.

[0202] For example, as illustrated in FIG. 11, sensing resources can be set / allocated in units of symbols in the time domain and / or resource blocks in the frequency domain. Resources other than those for which the sensing resources are set / allocated can be utilized as resources for general communication. That is, sensing resources and communication resources can be set / allocated based on a time-division multiplexing (TDM) scheme and / or a frequency-division multiplexing (FDM) scheme in terms of the operation of the base station / terminal. Additionally or alternatively, unlike what is illustrated in FIG. 10, sensing resources can also be set / allocated based on other units in the time domain (e.g., slots, frames, absolute time (ms, us), etc.) and / or other units in the frequency domain (e.g., subcarriers, carriers, absolute frequencies (MHz, GHz), etc.).

[0203] Additionally or alternatively, in connection with the setting / allocation / scheduling of resources for general communication as described herein, the relationship between the resources and the aforementioned sensing resources may need to be considered. For example, when setting / allocating resources for general communication according to the embodiment(s) of the present disclosure, the resources may be set / allocated to rate-match or puncture the resource region corresponding to the sensing resource. For example, when scheduling resources for general communication according to the embodiment(s) of the present disclosure, the resources may be scheduled so as not to overlap with the resource region corresponding to the sensing resource. If the resources for general communication according to the embodiment(s) of the present disclosure and the resource region corresponding to the sensing resource are set / allocated / scheduled to overlap, one or both operations may be dropped, skipped, or postponed based on priorities, predefined rules, etc. That is, in the embodiment(s) of the present specification, it may be desirable that resources related to general communication (e.g., resources for signals / channels related to UL / DL / Sidelink-based data / control, etc.) are set / allocated / scheduled so as not to overlap with the sensing resources described above.

[0204] Additionally, various channel modeling methods may be applied in connection with the wireless sensing described herein. Channel modeling related to sensing may refer to configuring a path for transmitting and receiving sensing signals and / or scattered / reflected signals, taking into account the object being sensed and / or the environment in which the object resides. Channel modeling may be related to the performance / requirements of sensing in wireless communication systems, and thus may be an important factor in validating the sensing function.

[0205] Channels related to sensing can be divided into channels between objects (e.g., targets of interest) and sensing transmitters / receivers, and channels between the environment to which the object belongs and sensing transmitters / receivers. In this regard, channel modeling related to sensing can be divided based on sensing mode (e.g., the six types of modes described above), whether there is an object / 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 the environment in a base station / terminal-based monostatic sensing mode, and channel modeling for the environment in a base station / terminal-based bistatic sensing mode can be configured and optimized differently. For example, when various sensing scenarios are classified, channel modeling for detection, location, and tracking scenarios, channel modeling for motion recognition, and channel modeling for imaging / environment reconstruction scenarios can be divided, etc. 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 the present disclosure may be based on stochastic geometric channel modeling techniques and / or hybrid with ray tracing channel modeling techniques. Here, the stochastic geometric 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 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.

[0206] FIG. 12 illustrates a procedure related to a sensing operation according to one embodiment of the present disclosure. The embodiment of FIG. 12 may be combined with various embodiments of the present disclosure.

[0207] 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 confirm (1205) the capability of the terminal for the sensing operation. In this regard, the terminal may be configured to report capability information on whether it supports the sensing operation to the base station. Additionally or alternatively, if the terminal is defined in advance in the standard as supporting the sensing operation, the procedure may be omitted. In addition, in the case of a sensing operation in which only the base station participates, the base station may be configured to report capability information on whether it supports the sensing operation to an entity that configures / controls its sensing operation (e.g., a network entity at an upper level / layer of the base station).

[0208] For example, the base station can perform signaling with the terminal to exchange configuration information related to the sensing operation. For example, the base station can set / instruct the terminal about the mode of the sensing operation (e.g., based on the six types of modes described above), the subject of the sensing operation (e.g., sensing transmitter, sensing receiver), the resource of the sensing operation (e.g., sensing resource as in FIG. 11), the target of utilizing the sensing result (e.g., type of wireless sensing service based on 6G network, trusted third party), channel modeling for sensing (e.g., channel between the base station / terminal and object / environment), etc. (1210). For example, the base station can also set / instruct such information from a network entity at an upper level / layer of the base station.

[0209] For example, the base station and / or the terminal may perform a sensing operation based on the set / instructed information (1215). For example, the base station and / or the terminal may, as a sensing transmitter and / or a sensing receiver, perform procedures such as transmitting a sensing signal, receiving a scattered / reflected signal, deriving sensing data, obtaining a sensing result through processing the sensing data, and providing the sensing result, as in FIG. 9 described above. As an example, in the operation of the base station / terminal described herein, the sensing result provided through the sensing operation may be utilized.

[0210] < Network Energy Saving, NES >

[0211] Network Energy Saving Technology of Rel-18

[0212] Energy conservation at base stations is a key consideration in wireless communication systems, including 3GPP, as it can contribute to building eco-friendly networks by reducing carbon emissions and reducing operational expenditures (OPEX) for telecommunications companies. In particular, the introduction of 5G communications will require higher transmission rates, necessitating base stations to be equipped with more antennas and provide services over wider bandwidths and frequency bands. Consequently, recent studies have shown that base station energy costs have reached as high as 20% of total OPEX. Accordingly, 5G systems are adopting various technologies to reduce energy consumption, known as network energy savings (NES), and the standardization of related technologies will continue.

[0213] Depending on the application of NES technology, the base station can perform operations such as controlling on / off for a certain duration in the time domain, controlling transmission / reception resources for UE-common or UE-specific signals / channels, changing the amount of frequency domain resources, controlling transmission power, or turning on / off antenna ports, transmission-reception points (TRPs), etc. in the spatial domain.

[0214] Figure 13 illustrates an example of the operation procedure of a base station supporting NES technology.

[0215] Referring to Fig. 13, the base station can identify the NES solution(s) to be applied (1305). The NES solution(s) may be related to control of signal transmission and reception (e.g., on / off), beam operation, handover procedures, channel measurement and reporting, etc. The NES solution(s) to be applied may be adaptively selected or predefined based on the current situation (e.g., cell load level, characteristics of connected terminals, etc.). The base station that identified the NES solution(s) can perform signaling for the NES (1310). The specific signaling procedure may vary depending on the identified NES solution(s). For example, the base station may transmit common information about the NES solution(s), transmit configuration information necessary for NES operation to at least one terminal, or transmit control information regarding the progress of the NES operation to at least one terminal. In addition, the base station may receive capability information related to the NES from at least one terminal. Thereafter, the base station performs operations for the NES. At this time, the base station can perform operations for the NES based on the previously performed signaling (1315). That is, based on the system information, configuration information, and control information transmitted through the signaling, the base station can turn on / off the transmission and reception of specific signals, turn on / off elements in the spatial domain, or adjust resources for the transmission and reception of measurement signals.

[0216] Through a procedure similar to that in Fig. 13, NES technology can be implemented. Examples of NES solutions that can be implemented through a procedure similar to that in Fig. 13 are as follows.

[0217] - Intra-system energy saving solution: A RAN node can request a neighboring RAN node to switch at least one SSB beam into its inactive cell, or can perform paging using a limited set of beams to an inactive terminal (e.g., a stationary terminal).

[0218] - Inter-system energy saving solution: NG-RAN nodes that own capacity booster cells can autonomously transition those cells to an inactive state.

[0219] - SSB-less SCell solution: If SSB or SMTC (SSB-based RRM measurement timing configuration) configuration is not provided for the SCell, the UE can obtain timing reference and AGC source from another serving cell. In FR1 or FR2, the base station can configure intra-band CA or inter-band CA including the SCell without SSB transmission, in which case the SSB / SIB transmission can be triggered by the WUS (wake up signal) of the UE. Accordingly, since the period of common channels / signals such as SSB is increased, the base station can stay in the sleep state for a longer time.

[0220] - Cell DTX / DRX solution: In order to reduce the downlink transmission / uplink reception activity time of the base station, a periodic cell DTX / DRX pattern (e.g., active and inactive periods) can be commonly set for terminals within a cell having the corresponding feature. Here, the cell DTX pattern and the cell DRX pattern can be set and activated separately, and up to two cell DTX / DRX patterns can be set per MAC entity. When cell DTX is set and activated, at least one of monitoring for SPS opportunities or monitoring PDCCH can be stopped during the cell DTX inactivity period. When cell DRX is set and activated, at least one of transmission on CG resources or SR transmission can be stopped during the cell DRX inactivity period. Cell DTX / DRX can be activated / deactivated via RRC signaling or L1 group common signaling.

[0221] Parameters such as active duration and cycle may be configured for cell DTX / DRX. The active duration is the period during which the UE receives a PDCCH or SPS opportunity and waits to transmit SR or CG, and the cycle specifies the periodic repetition of the active duration and inactive duration. When both cell DTX and cell DRX are configured, parameters such as active duration and cycle are common. If the base station recognizes an emergency call or a public safety-related service (e.g., MPS or MCS), the network may release or deactivate the cell DTX / DRX configuration so as not to affect the service. In addition, at least some overlap is required between the active duration of the connected mode DRX of the UE and the active duration of the cell DTX / DRX. For example, the connected mode DRX cycle of the UE may be a multiple of the cell DTX / DRX cycle, or vice versa.

[0222] - Conditional handover (CHO) solution: A CHO procedure performed in a way that the execution of the handover is determined by the UE is used while the NES technology is applied (e.g., when the cell activates or deactivates cell DTX / DRX). In this case, the UE can use an NES-specific CHO event to initiate CHO for a candidate cell, and the reception of a DCI that activates the CHO condition(s) set by the NES event indication can be applied as an additional triggering condition for this.

[0223] - Spatial and power domain adaptation solution: To support the gNB for transceiver muting and / or transmit power adaptation, the UE may be configured to report multiple CSI entries in a CSI report based on multiple sub-configurations. Each sub-configuration corresponds to a spatial domain adaptation pattern (e.g., a subset of available spatial elements) and / or a power offset between a data channel (e.g., PDSCH) and CSI-RS. Depending on the application of the spatial and power domain adaptation solution, the CSI configuration, measurement, and / or reporting behavior may be affected.

[0224] Cell DTX / DRX

[0225] To operate a base station in sleep mode for a relatively long period of time without frequent wake-ups, a base station DTX / DRX has been proposed for NES purposes. The base station can reduce energy consumption by utilizing DTX transmission under low system load conditions by setting a cell DTX and setting the on-duration of the C-DRX of terminals within the active period of the cell DTX. Figure 14 illustrates an example of a procedure for cell DTX / DRX operation.

[0226] Referring to FIG. 14, the base station transmits system information to the terminal (1401), and the terminal checks information related to cell DTX / DRX (1402). For example, the system information may include MIB, SIB1, etc. In relation to NES technology, the MIB may include information related to cell barring (e.g., cellBarred), and the SIB1 may include information related to the cell barring status (e.g., cellBarredNES). Specifically, if cellBarred included in the MIB is set to a value indicating that it is not barred (e.g., notBarred), the terminal may determine that the cell is not barred, regardless of whether it supports NES cell DTX / DRX. Conversely, if cellBarred included in the received MIB is set to a value indicating that the cell is barred (e.g., barred), a terminal that does not support NES cell DTX / DRX may determine that the cell is barred. However, if the terminal has the capability to support NES cell DTX / DRX, the terminal checks SIB1 to determine the cell barring status. If cellBarred of MIB is set to barred and cellBarredNES is absent in SIB1, the terminal supporting NES cell DTX / DRX can treat the cell as barred and perform cell reselection to another cell. On the other hand, if cellBarred of MIB is set to barred and cellBarredNES is included in SIB1, the terminal supporting NES cell DTX / DRX can determine that the cell is not barred.

[0227] In the case of FIG. 14, it is assumed that the terminal has the capability to support NES cell DTX / DRX, and the cellBarred of the MIB is set to notBarred, or the cellBarred of the MIB is barred and cellBarredNES is included in SIB1. Accordingly, the terminal performs a random access procedure to connect to the base station (1403), and can perform communication thereafter. At this time, the base station performs a cell DTX / DRX operation and transmits configuration information related to the cell DTX / DRX operation to the terminal (1404). The configuration information related to the cell DTX / DRX operation (e.g., CellDTXDRX-Config) includes at least one parameter related to the cell DTX / DRX, and may include, for example, at least one of an on-duration timer, a cycle start offset, a slot offset, a configuration type (e.g., DTX, DRX, or DTX-DRX), and an activation state of the DTX / DRX (e.g., active, inactive). Additionally, the configuration information may further include information for receiving and interpreting cell DRX / DRX-related control information (e.g., DCI-related information).

[0228] Thereafter, the base station transmits control information related to cell DTX / DRX to the terminal (1405). The control information related to cell DTX / DRX may include DCI having a designated format (e.g., format 2_9). If an operation for a serving cell according to at least one of the cell DTX operation and the cell DRX operation is configured by configuration information (e.g., cellDTXDRX-Config), the terminal may check a set of search spaces (e.g., a set of Type3-PDCCH CSS) for monitoring a PDCCH conveying control information of a designated format during an active time through a higher layer parameter (e.g., SearchSpace), and may obtain a location of information about the serving cell within the control information through a higher layer parameter (e.g., positionInDCI-cellDTRX). Then, the terminal may obtain control information based on the identified set of search spaces and location.

[0229] Control information related to cell DTX / DRX may be used to indicate activation or deactivation of cell DTX and / or cell DRX, and / or to provide an NES-mode indicator, and may include, for example, at least one block including a cell DTX / DRX indicator and an NES-mode indicator. In this case, when the serving cell is configured as a SUL (supplementary uplink) carrier, the indication of activation or deactivation of cell DRX by the cell DTX / DRX indicator may be applied to both the UL carrier and the SUL carrier.

[0230] Thereafter, the terminal and the base station can perform communication based on the cell DTX / DRX (1406). Specifically, the base station can turn on / off the transmission and reception of signals according to the settings related to the cell DTX / DRX, and accordingly, the terminal can selectively monitor the signal from the base station. During the DTX-OFF, the base station enters a sleep mode to reduce energy consumption. At this time, the base station DTX cycle can be aligned with the cycle of the terminal DRX. The base station DTX-ON can completely cover the DRX-ON of the terminal. Furthermore, the base station can align the transmission of Xn / NG and the transmission of Uu for the purpose of NES. The DTX / DRX mechanism triggers the switching of reference signal resource set groups, and the base station can perform a dormancy-like behavior of sparsely transmitting or not transmitting SSB, SIB, and CSI-RS to reduce energy consumption. The terminal can sparsely receive or not receive a downlink signal / channel depending on the settings of the base station. Once the base station DTX / DRX operation is triggered, during the DTX / DRX OFF period, the terminal can discontinuously receive the corresponding CSI-RS, SSB, or PDCCH.

[0231] SSB-less SCell

[0232] Figure 15 illustrates an example of a procedure for CA operation using SSB-less SCell.

[0233] Referring to FIG. 15, the base station transmits configuration information for the SCell to the terminal. That is, the base station transmits configuration information for CA to provide a service to the terminal through CA operation. Here, the CA operation may be intra-band CA or inter-band CA. For example, the configuration information for the SCell may include information related to SCell addition (e.g., sCellToAddModList), and specifically, may include a cell index, a physical cell identifier, information related to DL-UL configuration, information related to BWP, information related to cell DTX / DRX, information related to downlink frequency (e.g., FrequencyInfoDL), etc. Then, the terminal may determine the configuration for the CA operation and perform communication using the PCell and SCell of the base station. At this time, the terminal may confirm that the SCell is an SSB-less SCell based on the information related to the downlink frequency included in the configuration information, and may check the related parameters. For example, a terminal can determine that an SCell is an SSB-less SCell by checking for the presence of a parameter indicating that it is an SSB-less SCell (e.g., SSBlessSCell), and can determine the timing reference and AGC source for the SCell based on information about the reference cell (e.g., referenceCell). In the case of Fig. 15, the reference cell may be a PCell. Therefore, the terminal can use the PCell as a timing reference and AGC source for communication on the SCell.

[0234] Conditional Hand Over (CHO)

[0235] Figure 16 illustrates an example of a Conditional Handover (CHO) procedure. The order of the operations illustrated in Figure 16 may vary depending on the case.

[0236] Referring to FIG. 16, the base station transmits configuration information for CHO to the terminal (1601). The configuration information for CHO may include information related to conditional reconfiguration (e.g., ConditionalReconfiguration, CondReconfigToAddModList) and information related to configuration for reporting (e.g., ReportConfigNR). Here, the information related to configuration for reporting may include information related to events related to reporting, identifiers of the events (e.g., condEventId), information indicating whether it is an NES-specific CHO event (e.g., nesEvent), etc. In the example of FIG. 16, event information indicating that it is an NES-specific CHO event is received.

[0237] The base station transmits information for enabling an NES-specific CHO execution condition to the terminal (1602). The information for enabling the NES-specific CHO execution condition may be transmitted via control information of a specified format (e.g., DCI format 2_9). The information for enabling the NES-specific CHO execution condition may be referred to as an NES-mode indicator, for example, as 1-bit information, which indicates enabling the NES-specific CHO execution condition when a related upper layer parameter (e.g., nesEvent) is set and the serving cell of the related block in the corresponding DCI is a primary cell.

[0238] Thereafter, the terminal performs a measurement (1603) and transmits a measurement report to the base station (1604). The base station determines a CHO based on the measurement report and performs signaling for a handover request with the neighboring base stations indicated by the measurement report (1606). The base station determines the neighboring base stations that have confirmed admission through signaling as candidate base stations and transmits information about the candidate base stations to the terminal (1607). Accordingly, the terminal evaluates the CHO execution conditions for the candidate base stations (1608). Accordingly, when a candidate cell satisfying the condition is determined, the terminal detaches from the old cell and synchronizes to the new cell (1609). At this time, since the terminal has previously received event information indicating that it is a NES-specific CHO event and also received information enabling the NES-specific CHO execution condition, it can determine whether the event is satisfied. In other words, if a NES-mode indicator is received through a lower layer and conditional triggering configuration information (e.g., condTriggerConfig) includes information (e.g., nesEvent) indicating that the event is a NES-specific CHO event, the terminal can determine that the event associated with the corresponding measurement identifier (e.g., measId) is satisfied, and thus determine that the CHO execution condition is satisfied.

[0239] NES Enhancement

[0240] 3GPP NR release 19 will discuss NES enhancements, with (1) On-demand SSB, (2) On-demand SIB1 transmission, and (3) adaptation of common signal / channel transmissions being considered as key targets.

[0241] (1) On-demand SSB

[0242] A method to reduce energy consumption can be discussed by having the base station transmit SSB on a specific cell through the on-demand SSB process and not transmit SSB on the cell when the on-demand SSB process is not available. In the existing NR system, SSB must be transmitted periodically and constantly for purposes such as time / frequency synchronization or RRM measurement, making it difficult to reduce energy consumption even when the base station has no data to receive or send. Considering this, the base station can reduce base station energy consumption by not performing SSB transmission until the on-demand SSB process is involved and then performing SSB transmission. The on-demand SSB process can be triggered using one of the following methods:

[0243] 1) The terminal requests SSB transmission from the base station by transmitting an uplink signal / channel (e.g., PRACH, PUCCH, PUSCH, SRS in the NR system).

[0244] 2) Requesting SSB transmission from base station (or TRP) #1 to base station (or TRP) #2 through an interface between base stations (e.g., Xn interface in NR system) or backhaul signaling.

[0245] 3) Signaling whether SSB transmission is possible for the corresponding Scell ​​through Scell ​​activation / deactivation signaling.

[0246] Considering coexistence with existing NR terminals, Release 19 is limited to on-demand SSB operation for connected mode terminals and SCells. However, in future releases or next-generation communication systems, on-demand SSB operation (for SSB transmission on PCell) considering inactive or idle mode terminals or initially connected terminals may be defined. In addition, carrier aggregation (CA) including the SCell can be applied to both intra-band CA and inter-band CA, and the SSB on the SCell transmitted through the on-demand SSB process can be utilized for at least functionality such as time / frequency synchronization, L1 / L3 measurement, and SCell activation.

[0247] (2) On-demand SIB1 transmission

[0248] A method to reduce energy consumption by having the base station transmit SIB1 for a specific cell through the on-demand SIB1 process and not transmit SIB1 for the cell when there is no on-demand SIB1 process can be discussed. In the existing NR system, SIB1 containing system information, random access information, etc. for initial access or idle mode terminals to access a cell had to be provided periodically, so it was difficult to reduce energy consumption even when the base station had no data to receive or send. Considering this, the base station can reduce base station energy consumption by not performing SIB1 transmission until the on-demand SIB1 process is accompanied and then performing SIB1 transmission. The on-demand SIB1 process can trigger the base station's SIB1 transmission by the terminal transmitting an uplink signal / channel (e.g., PRACH in the NR system). Specifically, the following scenarios can be considered but may not be limited to the following scenarios.

[0249] 1) Scenario 1: As in (a) of Fig. 17, when a UE receives an SSB (and / or other downlink signal / channel) from a cell#1 and recognizes that SIB1 is not transmitted on the cell#1, the UE can trigger SIB1 transmission by transmitting a signal requesting SIB1 (for convenience, the signal is referred to as a WUS (wake-up signal)) based on information provided in the SSB (and / or other downlink signal / channel) and / or predetermined information. The base station that receives the WUS can transmit a specific DL signal / channel on cell#1 in response thereto, and (or) transmit SIB1 on cell#1 (without transmitting the DL signal / channel).

[0250] 2) Scenario 2: As in (b) of Fig. 17, a terminal may attempt to camp on cell#2 when it receives an SSB (and / or other downlink signal / channel such as SIB1) from a cell#1 and recognizes that SIB1 is not transmitted on the corresponding cell#2. The terminal may trigger SIB1 transmission for cell#2 by transmitting a signal requesting SIB1 (i.e., WUS) on cell#1 based on information provided in the received SSB (and / or other downlink signal / channel such as SIB1) and / or predetermined information. The base station receiving the WUS may transmit a specific DL signal / channel (on cell#1 or cell#2) in response thereto, and may transmit SIB1 for cell#2 on cell#1 or cell#2 (or without transmitting the DL signal / channel).

[0251] 3) Scenario 3: As in (c) of Fig. 17, a terminal that receives an SSB (and / or other downlink signal / channel such as SIB1) from a cell#1 and recognizes that SIB1 is not transmitted on the corresponding cell#2 may attempt to camp on cell#2. The terminal may trigger SIB1 transmission for cell#2 by transmitting a signal requesting SIB1 (i.e., WUS) on cell#2 based on information provided in the received SSB (and / or other downlink signal / channel such as SIB1) and / or predetermined information. The base station that receives the WUS may transmit a specific DL signal / channel (on cell#1 or cell#2) in response thereto, and may transmit SIB1 for cell#2 on cell#1 or cell#2 (or without transmitting the DL signal / channel).

[0252] (3) adaptation of common signal / channel transmissions

[0253] Methods for reducing energy consumption by modulating the transmission of common signals / channels such as SSB, PRACH, and paging by the base station can be discussed. While completely disabling SSB can significantly reduce the energy consumption of the base station, the absence of SSB, which performs functions such as time / frequency synchronization and RRM measurement, may not guarantee stable operation for the corresponding cell from the UE's perspective. Considering this, energy savings at the base station can be achieved by varying the SSB transmission pattern (e.g., transmission period, period per SSB candidate index(es), SSB candidate index(es) transmitted within a transmission period, transmission power, etc.) depending on the situation.

[0254] In the case of PRACH resources, since the base station cannot know when the terminal will transmit the PRACH in the case of contention-based random access, energy consumption may increase because the base station always attempts to receive within the configured PRACH resources. Considering this, energy of the base station can be saved by applying a method to adjust the amount of PRACH resources (e.g., adjusting the period of PRACH resources, adjusting the amount of resources through instructions such as pre-configuring PRACH resource set #1 and set #2 and turning on only one set or both sets, or providing the corresponding RACH resource amount uniformly or non-uniformly for each SSB index).

[0255] In the case of paging, previously, paging frames (PF) and / or paging occasions (PO) were distributed along the time axis within a DRX cycle (or paging cycle), and the terminal attempted to receive paging at a specific PF / PO derived from its ID-based formula. From the base station's perspective, if paging was to be transmitted to multiple terminals simultaneously, it may have to wake up frequently to transmit paging. To reduce base station energy consumption due to this, it is possible to consider arranging PFs and / or POs for paging reception as close to the time axis as possible or arranging different frequency resources within the same time.

[0256] Uplink transmission based on CG (Configured Grant)

[0257] 5G NR Rel. 15 defines Configured Grant (CG)-based PUSCH transmission, which minimizes UL scheduling delays and schedule signaling overhead. 5G NR Rel. 18 introduces Unused Transmission Occasional-Uplink Control Information (UTO-UCI) transmission over CG PUSCH to more efficiently support XR traffic and other traffic. Table 1 provides information on UTO-UCI, extracted from Rel. 18 TS 38.213.

[0258]

[0259] Referring to Table 1, UTO-UCI has a subsequent future (valid) N(=O UTO-UCI ) The terminal determines whether (un)used for CG-PUSCH transmission occasions (TO) is N(=O) UTO-UCI ) can be signaled through bitmap information containing N(=O) bits. UTO-UCI) value can be set by the base station through upper layer signaling. If the bit is '1', the UE can inform the base station that the TO associated with the bit is unused (UE will not transmit CG-PUSCH), and if it is '0', the associated TO is used (UE may transmit CG-PUSCH). Meanwhile, the base station can utilize the CG-PUSCH TO that a UE has signaled as unused, and can achieve UL capacity enhancement effect, for example, by allocating it to the UL scheduling of another UE.

[0260] Figure 18 illustrates an example of an (un)used TO report via UTO UCI.

[0261] For convenience, it is assumed that the number of bits N included in the UTO UCI is set to 3. Referring to FIG. 18, since N=3, the UTO-UCI transmitted at TO#An includes unused or used information for the three subsequent TOs, TO#An+1 / n+2 / n+3. In FIG. 18, for each TO, 'O' indicates that the UE transmits CG-PUSCH in the corresponding TO, and 'X' indicates that the UE does not transmit CG-PUSCH in the corresponding TO. The UE can signal to the base station that CG-PUSCH transmission through TO#A4 will not be performed by transmitting '001' in TO#A1. Based on the information, the base station can schedule TO#A4 for uplink transmission of another UE, thereby obtaining the advantage of improved system throughput.

[0262] Based on the above discussion, new proposals for CG-based UL transmission are described below. The indices assigned to the proposals described below do not necessarily mean that each proposal is constructed in an independent form, and two or more proposals may be implemented in a form of at least a partial combination within a non-conflicting range. Furthermore, the description assumes that the signal to be transmitted for CG-based UL transmission is PUSCH, but the target signal is not limited to the name PUSCH, and various other UL channels / signals that transmit UL data / information may be the target of the proposed CG-based UL transmission. UTO UCI information may mean uplink control information for an unused TO, but it is not necessarily limited to an unused TO and may also mean information for a used TO, and the expression of UCI may be simply replaced with information.

[0263] In the following description, TO(s) may mean TO(s) for CG-PUSCH transmission configured / instructed by a base station for CG-PUSCH, or may mean TO(s) excluding TO(s) allocated as TO(s) for CG-PUSCH transmission but not transmitted due to at least one of the following reasons (i), (ii), (iii). For example, TO(s) may mean TO(s) itself based on RRC signaled CG configuration, or may mean only valid TOs among configured TO(s).

[0264] (i) CG-PUSCH overlapping with a signal / channel for time / frequency synchronization acquisition, such as SS / PBCH block (and / or CORESET#0) in the time and / or frequency domain (e.g., PUSCH collided with symbol(s) of an SS / PBCH block with index provided by ssb-PositionsInBurst);

[0265] (ii) CG-PUSCH overlapping in the time and / or frequency domain with a semi-statically signaled DL domain, such as RRC signaling (e.g., PUSCH collided with DL symbol(s) indicated by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated if provided);

[0266] (iii) CG-PUSCH that overlaps in time and / or frequency domain with the non-active or non-activated area of ​​Cell DRX.

[0267] According to the existing NR UTO UCI transmission method through CG PUSCH, if the UE does not have UL data (UL SCH) to transmit through CG-PUSCH, transmission can be skipped through the CG-PUSCH (with UTO-UCI). UTO UCI cannot be transmitted alone, and if the UE has no UL data to transmit, CG PUSCH transmission is not performed, and as a result, UTO UCI cannot be transmitted. In a situation where there is very little UL data to transmit, there is a disadvantage in that while the number of unused TOs increases, the opportunity to report unused TOs to the base station (e.g., CG PUSCH transmission due to UL data generation) actually decreases. In addition, the existing NR UTO-UCI has a limitation in that it can only signal TOs of CG-PUSCHs belonging to the same CG configuration.

[0268] Due to these limitations, in a UTO-UCI situation like that of FIG. 18, the UTO-UCI is not transmitted in TO#A4, and as a result, the base station cannot determine that the CG-PUSCH of the corresponding terminal will not be transmitted in TO#A7. Therefore, the base station misses the opportunity to utilize TO#A7, which is not being used by the terminal.

[0269] Even if the second CG-PUSCH is transmitted based on a different second CG configuration not illustrated in FIG. 18, there is a limitation that the UTO UCI included in the second CG PUSCH cannot report whether TO#A7 of the CG configuration illustrated in FIG. 18 is used or not (since the CG configurations are different). In this way, the UTO UCI reporting structure within the same CG configuration range limits the opportunity to report unused TOs to the base station.

[0270] Therefore, in one example of the present disclosure, a more efficient UTO-UCI structure and a signaling method for it are proposed to address this issue. Furthermore, considering that the frequency and / or volume of uplink traffic may vary over time, a resource request method for future TOs is additionally proposed.

[0271] [Proposal #1] (Un)used Signaling of CG-PUSCH TOs Belonging to Different CG Configuration Indexes (CG-conf)

[0272] For example, the UTO UCI of the first CG-PUSCH transmitted in the first TO based on the first CG configuration may include information on whether the subsequent second TO(s) set based on at least one second CG configuration is unused / used.

[0273] For example, the UTO UCI may include information on whether subsequent first TO(s) established based on the first CG configuration are unused / used and information on whether subsequent second TO(s) established based on at least one second CG configuration are unused / used. Alternatively, the UTO UCI may only include information on whether subsequent second TO(s) established based on the second CG configuration are unused / used.

[0274] The UTO-UCI of CG-PUSCH TO(s) belonging to one or more CG-conf(s) transmitted by the terminal may basically include first information for indicating the relevant CG-config and second information for indicating (un)used TO. For example, the proposed UTO-UCI may include or consist of a CG-conf indication + an (un)used TO indication.

[0275] For example, the CG-conf indication may consist of first bitmap information.

[0276] (i) Each bit of the first bitmap may be corresponded to one CG-conf (a single CG-conf index). Alternatively, multiple CG-confs (multiple CG-conf indices) may be allowed to correspond to each bit.

[0277] (ii) Alternatively, an index may be set / defined to represent the association between each bit and a CG configuration, rather than using the CG-conf index. For example, each bit may have an associated index, and one or more CG-confs may be associated with one index. For example, assuming that index 0 is associated with Bit 0 and index 1 is associated with Bit 1, index 0 may be assigned to CG configuration 0, and index 1 may be assigned to both CG configuration 1 and CG configuration 2.

[0278] The index below may mean (i) a CG configuration index or (ii) an index set / defined for the purpose of expressing the association between each bit and the CG configuration.

[0279] The association between each bit and index can be pre-established or determined by rules (e.g., lowest / highest index maps to LSB, next lowest / highest index maps to next LSB, ... highest / lowest index maps to MSB).

[0280] For example, if only one CG-conf can be indicated through the CG-conf indication, the CG-conf indication may be configured to directly indicate specific CG-conf index(es) values ​​rather than in the first bitmap format as above. In this case, the CG-conf indication may be configured to indicate an index other than its own CG-conf. In this case, even if there is no explicit index indication for its own CG-conf, not only the indicated index but also its own index may be considered to be signaled by default. For example, the CG-conf indication information that is actually signaled corresponds to other CG-conf index(es) for which the CG-PUSCH is not transmitted, and the (un)used TO indication for the CG-conf for which the CG-PUSCH is transmitted may be considered to always be signaled.

[0281] Specifically, the following methods may be available:

[0282] [Proposal #1-1] (un)used TO indication with as many bitmaps as CG-conf (group) that can be indicated through CG-conf indication

[0283] For example, an N-bit bitmap is allocated for a CG-conf indication, and the CG-conf corresponding to the n-th (n=0, 1, ..., N-1) bit of the bitmap can be one or more indices, and the mapping relationship can be set in advance or determined by a rule as described above. In addition, a K_n-bit bitmap can be configured as an example of the second information for (un)used TO indication for one or more indices corresponding to the n-th (n=0, 1, ..., N-1) bit, and the K_n value can be different or the same depending on the n value, and the K_n value can be a value set by the base station. Therefore, the UTO-UCI corresponding to the proposal #1-1 can be configured including a first bitmap having N bits and a second bitmap having {K_0 + K_1 + ... + K_N-1}-bits.

[0284] For example, if N=3 and each bit is associated with CG-conf #A / B / C, a {K_0+K_1+K_2}-bit bitmap can be configured for (un)used TO indication. That is, K_0-bit can be loaded for CG-conf #A, K_1-bit for CG-conf #B, and K_2-bit for CG-conf #C. If the N-bit bitmap information is '110', the terminal can configure the last K_2 bits corresponding to '0' value arbitrarily or as a predefined value (e.g., all zero or all one).

[0285] Meanwhile, if the indication is carried on CG-PUSCH belonging to CG-conf #A, the CG-conf indication consists of only 2 bits (for CG-conf #B / C, excluding 1 bit for CG-conf #A), and whether the K_0 bit corresponding to CG-conf #A is always (un)used can be signaled.

[0286] Additionally, the N-bit bitmap corresponding to the CG-conf indication may be omitted, in which case the instructions via the {K_0+K_1+K_2}-bit bitmap may always be valid.

[0287] In Proposal #1-1, the second bitmap can be expressed as a single second bitmap with {K_0 + K_1 + ... + K_N-1} bits concatenated, or as a second bitmap of K_0 bits, a second bitmap of K_1 bits, etc., with a total of N second bitmaps.

[0288] [Proposal #1-2] (un)used TO indication as a common single bitmap for CG-conf (group) that can be indicated via CG-conf indication

[0289] A first bitmap having N bits is allocated for a CG-conf indication, and the CG-conf corresponding to the n-th (n=0, 1, ..., N-1) bit of the first bitmap may be one or more indices, and the mapping relationship may be set in advance or determined by a rule as described above. In addition, a second bitmap having a single K_0-bit may be configured for an (un)used TO indication that commonly corresponds to the CG-conf index(es) linked to the first bitmap having N bits, and the K_0 value may be a value set by the base station. When indicated indices given through the first information (the first bit) exist, each bit of the second information (the second bitmap) (the (un)used TO indication by the corresponding bit) may be shared / common among the indicated indices.

[0290] Therefore, the UTO-UCI corresponding to the proposal #1-2 can be composed of a first bitmap having N bits and a second bitmap having K_0 bits, and the second bitmap having K_0 bits is set to be common to the indicated CG config, which has the advantage of reducing the signaling overhead of the UTO-UCI carried on the CG-PUSCH.

[0291] For example, if N=3 and each bit of the first bitmap is linked to CG-conf #A / B / C, a second bitmap of K_0-bit can be configured (only one) for (un)used TO indication. Second bitmap information of K_0-bit size that is commonly applied to CG-conf #A / B / C can be loaded. If the first bitmap information of 3-bit size is '110', the terminal can exclude the information for CG-conf #C corresponding to the value '0' and configure only the second bitmap information of K_0-bit size for CG-conf #A / B.

[0292] When the corresponding indication is carried on the CG-PUSCH belonging to CG-conf #A, the first bitmap corresponding to the CG-conf indication consists of only 2 bits (for CG-conf #B / C, excluding 1 bit for CG-conf #A), and whether the K_0 bit corresponding to CG-conf #A is always (un)used can be signaled.

[0293] Additionally, the first bitmap of N-bit size corresponding to the CG-conf indication may be omitted, in which case the second bitmap of K_0-bit size may be applied to all of CG-conf #A / B / C.

[0294] [Proposal #1-3] (un)used TO indication with bitmaps less than the number of CG config index (group) that can be indicated through the CG-conf indication

[0295] For CG-conf indication, a first bitmap of N-bit size is allocated, and the CG-conf corresponding to the n-th (n=0, 1, …, N-1) bit of the first bitmap can be one or more indices, and the mapping relationship as described above can be set in advance or determined by a rule.

[0296] Also, for (un)used TO indication, second bitmaps of size K_n-bit can be configured, and at this time, the maximum value that n can be is less than N-1 (for convenience, the maximum value that n can be is defined as X, and the corresponding X value or {X+1} value can be a value that is set or defined in advance), and the corresponding K_n value can be different or the same depending on the n value, and the K_n value can be a value set by the base station. The maximum value that can be indicated as '1' in the N-bit first bitmap is limited to X+1, and the second bitmap corresponding to K_0-bit corresponds to the CG-conf (group) indicated by the first '1' in the N-bit first bitmap, and the second bitmap corresponding to K_1-bit corresponds to the CG-conf (group) indicated by the second '1', … , the CG-conf (group) indicated by the X+1th '1' corresponds to the second bitmap corresponding to K_X-bit. Therefore, the UTO-UCI corresponding to the proposal #1-3 has a second bitmap of N-bit size and a second bitmap (X) of {K_0 + K_1 + … + K_X}-bit size. <N-1)으로 구성될 수 있다.

[0297] Proposals #1-3 may slightly increase the signaling overhead of UTO-UCI carried on CG-PUSCH, but may offer benefits in terms of signaling flexibility. Furthermore, compared to constructing a second bitmap for every index potentially indicated in the first bitmap, there may still be benefits in terms of signaling overhead.

[0298] For example, if N=3, X=1 and each bit of the first bitmap is linked to CG-conf #A / B / C, a second bitmap of {K_0+K_1}-bits can be configured for (un)used TO indication. Up to two indices can be signaled as '1' in the 3-bit first bitmap for CG-conf indication, and K_0-bit bitmap information can be carried for the CG config index corresponding to the first '1', and K_1-bit bitmap information can be carried for the CG config index corresponding to the second '1'. If the 3-bit first bitmap information is '100', the terminal can configure the last K_1 bits arbitrarily or as a predefined value (e.g., all zero or all one). If the indication belongs to CG-PUSCH belonging to CG-conf #A, the CG-conf indication may consist of only 1 bit (for one of CG-conf #B / C) and the K_0-bit corresponding to CG-conf #A may always be signaled as (un)used.

[0299] When applying the K_n-bit bitmap (where n is a value between 0 and N-1, and the range of possible n values ​​may vary depending on the proposals) information from at least one of the above proposals #1-x to one or more (non-UTO-UCI) CG-confs, the following examples may be used:

[0300] (Example 1) When a second bitmap information of one K_n bit size is commonly applied to multiple CG-confs: The second bitmap information is applied / configured to indicate an unused TO for a specific CG-conf (e.g., the CG-conf corresponding to the CG-PUSCH carrying the UTO-UCI, or the lowest / highest CG-conf, or a separately configured reference CG-conf), and the TO(s) of other CG-confs that overlap (or are included) in the unused TO (or the section spanned by the unused TOs) based on the specific CG-conf can also be regarded as unused TOs. In this case, the TO(s) of other CG-confs that do not overlap (or are not included) in the unused TO (or the section spanned by the unused TO (or the section from the start symbol of the unused TO to the section before the start symbol of the immediately next TO)) can be regarded as a used (or not-unused) TO. Alternatively, the second bitmap information may be applied to designate unused TO#1 for a specific CG-conf (e.g., the CG-conf corresponding to the CG-PUSCH carrying the UTO-UCI, or the lowest / highest CG-conf, or a separately configured reference CG-conf), and the TO(s) of other CG-confs that overlap or are nested (but do not overlap with TO#2) in the section from the unused TO#1 (the start symbol thereof) to the immediately following TO#2 (the start symbol thereof) may also be regarded as unused TOs. In this case, the TO(s) of other CG-confs that do not overlap or are nested (but do not overlap with TO#2) in the section from the unused TO#1 (the start symbol thereof) to the immediately following TO#2 (the start symbol thereof) may be regarded as used (or not-unused) TOs.

[0301] Figure 19 is a diagram illustrating an example of commonly applying second bitmap information to multiple CG-confs. Figure 19 may be related to the above (Example 1).

[0302] Referring to FIG. 19, there is CG-conf A that sets TOs corresponding to TO#An, CG-conf B that sets TOs corresponding to TO#Bn, and CG-conf C that sets TOs corresponding to TO#Cn. Based on the above [Proposal #1-2], UTO-UCI for CG-conf A / B / C can be transmitted through CG-conf A. Assume N=3.

[0303] - UTO-UCI in TO#A1: Since the first bitmap of N-bit size through TO#A1 is '101' information, the second bitmap of K_0-bit size, '001' information, is valid for CG-conf A / C. By signaling '001', the terminal can notify that TO#C2, which overlaps with TO#A4, an unused TO based on CG-conf A, is also an unused TO.

[0304] - UTO-UCI in TO#A3: Since the first bitmap of N-bit size through TO#A3 indicates '111' information, the '111' information of K_0-bit size bitmap is valid for all CG-conf A / B / C. The terminal can signal that TO#B4 / TO#B5 / TO#C2, which overlaps with the section spanned by TO#A4 / 5 / 6, which are unused TOs based on CG-conf A, are also unused TOs. Or, since the first bitmap of N-bit size is indicated with '111' information through TO#A3, it can be known that the second bitmap of K_0-bit size, '111' information, is valid for all of CG-conf A / B / C, and if the TOs of CG-conf B / C that overlap the section from the start symbol of TO#An, which is an unused TO, to the start symbol of TO#An+1 immediately following it with CG-conf A are considered unused TOs, then the terminal can signal that TO#B4 / TO#B5 / TO#B6 / TO#C2 / TO#C3 (or TO#B4 / TO#B5 / TO#B6 / TO#C2 excluding TO#C3 that overlaps with TO#A7) are also unused TOs. A similar method can also be applied to the case where there are multiple CG-conf indices corresponding to one bit that constitutes the N-bit first bitmap in [Proposal #1-1] or [Proposal #1-3].

[0305] (Example 2) When applying the second bitmap information of one K_n bit size to multiple CG-confs: (Alternatively to Example 1 above) The second bitmap information can be configured through the following process.

[0306] - When the TO with the earliest ending (or starting) symbol after the UTO-UCI transmission resource or after a certain period of time is called TO X1 and the TOs overlapping with TO X1 (including TO X1) are called Set A1, the Set A1 corresponds to the first bit in the second bitmap and the corresponding bit indication is commonly applied to the TOs in Set A1.

[0307] - When the TO with the fastest ending (or starting) symbol among the remaining TOs excluding the above Set A1 is called TO X2 and the TOs overlapping with the TO X2 (including TO X2) are called Set A2, the Set 2A corresponds to the second bit in the second bitmap and the bit instruction is commonly applied to the TOs in Set A2,

[0308] - The second bitmap information of size K_n-bit can be configured by repeating the above method.

[0309] (Example 3) When applying / configuring the second bitmap information of size K_n-bit (individually) for a CG-conf(s) (for convenience, the second CG-config) other than the CG-config (for convenience, the first CG-config) that sets the TO to which the UTO-UCI is transmitted: The second bitmap information can be applied / configured for the second CG-conf based on the first TO time point (or the CG-PUSCH time point on which the UTO-UCI is carried) of a specific CG-conf (e.g., the CG-conf corresponding to K_n-bit or the first CG-conf corresponding to the CG-PUSCH on which the UTO-UCI is carried or the lowest / highest CG-conf or a separately set reference CG-conf). Alternatively, the second bitmap may be configured / mapped to correspond to consecutive TOs starting from a TO that is thereafter or after a certain time based on the first TO point of time (or the CG-PUSCH point of time) of a specific CG-conf (e.g., the CG-conf corresponding to K_n-bit or the first CG-conf corresponding to the CG-PUSCH carrying the UTO-UCI or the lowest / highest CG-conf or a separately configured reference CG-conf) and applied to the corresponding second CG-conf.

[0310] Fig. 20 is a diagram illustrating an example of applying / configuring bitmap information representing (un)used TO to another CG-conf. Fig. 20 may be related to the above (Example 3).

[0311] Referring to Fig. 20, there is CG-conf A, which sets TOs corresponding to TO#An, and CG-conf B, which sets TOs corresponding to TO#Bn. UTO-UCI for CG-conf A / B can be transmitted by applying the above [Proposal #1-2] through CG-conf A. For convenience, N=2 is assumed. Since the first bitmap of N-bit size indicates '11' information through TO#A1, the second bitmap of K_0-bit size, '001' information, is valid for both CG-conf A / B. At this time, the '001' information corresponding to CG-conf B can be applied based on CG-conf B, and among the TOs of CG-conf B, the TO where the '001' starts to be applied can be TO#B1 based on TO#A1 where Opt1) UTO-UCI is loaded (or after a certain time after TO#A1), or TO#B2 based on TO#A2, which is the first TO indicated by UTO-UCI loaded in TO#A1 (or after a certain time after TO#A2). In case of Opt1, the '001' information corresponding to CG-conf B can be applied to TO#B1 / 2 / 3, and in case of Opt2, the '001' information corresponding to CG-conf B can be applied to TO#B2 / 3 / 4. The base station can set / indicate or define in advance whether it is Opt1 or Opt2. A similar method can also be applied when applying (individually) the second bitmap information of size K_n-bit to the second CG-conf, not the first CG-config that sets the TO to which UTO-UCI is transmitted in the above [Proposal #1-1] or [Proposal #1-3].

[0312] (Example 4) Alternatively, (rather than having the link relationship determined by rules as in the examples above) the TO(s) of the corresponding CG-conf(s) for each bit can be linked by presetting. For example, in the above-described Fig. 20, when the 3-bit second bitmap transmitted through UTO-UCI carried in TO#A1 is to be applied to CG-conf B, TO#Bn corresponding to each bit of the 3-bit second bitmap can be preset by the base station.

[0313] In at least one of the proposals and examples described in this specification, the number of (valid) bits of the second bitmap corresponding to another CG-conf B that does not provide the resource on which the UTO-UCI is transmitted (assuming that the TO_A window of the CG-conf A that provided the resource on which the UTO-UCI is carried can be predicted) may be constrained by the maximum number of TO_Bs of another CG-conf B that are confined to the TO_A window of the CG-conf A (wherein the TO_A window can be defined as the time interval between the closest TO_A and the farthest TO_A over which the UE can signal used / unused via the UTO-UCI) (e.g., bits that are constrained for the value of K_n or that do not correspond to TO_Bs confined to the TO_A window (e.g., within the TO_A window, the number of TO_As > the number of TO_Bs) may be signaled as reserved state or all zero or all one), or may be unrestricted by allowing the base station to configure it freely.

[0314] Meanwhile, some of the CG-conf(s) mapped to the CG-conf indication may be deactivated or released, which may need to be taken into account. For the released CG-conf, it may be signaled as unused (or a pre-configured / defined reserved state or all zero or all one) (considering that it may be activated again later), or (after a certain period of time after transmitting an ACK or confirmation MAC CE for the release) the bits (in the N-bit size first bitmap) and / or the K_n-bit size second bitmap) corresponding to the CG-conf may be removed and the UTO-UCI may be reconstructed.

[0315] To minimize confusion at the base station receiving the proposed UTO-UCI, a constraint can be added that a UE should not signal a TO marked as unused in CG-conf #A as used in the same CG-conf or in a different CG-conf. This is to maintain the consistency of the unused indication, which should be maintained across CG-configurations. In addition, the UE may not be allowed to override a past unused indication by later marking a TO as used in a subsequent UTO-UCI transmission that was previously marked as unused. For example, a UE that has marked TO#A as unused in a UTO-UCI#A transmission based on CG-conf #A may not be allowed to mark TO#A in CG-conf #A as used in a UTO-UCI#B transmission based on CG-conf #B. Alternatively, if this restriction is applied further, the terminal may not be allowed to mark TO#B of CG-conf #B as used if it overlaps with TO#A of CG-conf #A marked unused (within the same serving cell (or carrier / BWP)).

[0316] The other CG-conf described above can be extended to not only other CG-confs within the same serving cell, but also CG-confs set in other serving cells (or carriers / BWPs). If the sub-carrier spacing (SCS) between cells / carriers / BWPs is different, a scaling method that considers the difference between SCS#1 of CG-conf A where UTO-UCI is transmitted and SCS#2 of CG-conf B where the UTO-UCI is applied can be applied. For example, when SCS#1 is 15 kHz and SCS#2 is 30 kHz, the TO (window) corresponding to CG-conf A can be scaled by 2 (or 1 / 2) when applied to CG-conf B.

[0317] At least some of the basic setup and descriptions of Proposal #1 may be applied to the proposals described below, to the extent they do not conflict.

[0318] [Proposal #2] Non-bitmap signaling for (un)used TOs

[0319] We propose a structure and signaling method for secondary information other than bitmaps as a format for secondary information on used / unused TOs. Proposal #2 can replace all or part of the K_n-bit secondary bitmaps described in [Proposal #1] above. For example, the signaling of the method can be applied instead of the K_n-bit secondary bitmaps for all n values, or the K_n-bit secondary bitmaps can be utilized for some n values ​​and Proposal #2 can be applied for the remaining n values. Proposal #2 can have the advantage of reducing signaling overhead compared to bitmaps.

[0320] [Proposal #2-1] Indicate the start or end point of a used / unused TO, or signal the TO section.

[0321] When a UE signals whether N future (valid) CG-PUSCH TOs are (un)used, the UE may signal a specific time point X (e.g., before the first TO, between the nth TO and the n+1th TO, after the last TO, etc.). In this case, the required number of bits may be ceiling{log2(N+1)}. For example, when N=3, signaling may be performed using 2 bits (i.e., 4 states). The signaling information of the specific time point X may be specifically interpreted based on at least one of the following.

[0322] - Indicate the start point of Used TO as X: The terminal can indicate that from the indicated point X to the end (until the last point) are used TOs and the rest are unused TOs. For example, in the above example where N=3, if '00' is indicated, it can signal that all three TOs are used TOs (i.e., there are no unused TOs), if '01' is indicated, it can signal that the last two TOs are used TOs (i.e., the first TO is unused TO), and if '11' is indicated, it can signal that there are no used TOs (i.e., all three TOs are unused TOs).

[0323] - Indicate the end point of the used TO as X: The terminal can indicate that from the first point to the indicated point X, it is a used TO, and the rest is an unused TO. For example, in the above example where N=3, if '00' is indicated, it can signal that there is no used TO (i.e., all three TOs are unused TOs), if '01' is indicated, it can signal that the first TO is a used TO (i.e., the last two TOs are unused TOs), and if '11' is indicated, it can signal that all three TOs are used TOs (i.e., there are no unused TOs).

[0324] - Indicate the starting point of unused TO as X: The terminal can indicate that from the indicated point X to the end (until the last point) are unused TOs and the rest are used TOs. For example, in the above example where N=3, if '00' is indicated, it can signal that all three TOs are unused TOs (i.e., there are no used TOs), if '01' is indicated, it can signal that the last two TOs are unused TOs (i.e., the first TO is a used TO), and if '11' is indicated, it can signal that there are no unused TOs (i.e., all three TOs are used TOs).

[0325] - Indicate the end point of the unused TO as X: The terminal can indicate that from the first point to the indicated point X, there are unused TOs, and the rest are used TOs. For example, in the above example where N=3, if '00' is indicated, it can signal that there are no unused TOs (i.e., all three TOs are used TOs), if '01' is indicated, it can signal that the first TO is unused TO (i.e., the last two TOs are used TOs), and if '11' is indicated, it can signal that all three TOs are unused TOs (i.e., there are no used TOs).

[0326] Which of the above signaling methods is applied can be set / indicated by the base station, indicated by the terminal via CG-PUSCH, or determined in advance.

[0327] The above-described start / end point signaling method and the TO interval signaling method can be combined. For example, if a TO interval is signaled from a used (or unused) start point, the terminal can indicate that the TOs belonging to the TO interval are used (or unused) and the remaining TOs are unused (or used). The above-described start / end point and TO interval signaling method can be applied to the RIV (resource indication value) method utilized in NR downlink resource type 1.

[0328] The above signaling scheme can be useful in cases where there are consecutive Unused TOs and consecutive Used TOs, such as when used TOs are followed only by Unused TOs, or conversely, when used TOs are followed only by Unused TOs.

[0329] [Proposal #2-2] By indicating the HARQ process number (HPN), signaling used / unused for the TO corresponding to the HPN

[0330] Table 2 is an excerpt from TS 38.321 Rel.18. According to the current NR standard, the HPN for each TO of a CG-PUSCH can be determined by the formula in Table 2. Specifically, the HPN can be determined as a function of the timing parameters (e.g., symbols, periods, etc.) of the corresponding CG-PUSCH.

[0331]

[0332]

[0333] Considering that the HPN can be determined in advance for each TO of CG-PUSCH, used / unused information for each HPN (group) can be signaled, which has the advantage of reducing signaling overhead.

[0334] The signaling may consist of an H-bit bitmap, where the H value may be preset or defined by the base station (e.g., H=16 or maximum (configured) UL HPN). In addition, the HPN index corresponding to each bit may be preset by the base station or determined by a rule (e.g., the lowest / highest index HPN is mapped to the LSB, the next lowest / highest index HPN is mapped to the next LSB, ... the highest / lowest index HPN is mapped to the MSB), and one bit may be associated with more than one HPN index. In addition, when the UTO-UCI is transmitted via CG-PUSCH on a specific CG-conf, it may be applied only to the corresponding CG-conf (depending on the preset) or to other CG-confs (all or part thereof).

[0335] When H-bit bitmap information is signaled through CG-PUSCH of a specific TO#A, when there are (valid) TOs (corresponding to the associated CG-conf(s)) following TO#A, it can be signaled by the UE that the TO corresponding to the HPN whose bitmap information is '1' (or '0') is unused (or used). Additionally, a time duration to which the corresponding H-bit bitmap information applies can be defined, set by the base station, or signaled by the UE, and the bitmap information can be applied only to TOs that fall within the corresponding time duration (from the same reference point as TO#A) among the (valid) TOs (corresponding to the associated CG-conf(s)) following TO#A.

[0336] [Proposal #2-3] Instead of expressing used / unused information as a two-state like '0' or '1', express it as a tri-state.

[0337] CG-PUSCH resources indicated as unused through the used / unused information cannot be used by the corresponding UE again. On the other hand, even if a CG-PUSCH resource is indicated as used, the UE may not use it depending on the UL traffic situation. Therefore, by adding a state to the used / unused information, among the existing used resources, it is possible to distinguish between CG-PUSCH resources that the UE will definitely use and CG-PUSCH resources that may or may not be used. This allows the base station to utilize the latter CG-PUSCH resources for other UEs. An example of configuring a tri-state may be as follows.

[0338] (1) Alt 1

[0339] - X0: This is a TO that the terminal will use (since it is a resource that has already been configured for the UE), and the base station cannot send a message not to send the TO (e.g., in case of less than a certain number of repeated transmissions, or in case of relatively high QoS or priority).

[0340] - X1: A TO that the terminal can use, but the base station can send a message to the terminal not to send to the corresponding TO (e.g., in case of repeated transmission more than a certain number of times, or in case of relatively low QoS or priority).

[0341] - X2: TO not used by terminal

[0342] (2) Alt 2

[0343] - Y0: TO that the terminal must use (e.g., TO associated with high priority UL transmission)

[0344] - Y1: TO that the terminal may use (e.g., TO associated with low priority UL transmission)

[0345] - Y2: TO that the terminal will not use

[0346] One of the above {X0, X1, X2} or {Y0, Y1, Y2} can be signaled as one of the states {00, 01, 10, 11}, respectively. The base station can transmit signaling not to use the resources of the TO(s) indicated by 'X1' or 'Y1' (for the purpose of utilizing them for other resources / purposes), and the terminal can not transmit CG-PUSCH in the corresponding TO(s).

[0347] [Proposal #3] How to request resources for CG-PUSCH(s) corresponding to future (valid) N TO(s)

[0348] Considering that the UE can more accurately determine the occurrence frequency and / or amount of uplink traffic than the eNB, the pre-configured / indicated CG-PUSCH may be insufficient or too large to accommodate the traffic. In such cases, if the UE transmits information directly on the CG-PUSCH (e.g., UTO-UCI or information multiplexed and piggybacked onto existing UCI), it has the advantage of being able to adapt uplink resources more quickly than through the existing BSR (buffer status report).

[0349] At least one of the following information may be transmitted via CG-PUSCH for CG-PUSCH(s) corresponding to (valid) N TO(s) arriving in the future.

[0350] - MCS (modulation and coding scheme)

[0351] - Number of PRBs

[0352] - Number of symbols

[0353] - CG-PUSCH cycle

[0354] - Number of TOs per cycle when multiple TOs can be set for one CG-PUSCH cycle

[0355] Some or all of the above information can be linked to candidate values ​​in a table (by presetting), and the index value of the table can be signaled by the UE via CG-PUSCH. For example, {5 RBs, 10 symbols} can be linked to index 0 and {10 RBs, 14 symbols} can be linked to index 1, and the UE can signal index 0 (or index 1) via CG-PUSCH to inform the base station of the amount of resources it requires.

[0356] The resource information requested as above can be defined as being applied starting from T ms (or slots) or TO number after TO#A corresponding to CG-PUSCH carrying the information. At this time, the T value may be a value that is set or defined in advance. Alternatively, since the request of the terminal alone may be insufficient in terms of reliability, it can be defined that the resource information requested by the terminal (or the resource information carried in the signaling of the corresponding base station) is applied after the terminal receives confirmation through the signaling of the base station (e.g., DCI). At this time, it can be defined that the resource information requested by the terminal (or the resource information carried in the signaling of the corresponding base station) is applied starting from T ms (or slots) after the time point of receiving the signaling of the base station (or the HARQ feedback time point corresponding to the signaling of the base station). The T value may be a value that is set or defined in advance.

[0357] [Proposal #4] Introducing a separate format carrying UTO-UCI and / or the above signaling.

[0358] Information such as the proposed method can be transmitted in the form of a specific PUCCH (format) or sequence (e.g., Zadoff-Chu sequence, constant amplitude zero autocorrelation (CAZAC) sequence, computer-generated sequence). The base station can configure / instruct that the PUCCH format or sequence be transmitted at a time offset from a TO belonging to a specific CG-conf, and the offset value can be a time point after the TO (considering the processing time of the terminal) or a time point before the TO (considering the processing time of the base station). In addition, the periodicity at which the PUCCH format or sequence is transmitted can be configured. For example, the periodicity can be set to W times the CG periodicity configured in the associated CG-conf (the W value can be configured or defined in advance by the base station).

[0359] The TOs (and / or the number of TOs) corresponding to the information carried in the corresponding PUCCH format or sequence may be the TOs (and / or the number of TOs) of (corresponding and / or different) CG-conf(s) belonging to one period (or a multiple of a period) of the corresponding PUCCH format or sequence. Alternatively, the TOs (and / or the number of TOs) corresponding to the information carried in the corresponding PUCCH format or sequence may correspond to consecutive TOs starting from a TO that is thereafter or after a certain period of time based on the corresponding PUCCH format or sequence resource. The used / unused and / or resource request information for the corresponding TOs may be signaled by the methods proposed above.

[0360] FIG. 21 is a diagram illustrating an example of reporting (un)used TO using PUCCH.

[0361] Referring to FIG. 21, PUCCH resources are allocated from a point in time prior to an offset from a specific TO#A2 belonging to CG-conf A, and the period P2 of the PUCCH resources can be set to 5 times the period P1 of CG-conf A. The number of TOs corresponding to the used / unused information carried on each PUCCH can be 5, which is the number of TOs belonging to the P2 section, and PUCCH1 can carry bitmap information of '00111' for TO#A2 / 3 / 4 / 5 / 6, and PUCCH2 can carry bitmap information of '01111' for TO#A7 / 8 / 9 / 10 / 11.

[0362] There may be cases where information (and / or UTO-UCI) carried on a specific PUCCH (format) or sequence is multiplexed with other PUCCHs and / or PUSCHs and transmitted by a terminal. In this case, the information (and / or UTO-UCI) carried on a specific PUCCH (format) or sequence is treated as HARQ-ACK, and the beta_offset applied to HARQ-ACK (e.g., a parameter for determining the amount of HARQ-ACK resources in rate matching) is applied to the information, and when multiplexed with HARQ-ACK, the information may be placed after or before the HARQ-ACK. The priority index of the information may be preset or defined, or may follow the priority index set / indicated / defined in the linked CG-conf.

[0363] When simultaneously operating UTO-UCI via CG-PUSCH and information carried on a specific PUCCH (format) or sequence proposed in the method, transmitting both pieces of information may be inefficient. Therefore, information carried on a specific PUCCH (format) or sequence proposed may be transmitted only when the UE requires an update on used / unused information. Alternatively, information carried on a specific PUCCH (format) or sequence proposed may be transmitted only when the CG-PUSCH corresponding to the TO(s) immediately before and / or immediately after the specific PUCCH (format) or sequence is not transmitted.

[0364] Alternatively, the CG-PUSCH carrying the UTO-UCI using the method and / or the method(s) above may be specified to always be transmitted without skipping.

[0365] Figures 22 to 24 each summarize implementation examples for at least some of the embodiments described above. Any descriptions that overlap with those previously described may be omitted, and even without a separate description, the previously described content may be referenced for understanding Figures 22 to 24.

[0366] FIG. 22 is a diagram for explaining the operation of a terminal and a base station according to one embodiment.

[0367] Referring to FIG. 22, a terminal may receive information about multiple CG settings from a base station (A05). Information about the multiple CG settings may be received via higher-layer signaling. For example, at least one of the multiple CG settings may include parameters (e.g., N, K_n, etc.) for configuring / reporting the UTO information described above.

[0368] The terminal may determine whether subsequent CG PUSCH TOs are (un)used based on at least one of a plurality of CG configurations (A10). For example, the terminal may determine whether subsequent CG PUSCH TOs are (un)used and configure the UTO information to be included in the CG-PUSCH based on the first CG configuration. For example, the terminal may configure first information (e.g., N-bit bitmap) and / or second information (e.g., K_n-bit bitmap) as UTO information (e.g., used / unused information) of TOs linked to the plurality of CG configurations.

[0369] The terminal can transmit UTO information (A15).

[0370] The base station can determine the used / unused information of TOs belonging to multiple CG settings based on the received UTO information, and can schedule TO(s) marked as unused to other terminals when necessary (A20).

[0371] Figure 23 illustrates a flow of a method performed in a terminal according to one embodiment.

[0372] Referring to FIG. 23, a terminal can receive multiple CG (configured grant) settings for uplink transmission through upper layer signaling (B05).

[0373] The terminal can transmit a CG PUSCH (physical uplink shared channel) based on a first CG setting among the plurality of CG settings (B10).

[0374] The above CG PUSCH may include UTO (unused TO) information on whether subsequent CG PUSCH TOs (transmission occasions) will not be used by the terminal.

[0375] The above subsequent CG PUSCH TOs may be related to at least two CG settings.

[0376] The above UTO information may include first information indicating which CG settings are among the at least two CG settings related to the subsequent CG PUSCH TOs.

[0377] The above first information is a first bitmap including a plurality of bits, and each of the plurality of bits of the first bitmap can be associated with a CG setting.

[0378] The at least two CG settings include the first CG setting, and a plurality of bits of the first bitmap can be respectively associated with CG settings other than the first CG setting.

[0379] The above UTO information may include second information indicating whether subsequent CG PUSCH TOs will not be used individually for each of the at least two CG settings.

[0380] The second information may be a second bitmap, and the second bitmap for the first CG configuration among the at least two CG configurations may include first bits for first subsequent CG PUSCH TOs based on the first CG configuration, and the second bitmap for the second CG configuration among the at least two CG configurations may include second bits for second subsequent CG PUSCH TOs based on the second CG configuration.

[0381] The UTO information may include second information indicating whether subsequent CG PUSCH TOs common to the at least two CG configurations will not be used. For example, the at least two CG configurations may include a first CG configuration and a second CG configuration. The second information may be a second bitmap. A first bit of the second bitmap may indicate whether first sets of subsequent CG PUSCH TOs of the second CG configuration, which are determined based on a first subsequent CG PUSCH TO of the first CG configuration and the first subsequent CG PUSCH TO of the first CG configuration, will not be used by the terminal. A second bit of the second bitmap may indicate whether second sets of subsequent CG PUSCH TOs of the second CG configuration, which are determined based on a second subsequent CG PUSCH TO of the first CG configuration and the second subsequent CG PUSCH TO of the first CG configuration, will not be used by the terminal.

[0382] The above UTO information may include second information indicating at least one of a start point or an end point of subsequent CG PUSCH TOs used by the terminal, or a start point or an end point of subsequent CG PUSCH TOs not used by the terminal.

[0383] The above CG PUSCH may include information about at least one of a modulation and coding scheme (MCS) for the subsequent CG PUSCH TOs, frequency resource allocation, time resource allocation, CG-PUSCH period, or the number of CG PUSCH TOs per each CG-PUSCH period.

[0384] Figure 24 illustrates a flow of a method performed at a base station according to one embodiment.

[0385] Referring to FIG. 24, the base station can transmit multiple CG (configured grant) settings for uplink transmission of the terminal through upper layer signaling (C05).

[0386] The base station can receive a CG PUSCH (physical uplink shared channel) from the terminal based on a first CG setting among the plurality of CG settings (C10).

[0387] The above CG PUSCH may include UTO (unused TO) information on whether subsequent CG PUSCH TOs (transmission occasions) will not be used by the terminal.

[0388] The above subsequent CG PUSCH TOs may be related to at least two CG settings.

[0389] The above UTO information may include first information indicating which CG settings are among the at least two CG settings related to the subsequent CG PUSCH TOs.

[0390] The above first information is a first bitmap including a plurality of bits, and each of the plurality of bits of the first bitmap can be associated with a CG setting.

[0391] The at least two CG settings include the first CG setting, and a plurality of bits of the first bitmap can be respectively associated with CG settings other than the first CG setting.

[0392] The above UTO information may include second information indicating whether subsequent CG PUSCH TOs will not be used individually for each of the at least two CG settings.

[0393] The second information may be a second bitmap, and the second bitmap for the first CG configuration among the at least two CG configurations may include first bits for first subsequent CG PUSCH TOs based on the first CG configuration, and the second bitmap for the second CG configuration among the at least two CG configurations may include second bits for second subsequent CG PUSCH TOs based on the second CG configuration.

[0394] The UTO information may include second information indicating whether subsequent CG PUSCH TOs common to the at least two CG configurations will not be used. For example, the at least two CG configurations may include a first CG configuration and a second CG configuration. The second information may be a second bitmap. A first bit of the second bitmap may indicate whether first sets of subsequent CG PUSCH TOs of the second CG configuration, which are determined based on a first subsequent CG PUSCH TO of the first CG configuration and the first subsequent CG PUSCH TO of the first CG configuration, will not be used by the terminal. A second bit of the second bitmap may indicate whether second sets of subsequent CG PUSCH TOs of the second CG configuration, which are determined based on a second subsequent CG PUSCH TO of the first CG configuration and the second subsequent CG PUSCH TO of the first CG configuration, will not be used by the terminal.

[0395] The above UTO information may include second information indicating at least one of a start point or an end point of subsequent CG PUSCH TOs used by the terminal, or a start point or an end point of subsequent CG PUSCH TOs not used by the terminal.

[0396] The above CG PUSCH may include information about at least one of a modulation and coding scheme (MCS) for the subsequent CG PUSCH TOs, frequency resource allocation, time resource allocation, CG-PUSCH period, or the number of CG PUSCH TOs per each CG-PUSCH period.

[0397] The embodiments described above are combinations of components and features of the present disclosure in a predetermined form. Each component or feature should be considered optional unless explicitly stated otherwise. Each component or feature may be implemented without being combined with other components or features. Furthermore, it is also possible to form 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 self-evident that claims that do not have an explicit citation relationship in the patent claims may be combined to form embodiments or incorporated as new claims through post-application amendments.

[0398] It will be apparent to those skilled in the art that the present disclosure may be embodied in other specific forms without departing from the scope of the present disclosure. Therefore, the above detailed description should not be construed as limiting in any respect, but rather as illustrative. The scope of the present disclosure should be determined by a reasonable interpretation of the appended claims, and all modifications within the scope of equivalents of the present disclosure are intended to be included within the scope of the present disclosure.

[0399] 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, Receiving multiple CG (configured grant) settings for uplink transmission through upper layer signaling; and Including transmitting a CG PUSCH (physical uplink shared channel) based on a first CG configuration among the plurality of CG configurations, The above CG PUSCH includes UTO (unused TO) information on whether subsequent CG PUSCH TOs (transmission occasions) will not be used by the terminal. The above subsequent CG PUSCH TOs are related to at least two CG settings, A method wherein the UTO information includes first information indicating which CG settings are among the at least two CG settings related to the subsequent CG PUSCH TOs.

2. In paragraph 1, The first information is a first bitmap containing a plurality of bits, A method in which each of a plurality of bits of the first bitmap is associated with a CG setting.

3. In paragraph 2, The above at least two CG settings include the first CG setting, A method wherein a plurality of bits of the first bitmap are each associated with CG settings other than the first CG setting.

4. In paragraph 1, A method wherein the UTO information includes second information indicating whether subsequent CG PUSCH TOs will not be used individually for each of the at least two CG settings.

5. In paragraph 4, The above second information is a second bitmap, A second bitmap for the first CG setting among the at least two CG settings includes first bits for first subsequent CG PUSCH TOs based on the first CG setting, A method, wherein a second bitmap for a second CG setting among the at least two CG settings includes second bits for second subsequent CG PUSCH TOs based on the second CG setting.

6. In paragraph 1, A method wherein the UTO information includes second information indicating whether subsequent CG PUSCH TOs will not be used in common for the at least two CG settings.

7. In paragraph 6, The at least two CG settings include the first CG setting and the second CG setting, The above second information is a second bitmap, The first bit of the second bitmap indicates whether the first sets of subsequent CG PUSCH TOs of the second CG configuration determined based on the first subsequent CG PUSCH TO of the first CG configuration and the first subsequent CG PUSCH TO of the first CG configuration will not be used by the terminal, A method according to claim 1, wherein the second bit of the second bitmap indicates whether the second sets of subsequent CG PUSCH TOs of the second CG configuration determined based on the second subsequent CG PUSCH TO of the first CG configuration and the second subsequent CG PUSCH TO of the first CG configuration will not be used by the terminal.

8. In paragraph 1, A method wherein the UTO information includes second information indicating at least one of a start point or an end point of subsequent CG PUSCH TOs used by the terminal and a start point or an end point of subsequent CG PUSCH TOs not used by the terminal.

9. In paragraph 1, A method wherein the CG PUSCH includes information on at least one of a modulation and coding scheme (MCS) for the subsequent CG PUSCH TOs, frequency resource allocation, time resource allocation, CG-PUSCH period, or the number of CG PUSCH TOs per each CG-PUSCH period.

10. A non-transitory computer-readable recording medium having recorded thereon a program for performing the method described in paragraph 1.

11. In the device, at least one processor; and At least one memory configured to store instructions that are executed by said at least one processor to cause said at least one processor to perform operations, The operations of the above processor are: Receiving multiple CG (configured grant) settings for uplink transmission through upper layer signaling; and Including transmitting a CG PUSCH (physical uplink shared channel) based on a first CG configuration among the plurality of CG configurations, The above CG PUSCH includes UTO (unused TO) information on whether subsequent CG PUSCH TOs (transmission occasions) will not be used by the terminal. The above subsequent CG PUSCH TOs are related to at least two CG settings, A device wherein the UTO information includes first information indicating which CG settings are among the at least two CG settings related to the subsequent CG PUSCH TOs.

12. In paragraph 11, Including a transmitter and receiver, The above device is a terminal operating in a wireless communication system.

13. In paragraph 11, The above device is a processing device configured to control a terminal operating in a wireless communication system.

14. In a method performed by a base station, Transmitting multiple CG (configured grant) settings for uplink transmission of the terminal through upper layer signaling; and Including receiving a CG PUSCH (physical uplink shared channel) from the terminal based on a first CG setting among the plurality of CG settings, The above CG PUSCH includes UTO (unused TO) information on whether subsequent CG PUSCH TOs (transmission occasions) will not be used by the terminal. The above subsequent CG PUSCH TOs are related to at least two CG settings, A method wherein the UTO information includes first information indicating which CG settings are among the at least two CG settings related to the subsequent CG PUSCH TOs.

15. At the base station, at least one processor; and At least one memory configured to store instructions that are executed by said at least one processor to cause said at least one processor to perform operations, The operations of the above processor are: Transmitting multiple CG (configured grant) settings for uplink transmission of the terminal through upper layer signaling; and Including receiving a CG PUSCH (physical uplink shared channel) from the terminal based on a first CG setting among the plurality of CG settings, The above CG PUSCH includes UTO (unused TO) information on whether subsequent CG PUSCH TOs (transmission occasions) will not be used by the terminal. The above subsequent CG PUSCH TOs are related to at least two CG settings, A base station, wherein the UTO information includes first information indicating which CG settings are among the at least two CG settings related to the subsequent CG PUSCH TOs.

Images