Method for receiving downlink signal in wireless communication system and base station using the same

Abstract

The present invention relates to a method of receiving a downlink signal in a wireless communication system and a terminal using the same. A method and apparatus for receiving a downlink signal in a wireless communication system are provided. The method includes receiving resource block assignment information including a bitmap, and receiving a downlink signal through resource block groups (RBGs) indicated by the bitmap in a bandwidth part. A total number of resource block groups (RBGs) in the bandwidth part is determined based on an index of a starting resource block of the bandwidth part, a size of the bandwidth part, and a size of one resource block group.

Description

[0001] This application is a divisional application of patent application No. 201880028284.1 (PCT / KR2018 / 007262), filed in China on October 29, 2019, with an international application date of June 27, 2018, entitled "Method for Receiving Downlink Signals in a Wireless Communication System and Terminal Using the Same". Technical Field

[0002] This disclosure relates to wireless communication, and more specifically, to a method for receiving downlink signals by a terminal (or user equipment (UE)) in a wireless communication system and a terminal using the method. Background Technology

[0003] As communication devices increasingly require greater communication capacity, there has been a need to improve mobile broadband communications relative to existing radio access technologies (RATs). Furthermore, massive machine-type communications (MTC), which provides many different services by connecting multiple devices and objects, is also one of the major issues to be considered in next-generation communications.

[0004] The discussion also considers communication systems for services or terminals that are susceptible to reliability or latency issues, as well as next-generation RATs that consider improvements to mobile broadband communications, massive MTC, ultra-reliable low-latency communications (URLLC), etc., which may also be referred to as new RATs or new radios (NR).

[0005] In future wireless communication systems, a bandwidth portion can be introduced. This bandwidth portion can be used to allocate certain frequency bands to terminals that struggle to support broadband in existing broadband wireless communication systems. Resources allocated to the UE within this bandwidth portion can be allocated in units of Resource Block Groups (RBGs), and determining the number of RBGs within this bandwidth portion may be a challenge.

[0006] Additionally, the BS can use interleaving when allocating resources to the UE. Interleaving maps virtual resource blocks, which are logical resource blocks, to physical resource blocks. Interleaving units can be resource block bundles, and the relationship between the boundaries of the resource block bundles and the boundaries of the physical resource blocks needs to be defined. Summary of the Invention

[0007] This disclosure provides a method for receiving downlink signals by a terminal (or user equipment (UE)) in a wireless communication system, and a terminal using the method.

[0008] In one aspect, a method for receiving downlink signals in a wireless communication system is provided. The method includes receiving resource block assignment information including a bitmap and receiving the downlink signals through resource block groups (RBGs) indicated by the bitmap in a bandwidth portion. The total number of resource block groups (RBGs) in the bandwidth portion is determined based on the index of the starting resource block of the bandwidth portion, the size of the bandwidth portion, and the size of a resource block group.

[0009] When the bandwidth component is the i-th bandwidth component (i is 0 or a natural number), the total number of RBGs (N) RBG It can be determined by the following equation:

[0010]

[0011] Where, N start BWP,i N represents the index of the starting resource block of the i-th bandwidth segment. size BWP,i Let P represent the size of the i-th bandwidth portion, and let P represent the size of an RBG.

[0012] The number of bits in a bitmap can be equal to the total number of RGB values ​​(N). RBG ).

[0013] P can be selected from the candidate values ​​previously set via Radio Resource Control (RRC) messages, based on the size of the bandwidth portion.

[0014] The bits in the bitmap correspond to the RBGs of the bandwidth portion to indicate whether each RBG is allocated.

[0015] On the other hand, a terminal is provided. The terminal includes a transceiver that transmits and receives wireless signals; and a processor coupled to the transceiver for operation. The processor receives resource block assignment information including a bitmap and receives downlink signals through resource block groups (RBGs) indicated by the bitmap in a bandwidth portion. The total number of resource block groups (RBGs) in the bandwidth portion is determined based on the index of the starting resource block of the bandwidth portion, the size of the bandwidth portion, and the size of a resource block group.

[0016] Beneficial effects

[0017] In next-generation wireless communication systems such as NR, this invention provides a method for determining the number of resource allocation units (e.g., RBGs) and is capable of determining the size of the resource allocation field in the frequency domain. Frequency domain resource allocation can be performed efficiently without wasting bits in the resource allocation field. Attached Figure Description

[0018] Figure 1 This illustrates a traditional wireless communication system.

[0019] Figure 2 This is a diagram illustrating the radio protocol architecture used for the user plane.

[0020] Figure 3 This is a diagram illustrating the radio protocol architecture used for the control plane.

[0021] Figure 4 The diagram illustrates the system architecture of a next-generation radio access network (NG-RAN) using NR.

[0022] Figure 5 The diagram illustrates the frame structure that can be applied in NR.

[0023] Figure 6 The diagram shows CORESET.

[0024] Figure 7 This is a diagram illustrating the differences between the existing technology control area and the CORESET in NR.

[0025] Figure 8 The diagram illustrates the carrier bandwidth portion newly introduced into NR.

[0026] Figure 9 The illustration shows an example of resource allocation type 1.

[0027] Figure 10 The diagram illustrates an example of a transition area configuration.

[0028] Figure 11 The diagram illustrates terminal operations related to downlink resource allocation.

[0029] Figure 12 The diagram confirms that N is included. size BWP,i The number of RBGs (N) of the downlink carrier bandwidth portion i of each PRB RBG Examples of ).

[0030] Figure 13 The illustration shows an example of aligning the boundary between the RB bundle used for interleaving and the CRB of resource allocation type 1.

[0031] Figure 14 This is a block diagram illustrating an apparatus for implementing an embodiment of the present disclosure. Detailed Implementation

[0032] Figure 1 This illustrates a conventional wireless communication system. For example, a wireless communication system may be referred to as the Evolved UMTS Terrestrial Radio Access Network (E-UTRAN) or a Long Term Evolution (LTE) / LTE-A system.

[0033] E-UTRAN includes at least one base station (BS) 20 that provides a control plane and a user plane to a user equipment (UE) 10. The UE 10 can be fixed or mobile and can be referred to by other terms such as mobile station (MS), user terminal (UT), subscriber station (SS), mobile terminal (MT), radio equipment, etc. The BS 20 is typically a fixed station that communicates with the UE 10 and can be referred to by other terms such as evolved Node B (eNB), base transceiver system (BTS), access point, etc.

[0034] BS 20 interconnects with each other via the X2 interface. BS 20 also connects to the evolved packet core (EPC) 30 via the S1 interface, and more specifically, to the mobility management entity (MME) via the S1-MME, and to the serving gateway (S-GW) via the S1-U.

[0035] EPC 30 includes an MME, an S-GW, and a Packet Data Network Gateway (P-GW). The MME holds UE access information or UE capability information, and this information is typically used for UE mobility management. The S-GW is a gateway with an E-UTRAN as its endpoint. The P-GW is a gateway with a PDN as its endpoint.

[0036] Based on the three layers of the Open Systems Interconnection (OSI) model, which is well-known in communication systems, the radio interface protocol between the UE and the network can be divided into Layer 1 (L1), Layer 2 (L2), and Layer 3 (L3). Among these, the Physical (PHY) layer, belonging to Layer 1, provides information transmission services using physical channels, while the Radio Resource Control (RRC) layer, belonging to Layer 3, controls radio resources between the UE and the network. For this purpose, the RRC layer exchanges RRC messages between the UE and the BS.

[0037] Figure 2 This is a diagram illustrating the radio protocol architecture used for the user plane. Figure 3 This is a diagram illustrating the radio protocol architecture used for the control plane. The user plane is the protocol stack used for user data transmission. The control plane is the protocol stack used for control signal transmission.

[0038] refer to Figure 2 and 3 The PHY layer provides information transmission services to higher layers via physical channels. The PHY layer connects to the Media Access Control (MAC) layer via a transport channel, which is the layer above the PHY layer. Data is transmitted between the MAC and PHY layers via the transport channel. Transport channels are classified according to how data is transmitted via the radio interface and what characteristics of the data are transmitted.

[0039] Through the physical channel, data moves between different PHY layers, namely the PHY layer of the transmitter and the PHY layer of the receiver. The physical channel can be modulated according to an orthogonal frequency division multiplexing (OFDM) scheme and uses time and frequency as radio resources.

[0040] The functions of the MAC layer include mapping between logical channels and transport channels, and multiplexing / demultiplexing transport blocks provided via physical channels on the transport channel of MAC Service Data Units (SDUs) belonging to logical channels. The MAC layer provides services to the Radio Link Control (RLC) layer through logical channels.

[0041] The RLC layer's functions include the cascading, splitting, and reassembling of RLC SDUs. To ensure various types of Quality of Service (QoS) requirements for radio bearers (RBs), the RLC layer provides three operating modes: Transparent Mode (TM), Unacknowledged Mode (UM), and Acknowledged Mode (AM). AM RLC provides error correction through Automatic Repeat Request (ARQ).

[0042] The RRC layer is defined only in the control plane. The RRC layer is related to the configuration, reconfiguration, and release of radio bearers, and is responsible for the control of logical channels, transport channels, and physical (PHY) channels. RB refers to the logical routing provided by Layer 1 (PHY layer) and Layer 2 (MAC layer, RLC layer, and PDCP layer) to facilitate data transmission between the UE and the network.

[0043] The Packet Data Convergence Protocol (PDCP) layer on the user plane performs functions including the transmission of user data and header compression and encryption. The PDCP layer on the control plane performs functions including the transmission of control plane data and encryption / integrity protection.

[0044] RB configuration refers to the process of defining the characteristics of the radio protocol layer and channel to provide specific services and configuring each detailed parameter and operation method. RBs can be divided into two types: signaling RBs (SRBs) and data RBs (DRBs). SRBs are used as channels to transmit RRC messages on the control plane, while DRBs are used as channels to transmit user data on the user plane.

[0045] If an RRC connection is established between the UE's RRC layer and the E-UTRAN's RRC layer, the UE is in an RRC connected state. Otherwise, the UE is in an RRC idle state.

[0046] The downlink transport channels through which data is transmitted from the network to the UE include the Broadcast Channel (BCH) for transmitting system information and the Shared Downlink Channel (SCH) for transmitting user service or control messages. Service or control messages used for downlink multicast or broadcast services can be transmitted via the downlink SCH or via the Additional Downlink Multicast Channel (MCH). Meanwhile, the uplink transport channels through which data is transmitted from the UE to the network include the Random Access Channel (RACH) for transmitting initial control messages and the Shared Uplink Channel (SCH) for transmitting user service or control messages.

[0047] Logical channels placed above and mapped to the transport channel include the Broadcast Control Channel (BCCH), Paging Control Channel (PCCH), Common Control Channel (CCCH), Multicast Control Channel (MCCH), and Multicast Service Channel (MTCH).

[0048] A physical channel comprises several OFDM symbols in the time domain and several subcarriers in the frequency domain. A subframe comprises multiple OFDM symbols in the time domain. An RB (Resource Allocation Unit) is a resource allocation unit and comprises multiple OFDM symbols and multiple subcarriers. Furthermore, each subframe may use specific subcarriers of a specific OFDM symbol (e.g., the first OFDM symbol) for the Physical Downlink Control Channel (PDCCH), i.e., the L1 / L2 control channel. The Transmission Time Interval (TTI) is the unit of time used for subframe transmission.

[0049] The following text will describe the new radio access technology (new RAT) or new radio (NR).

[0050] As communication devices increasingly require greater communication capacity, the need has arisen to improve mobile broadband communications relative to existing radio access technologies (RATs). Furthermore, massive machine-type communication (MTC), which provides many different services by connecting multiple devices and objects, is also one of the main issues to be considered in next-generation communications. In addition, communication system designs considering services or terminals susceptible to reliability or latency issues have been discussed. The introduction of next-generation RATs considering enhanced mobile broadband communications, massive MTC, ultra-reliable low-latency communication (URLLC), etc., has been discussed, and in this disclosure, for the purposes of description, the corresponding technologies will be referred to as new RATs or new radios (NR).

[0051] Figure 4 The system architecture of a next-generation radio access network (NG-RAN) using NR is shown.

[0052] refer to Figure 4NG-RAN may include gNBs and / or eNBs that provide user plane and control plane protocol termination to terminals. Figure 4 The diagram illustrates the case involving only the gNB. The gNB and eNB are connected via the Xn interface. The gNB and eNB are connected to the 5G core network (5GC) via the NG interface. More specifically, the gNB and eNB are connected to the Access and Mobility Management Function (AMF) via the NG-C interface and to the User Plane Function (UPF) via the NG-U interface.

[0053] gNB can provide functions such as inter-cell radio resource management (inter-cell RRM), radio bearer management (RB control), connection mobility control, radio access control, measurement configuration and provisioning, and dynamic resource allocation. AMF can provide functions such as NAS security and idle state mobility processing. UPF can provide functions such as mobility anchoring and PDU processing.

[0054] Figure 5 The diagram illustrates the frame structure that can be applied in NR.

[0055] refer to Figure 5 A frame can consist of 10 milliseconds (ms) and include 10 subframes, each consisting of 1 ms.

[0056] Depending on the subcarrier spacing, one or more time slots can be included in a subframe.

[0057] The following table shows the subcarrier spacing configuration μ.

[0058] [Table 1]

[0059]

[0060] Based on the subcarrier spacing configuration μ, the following table shows the number of time slots (N) in the frame. frame,μ slot ), number of time slots in subframes (N) subframe,μ slot ), Number of symbols in a time slot (N) slot symb )etc.

[0061] [Table 2]

[0062]

[0063] exist Figure 5 In the diagram, μ = 0, 1, 2.

[0064] A time slot can include multiple Orthogonal Frequency Division Multiplexing (OFDM) symbols. These OFDM symbols can be classified as downlink (indicated by D), flexible (indicated by X), and uplink (indicated by U). The format of a time slot can be determined based on which of the OFDM symbols in the time slot is configured as D, X, or U.

[0065] The following shows an example of a time slot format.

[0066] [Table 3]

[0067]

[0068]

[0069] The format of the terminal's time slots can be configured via higher-layer signaling, via DCI, or based on a combination of higher-layer signaling and DCI.

[0070] The Physical Downlink Control Channel (PDCCH) may include one or more Control Channel Elements (CCEs), as illustrated in the table below.

[0071] [Table 4]

[0072] Aggregation Level Number of CCEs 1 1 2 2 4 4 8 8 16 16

[0073] In other words, PDCCH can be transmitted using resources comprising 1, 2, 4, 8, or 16 CCEs. Here, a CCE comprises six Resource Element Groups (REGs), and a REG comprises a resource block in the frequency domain and an orthogonal frequency division multiplexing (OFDM) symbol in the time domain.

[0074] Meanwhile, in future wireless communication systems, a new unit called the Control Resource Set (CORESET) can be introduced. Terminals can receive PDCCHs in the CORESET.

[0075] Figure 6 The diagram shows CORESET.

[0076] refer to Figure 6 CORESET includes N in the frequency domain. CORESET RB The number of resource blocks, and N in the time domain CORESET symb The symbol for the quantity ∈{1,2,3}. N CORESET RB and N CORESET symb This can be provided by the base station via higher-layer signaling. For example... Figure 6 As shown in the diagram, a CORESET can include multiple CCEs (or REGs).

[0077] The UE can attempt to detect PDCCH in units of 1, 2, 4, 8, or 16 CCEs in the CORESET. One or more CCEs that can be attempted for PDCCH detection can be referred to as PDCCH candidates.

[0078] Multiple CORESETs can be configured for the terminal.

[0079] Figure 7 This is a diagram illustrating the differences between the existing technology control area and the CORESET in NR.

[0080] refer to Figure 7 The control area 300 of an existing wireless communication system (e.g., LTE / LTE-A) is configured across the entire system frequency band used by the base station (BS). All terminals, except for a few that only support narrowband (e.g., eMTC / NB-IoT terminals), must be able to receive wireless signals across the entire system frequency band of the BS in order to properly receive / decode control information transmitted by the BS.

[0081] In contrast, future wireless communication systems introduce the aforementioned CORESETs. CORESETs 301, 302, and 303 are radio resources used for control information to be received by the terminal, and can utilize only a portion of the system bandwidth instead of the entire system bandwidth. The BS can allocate CORESETs to each UE and can transmit control information through the allocated CORESETs. For example, in Figure 7 In NR, the first CORESET 301 can be assigned to UE 1, the second CORESET 302 can be assigned to UE 2, and the third CORESET 303 can be assigned to UE 3. In NR, the terminal can receive control information from the BS without having to receive the entire system frequency band.

[0082] CORESET can include UE-specific CORESET for sending UE-specific control information and public CORESET for sending control information common to all UEs.

[0083] Figure 8 The diagram illustrates the carrier bandwidth portion newly introduced into NR.

[0084] refer to Figure 8 The carrier bandwidth portion can be simply referred to as the bandwidth portion (BWP). As mentioned above, in future wireless communication systems, various parameter sets (e.g., various subcarrier spacings) can be supported for the same carrier. NR can define a common resource block (CRB) for a given parameter set in a given carrier.

[0085] The bandwidth component is a set of consecutive physical resource blocks (PRBs) selected from a consecutive subset of common resource blocks (CRBs) with a given set of parameters in a given carrier.

[0086] like Figure 8 As illustrated, common resource blocks can be determined based on which set of parameters, such as which subcarrier interval and which carrier bandwidth is used. Common resource blocks can be indexed starting from the lowest frequency of the carrier bandwidth (starting from 0), and a resource grid (which can be called a common resource block resource grid) can be defined with common resource blocks as units.

[0087] The bandwidth portion can be indicated based on the CRB with the lowest index (which can be referred to as "CRB 0"). CRB 0 with the lowest index can also be referred to as "point A".

[0088] For example, in a given parameter set for a given carrier, the i-th bandwidth portion (BWP) can be determined by N. start BWP,i and N size BWP,i Instructions. N start BWP,i The starting CRB of the i-th BWP can be indicated based on CRB 0, and N size BWP,i This can indicate the size of the i-th BWP in the frequency domain (e.g., in PRBs). The PRBs of each BWP can be indexed starting from zero. The index of the CRB of each BWP can be mapped to the index of the PRB. For example, a mapping can be performed such that n CRB =n PRB +N start BWP,i .

[0089] In the downlink, up to four downlink bandwidth sections can be configured for the UE, but only one downlink bandwidth section can be active at a given time. The UE does not expect to receive PDSCH, PDCCH, CSI-RS, etc. in any downlink bandwidth section other than the active downlink bandwidth section. Each downlink bandwidth section may include at least one CORESET.

[0090] In the uplink, up to four uplink bandwidth portions can be configured for the UE, but only one uplink bandwidth portion can be active at a given time. The UE does not send PUSCH, PUCCH, etc. in any uplink bandwidth portion other than the active one.

[0091] Compared to traditional systems, NR operates in broadband, and not all terminals can support this broadband. The characteristic of the Bandwidth Partial (BWP) is that it is operable even for terminals that may not support broadband.

[0092] Resource allocation types will now be described. Resource allocation types specify how the scheduler (e.g., the BS) allocates resource blocks for each transmission. For example, when the BS allocates bandwidth to the UE comprising multiple resource blocks, the BS can inform the UE about the resource blocks allocated to the UE through a bitmap consisting of bits corresponding to the resource blocks of the bandwidth. In this case, the flexibility of resource allocation can be increased, but disadvantageously, the amount of information used for resource allocation is increased.

[0093] Taking into account these advantages and disadvantages, the following three resource allocation types can be defined / used.

[0094] 1) Resource allocation type 0 allocates resources via a bitmap, where each bit of the bitmap indicates a resource block group (RBG) rather than a resource block. That is, in resource allocation type 0, resource allocation is performed at the resource block group level, not at the resource block level. The table below illustrates this when the system has N... DL RB The size of the RBG used when a resource block is composed.

[0095] [Table 5]

[0096]

[0097] 2) Resource allocation type 1 is a method of allocating resources based on RBG subsets. An RBG subset can include multiple RBGs. For example, RBG subset #0 includes RBGs #0, 3, 6, 9..., RBG subset #1 includes RBGs #1, 4, 7, 10..., RBG subset #2 includes RBGs #2, 5, 8, 11..., and so on. The number of RBGs included in an RBG subset and the number of resource blocks (RBs) included in an RBG are configured to be equal. Resource allocation type 1 indicates which RBG subset is used and which RBs are used within the currently used RBG subset.

[0098] 3) Resource allocation type 2 is a method of allocating resources by notifying the starting position (RB number) of the allocated bandwidth and the number of contiguous resource blocks. Contiguous resource blocks can start from a starting position. However, it should be understood that contiguous resource blocks are not necessarily physically contiguous, but can mean that the logical or virtual resource block indices are contiguous.

[0099] In future wireless communication systems, the number of resource blocks constituting an RBG (or RB group) can be flexibly changed. Here, information for the RBG, such as information indicating the number of resource blocks constituting the RBG, can be transmitted via scheduling DCI, third physical layer (L1) signaling, or higher-layer signaling such as RRC messages.

[0100] Furthermore, in future wireless communication systems, in addition to information about the frequency domain, resource allocation information may include information about the time domain, and the specific information included and the manner in which it is included can be flexibly changed.

[0101] This disclosure proposes a resource allocation method for PDSCH and / or PUSCH when the field size and / or analysis method used for resource allocation changes. In the following embodiments, for ease of explanation, a bitmap scheme based on RBG is assumed when the RBG size is flexible; however, it can be extended to cases where the granularity of resource allocation changes and / or the resource allocation scheme changes accordingly, etc.

[0102] In embodiments of this disclosure, resource allocation schemes (specifically, RBG sizes or grid contents) can be applied to resource areas that can be mapped to at least only PDSCH or PUSCH. Other resource allocation techniques (RBG sizes or grids) can be applied to other resource areas. For example, when a specific resource in a PDCCH area is used for PDSCH mapping, the RBG size and other RBG sizes in the corresponding area can be set or indicated independently.

[0103] In another example, when performing resource allocation for PDSCH or PUSCH on multiple carriers or bandwidth portions, the RBG size can be set / indicated differently or independently for each carrier or bandwidth portion.

[0104] In embodiments of this disclosure, it is assumed that the size of the RBG is flexibly changed (or indicated in the DCI), but this disclosure can also be extended to situations where the number of RBGs, which can be indicated by the Resource Allocation (RA) field, is flexibly changed (or indicated in the DCI).

[0105] <Dynamic field size used for time and / or frequency resource allocation>

[0106] In the following embodiments, RBG can be considered as a value representing frequency domain granularity. The size of RBG can be flexibly changed. Therefore, when using RBG, the size of the resource allocation field in the frequency domain can also be flexibly changed.

[0107] Having a larger RBG size to indicate a large area (e.g., the entire terminal bandwidth or system bandwidth) via the frequency axis can be advantageous. Conversely, having a smaller RBG size to indicate a small area (e.g., one or more physical resource blocks) via the frequency axis can be advantageous.

[0108] While maximizing scheduling flexibility via the frequency axis, the required resource allocation field size may become excessively large if the RBG size is small (compared to a larger RBG size).

[0109] For example, when the RBG size is set to 10 in a bandwidth BW consisting of 50 physical resource blocks (PRBs), the frequency axis resource allocation field in the bitmap scheme can consist of 5 bits. Meanwhile, if the RBG size is 2, the frequency axis resource allocation field can consist of 25 bits.

[0110] The resource allocation field is included in the DCI. For blind decoding / detection from the UE's location, maintaining either the entire DCI size or the entire resource allocation field size may be advantageous.

[0111] The bits of the resource allocation field, which vary depending on the chosen RBG size, can primarily be used to perform time-domain resource allocation. The allocation methods for time-domain and / or frequency-domain resources can differ depending on the indicated RBG size.

[0112] The following are examples of resource allocation schemes based on RBG size. All or some combinations of the following schemes can be used for time and frequency resource allocation.

[0113] 1) If the RBG size is equal to or less than a specific level (N) low If the resource allocation field is specified, the indication can be limited to resources in the frequency domain. The specific level can be the preset default RBG size, or it can be set at a higher level.

[0114] When the RBG size is equal to or less than a specific level, resource allocation in the time domain is predetermined. Alternatively, resource allocation can be performed across the entire PDSCH mapping area or on the PUSCH mapping area determined by higher-level signaling or slot type format (on the time axis). Alternatively, the time-domain resources targeted for resource allocation can be individually indicated by higher-level signaling, information about the slot type format, etc.

[0115] If a default time-domain resource is used, the default time-domain resource (e.g., PDSCH or PUSCH for the entire time slot) can be predetermined. Alternatively, if time-slot type-related information is dynamically indicated, the time-domain information can be dynamically changed within the time slot based on the time-slot type-related information. Alternatively, when sending time-slot type-related information, the start point and duration of the PDSCH or PUSCH can be pre-configured via higher-layer signaling to ensure reliability. Or, even when time-slot type-related information is not sent, higher-layer signaling can be considered similarly.

[0116] 2) If the RBG size exceeds a specific level (N) high If the resource allocation field indicates that the resource allocation is limited to resources in the time domain, then more specifically, the RBG size can be the same as or equivalent to the system bandwidth or terminal bandwidth. In this case, in the frequency domain resource allocation, either RBG can be allocated for either PDSCH or PUSCH transmissions (based on the indicated RBG size).

[0117] 3) When the RBG size is within a specific range (e.g., when the RBG size is within N...) low and N high (In between), the resource allocation field can indicate time and frequency resources. More specifically, some bits of the resource allocation field can be used to indicate frequency domain resource allocation, and other bits can be used to indicate time domain resource allocation.

[0118] For example, frequency domain resource allocation can indicate the RBG to be allocated at an indicated RBG size. Time domain resource allocation can indicate which RBGs to be allocated by a predetermined or indicated time domain scheduling unit. Alternatively, time domain resource allocation can be provided in the form of patterns, and the number of patterns can vary depending on the bits used for time domain resource allocation.

[0119] Alternatively, time-domain resource allocation and frequency-domain resource allocation can be performed jointly. Specifically, information about the allocated time and frequency resource pairs can be configured in the form of multiple patterns. Moreover, the bits of the entire resource allocation field can indicate the pattern.

[0120] The method for implementing the above scheme is as follows: Multiple bandwidth portions can be configured for the UE, and each bandwidth portion can be configured by a set of consecutive PRBs, the size of the RBG to be used, and the size of the time-domain resource allocation. The bandwidth portion index used in the DCI can be notified, and the RBG size, the time information used in each bandwidth portion when indicating each bandwidth portion, etc., can be used for resource allocation.

[0121] In other words, the selection of bandwidth portions can represent the selection of scheduling units for time and / or frequency resources when allocating resources. Bandwidth portions that can be used together within the configured bandwidth portions (i.e., bandwidth portions that can be dynamically changed to a DCI size) can be configured as bandwidth portion groups for the UE, and it can be assumed that the bit size of the resource allocation field in each bandwidth portion group is determined based on the size of the maximum resource allocation field in each bandwidth portion group.

[0122] This configuration can be combined with dynamically changing bandwidth portions. It can be assumed that the bandwidth portion group shares a CORESET. In this case, when the CORESET changes, the size of the DCI to be scheduled can be changed, and therefore, the possibility of resource allocation fields dynamically changing when sharing a CORESET should be considered.

[0123] Alternatively, in such a configuration, it can be expected that the UE's baseband bandwidth will be mismatched when the bandwidth portion groups share the CORESET. It can be assumed that the UE's baseband is not changed to match the maximum value of the bandwidth portion group within that group.

[0124] Alternatively, in such a configuration, higher-layer signaling allows for the assumption of frequency band changes or retuning delays between control signals and data, depending on whether the UE can assume such changes. If no delay is configured to assume bandwidth changes, it can be assumed that the bandwidth remains unchanged and is adjusted to its maximum value.

[0125] Alternatively, a bandwidth portion can be configured, and a set of time / frequency schemes for DCI resource allocation can be configured, which can be indicated in the CORESET of the corresponding bandwidth portion. For example, when the bandwidth portion consists of 200 resource blocks, the set of time / frequency schemes can consist of frequency band, RBG size, time-domain resource allocation information, etc.

[0126] For example, the time / frequency scheme set can be defined as: Entry 1 = (200 RB (bandwidth), 10 RB (RBG size), starting OFDM symbol (4 bits), 4 time slots (2 bits)) Entry 2 = (16 RB (bandwidth) starting from the 100th RB, 1 RB (RBG size), 0 for time domain resource allocation) etc.

[0127] 4) When there are multiple candidate values ​​for RBG size, the following methods can be used to indicate different RBG sizes or time-frequency resource allocation schemes.

[0128] i) Explicit bits can be used in the DCI. ii) The DCI can be interpreted differently depending on the CCE index to which it is mapped. This mapping can be configured by higher-level signaling or can be a value that is always set. iii) Alternatively, scrambling with either the DCI or CRC can be used.

[0129] 5) When multiple time / frequency resources exist, the UE can be controlled to simultaneously monitor CORESETs configured in several bandwidth portions, so as to dynamically change several time / frequency resources. The resource allocation method for each CORESET can be different.

[0130] For example, CORESETs can be configured in 200RB and 10RB bandwidth portions respectively, and the required bit size for the resource allocation field for each CORESET can be assumed for scheduling 200RB and 10RB. More generally, bandwidth and resource allocation information for data that can be scheduled for each CORESET can be configured.

[0131] More specifically, regarding the aforementioned scheme, the entire bit field size used for time and frequency resource allocation can be the same. In this case, the frequency domain resource allocation can indicate the resources allocated via a bitmap scheme for a given RBG size, or it can indicate a RIV scheme based on a given RBG size as the basic unit (i.e., a scheme indicating the number of RBs or RBGs consecutive to the starting RB or RBG index).

[0132] In this case, the time-domain resource allocation can be a starting time-domain scheduling unit index, an ending time-domain scheduling unit index, and / or a consecutive number of time-domain scheduling units for PDSCH or PUSCH.

[0133] A time-domain scheduling unit can be a symbol (reference parameter set or DCI parameter set reference), multiple symbols, or a microslot. When the size of a symbol group is set and the scheduling unit is configured based on the size of the symbol group, the size of a particular symbol group can differ from the size of another symbol group, depending on the number of symbols constituting a slot.

[0134] Alternatively, patterns for symbol groups in one or more time slots can be pre-configured according to instructions from the BS, or resource allocation can be performed based on the starting unit and the number of corresponding units.

[0135] For example, the symbol group pattern can vary depending on the control area configuration (e.g., the number of symbols in the time domain). For example, the symbol group pattern in a time slot consisting of seven symbols can be any one of (3,2,2), (1,2,2,2), (2,2,2,1), (2,2,3), and (2,3,2).

[0136] Information about the start / end / interval can exist in the form of a pattern, and the resource allocation bit field can be used to indicate the corresponding pattern. More specifically, information about the pattern can be indicated by the BS (via higher-level signaling or the third PDCCH).

[0137] As an example of a pattern, a RIV scheme (a scheme that indicates the starting symbol index and the number of consecutive symbols) can be used. If the bit field size of the time-domain resource allocation changes according to the RBG size, resource allocation can be performed with some bits of the RIV scheme fixed to specific values ​​(e.g., 0 or 1), or basic units can be added in the RIV scheme (e.g., based on multiple symbols in a symbol period).

[0138] Fixed field size used for time and / or frequency resource allocation>

[0139] When allocating resources, if the bit size of the resource allocation field is the same, while the RBG size is changed, the combination of resources that can be allocated can become different.

[0140] The RBG size can be changed by at least one of the following: 1) directly indicated in the DCI, 2) changed according to changes in the bandwidth portion, or 3) changed according to the bit size of the resource allocation field.

[0141] Specifically, the bit field used for frequency resource allocation can be configured based on a specific RBG size. For example, the size of the bit field can be determined based on the maximum RBG size that can be set.

[0142] In future wireless communication systems, the BS can indicate the bit size of the resource allocation field. For a specific RBG size or a larger RBG size, resource allocation can be flexibly performed for all RBGs in the system bandwidth, terminal bandwidth, or configured bandwidth portion.

[0143] If the indicated RBG size is small, resource allocation can be performed only on some RBG sets. More specifically, for example, when configuring frequency domain resource allocation via a bitmap for RBGs, all RBGs or combinations of RBGs within the bandwidth allocated to the corresponding UE can be expressed for a specific RBG size (group). Meanwhile, if the RBG size is very small, resource allocation can be performed only on some RBG sets within the bandwidth allocated to the corresponding UE.

[0144] In a more specific example, suppose the number of RBGs within the terminal bandwidth of the first RBG size is N, and the number of RBGs within the terminal bandwidth of the second RBG size is M. Here, if the first RBG size is larger than the second RBG size, then M is greater than N (M>N). However, if the resource allocation field is set based on the first RBG size, then only N or a subset of M RBGs out of the M RBGs can be allocated using the resource allocation field for the second RBG size.

[0145] At the point where resource allocation is performed, the RBG size can be set to large to allocate more frequency resources, and conversely, the RBG size can be set to small to allocate smaller frequency resources.

[0146] Alternatively, in cases where the bandwidth portion (BWP) is flexibly changed, and when the bit size of the scheduled BWP and the scheduled BWP are different, in this disclosure, resource allocation can be performed on the scheduled BWP, which has the bit size of the resource allocation field of the scheduled BWP.

[0147] When the RBG size is small, the amount of resources that can be allocated using the bit size of the finite resource allocation field is limited. In this case, the BS can indicate to the UE the information for selecting the RBG set in order to reduce restrictions on resource allocation.

[0148] Specifically, the resource allocation field in the frequency domain may include an RBG size indicator, an RBG set indicator in the bandwidth, and / or an RBG indicator in the RBG set.

[0149] For example, candidates for the RBG set can be individually indicated to the UE by the BS (e.g., via signaling notification through higher-layer signaling and / or via group common PDCCH and / or third DCI indication). Specific candidates within the RBG set can be indicated by scheduling the DCI of the corresponding PDSCH or PUSCH.

[0150] Depending on the base station configuration, RBGs in the RBG set can be configured as centralized (i.e., adjacent to each other) or distributed (i.e., separate from each other).

[0151] In a simple example, the BS can configure candidates for the RBG set via signaling notifications such as higher-level signaling such as RRC messages and / or PDCCH and / or third DCI, and the corresponding scheme can be in the form of a bitmap for RBGs within the terminal bandwidth or system bandwidth.

[0152] Therefore, a BS can map multiple consecutive RBGs to the same RBG set for centralized resource allocation, or it can map multiple non-consecutive RBGs to the same RBG set for distributed resource allocation.

[0153] Alternatively, the RBG to be indicated may include the number of RBGs that can be represented by the bit size of the resource allocation field of the BWP scheduled from the lowest RBG of the scheduled BWP.

[0154] If the number of PRBs constituting an RBG based on the bandwidth portion (BWP) is relatively small and / or the number of PRBs that can actually be used for data mapping in the RBG is relatively reduced due to reserved resources, etc., the corresponding RBG can be excluded from the RBG set as the target. The relatively reduced RBG size can refer to the case where the RBG size becomes smaller than the set RBG size based on the size of the bandwidth portion (BWP).

[0155] Regardless of the resource allocation type, the above description can be applied. Alternatively, the resource allocation type in the bitmap scheme can follow the scenario where the bit size of the required resource allocation field differs from the actual bit size of the resource allocation field, as described above. In the RIV scheme's resource allocation type, the bit size of the resource allocation field can be configured based on either the maximum bandwidth portion or the maximum bandwidth portion within the configured bandwidth portion. This is because, in the case of the RIV scheme, the difference in bit size of the resource allocation field may be small depending on the bandwidth portion size.

[0156] Alternatively, multiple RBG sizes can be used to indicate resources in a resource allocation. In a specific example, when a bandwidth portion consists of multiple RBGs, the size of a particular RBG can be set to follow the set RBG size (including + / -1 difference), and the size of other particular RBGs can be set to include all remaining PRBs in the bandwidth portion.

[0157] For example, suppose the bandwidth portion consists of 50 PRBs, the resource allocation field has a bit size of 5 bits, and the RBG size is 5 PRBs. In this case, for example, the RBG configuration for the bandwidth portion could consist of four RBGs with a size of 5 PRBs and one RBG with a size of 30 PRBs. In the above scheme, there may be a problem where the size of a particular RBG is too large.

[0158] Alternatively, when the bit size of the resource allocation field and the size of the bandwidth portion are set or given, the difference between the configured RBGs can be considered as 1 (PRB) or less when setting the RBG size and the number of RBGs. Specifically, when the bandwidth portion consists of N PRBs and the bit size of the resource allocation field is set to M bits, among the RBGs constituting the bandwidth portion, RBGs with a size of Ceil(N / M) can be M*Ceil(N / M)-N, and RBGs with a size of Floor(N / M) can be M-(M*Ceil(N / M)-N). Regarding the order of arranging RBGs of different sizes, RBGs with the same RBG size are arranged first, and then RBGs with different RBG sizes can be arranged.

[0159] To match the RBG size to the maximum value in different ways, most RBGs (excluding specific RBGs within all RBGs) can be configured to have a size of Ceil (N / M) or Floor (N / M), and the size of the remaining (one) RBG can be configured to include the other remaining PRBs (e.g., configured to have a size of N-(M-1)*Ceil (N / M) or N-(M-1)*Floor (N / M). For example, suppose the bandwidth portion consists of 50 PRBs (N=50) and the bit size of the resource allocation field is 13 bits (M=13). In this case, the RBG configuration for the bandwidth portion consists of 12 RBGs of size 4 PRBs (=ceil(50 / 13)) and one RBG of size 2 PRBs (=50-12*4).

[0160] The example above described a method for resource allocation (interpretation) based on the RBG size in the frequency domain; however, it can be extended to a method for allocating (interpreting) resources in the time domain based on scheduling (time) units. Similarly, time-domain resource allocation can be configured for specific scheduling units, and resource allocation can be performed based on flexibly changing scheduling unit values. More typically, RBG set indicators can be represented in units of time and / or frequency resource scheduling units.

[0161] For example, an RBG set indicator may include information about the RBGs that make up the RBG set and information about the starting symbol index and / or duration, etc. Alternatively, a basic time and frequency resource unit may be selected for each RBG in the time-domain scheduling unit. Or, the resource allocation (or scheduling unit) may not change flexibly with respect to the time axis.

[0162] In another approach, frequency-domain resource allocation is performed on a specific RBG set, and the allocation information for that specific RBG set can be applied equally to multiple RBG sets within the bandwidth. For example, when all RBGs are configured as multiple RBG sets, the bitmap information of a specific RBG set can be considered to be applied in the same way to each of the other RBG sets.

[0163] In this embodiment, the bandwidth can be the system bandwidth (system BW) or the UE bandwidth, and can be replaced by bandwidth portions. If multiple bandwidth portions are configured for a specific UE, bandwidth portion indicator information can be sent. The RBG set can be limited to the corresponding bandwidth portion, or the RBG set itself can include RBGs of multiple bandwidth portions.

[0164] In another approach, for example, two resource allocation types can be configured dynamically. The frequency domain will be described below, but it can also be applied to resource allocation in the time domain and time / frequency domain resources.

[0165] 1) Resource allocation type 0: Bitmap, whose bit size is RBG size K+floor(M / K), where M is the number of PRBs of bandwidth configured in the bandwidth section.

[0166] 2) Resource allocation type 1: Bitmap, its bit size is RBG size + p*K + floor(M / p*K)

[0167] Figure 9 The illustration shows an example of resource allocation type 1.

[0168] refer to Figure 9 In resource allocation type 1, RB-level resources can be allocated by increasing the RBG size, providing a bitmap (RBG indicator) specifying which RBG to select, and providing another bitmap (RB indicator within the RBG) of the same RBG size. The bitmap of the RBG size is typically appropriate for the selected RBG.

[0169] The above methods can be used in combination. For example, in order not to significantly increase the bit size in the frequency domain, the set of allocable RBs can be different depending on the RBG size, and the resource allocation scheme in the time domain can be changed.

[0170] In future wireless communication systems, when performing time-domain resource allocation, the DCI can indicate to the UE the start symbol index and / or the last symbol index for PDSCH or PUSCH.

[0171] More specifically, the start symbol index and / or the last symbol index may be indicated separately by symbol units or symbol groups constituting a time slot, or the start symbol index and the last symbol index may be combined for joint indication. For example, the start symbol index and / or the last symbol index may be combined to indicate according to a RIV scheme. The RIV scheme may be a scheme indicating the start symbol index and duration.

[0172] Furthermore, in future wireless communication systems, the BS can configure one or more sets of multiple time-domain resources via RRC signaling, and each set can include a combination of time slot index information mapped to PDSCH / PUSCH, and / or start symbol index, and / or last symbol index. Time-domain resource allocation can be performed via scheduling DCI instructions from one of the configured sets.

[0173] The set configured by RRC can be set separately from the Slot Format Information (SFI) sent via the group common PDCCH. The SFI indicates the downlink portion, gap, and / or uplink portion of a slot. Here, because it is assumed that the downlink portion in the SFI typically starts using the first symbol of the slot, and the scheme of not mapping some earlier symbols in the case of time-domain resource allocation to avoid overlap with the CORESET (control area) when scheduling PDSCH or PUSCH is not excluded, the purpose and scheme are considered different.

[0174] When performing time-domain resource allocation based on RRC signaling, it is necessary to determine the time-domain resource allocation method before RRC configuration is established and / or during the RRC reconfiguration period. The following is a more specific example.

[0175] 1) A set of parameters (e.g., a combination of at least one of time slot index information, start symbol index, and last symbol index) for time-domain resources can be configured via the Physical Broadcast Channel (PBCH) and / or Residual Minimum System Information (RMSI) and / or other System Information (OSI). In future wireless communication systems, when transmitting the minimum system information, a portion of the minimum system information can be transmitted via the PBCH, and the remainder, i.e., the RMSI, can be transmitted via the PDSCH. More typically, in the time-domain resource allocation of the above scheme, the scheduling DCI can belong to a common search space or a group of common search spaces. The common search space can be a search space used for RMSI and / or OSI transmission.

[0176] 2) Dynamic time-domain resource allocation may not be performed. In this case, the slot index can be a fixed value, and different values ​​can be set for PDSCH and PUSCH. For example, PDSCH can be sent in the same slot as PDCCH, and PUSCH can be sent four slots after PDCCH. In the case of the start symbol index, it can be specified by the symbol following the CORESET interval. More typically, for PUSCH, the start symbol index can be set via higher-layer signaling (PBCH and / or RMSI and / or OSI) and / or DCI indication, or it can be configured to start from the first symbol of the configured slot. In the case of the last symbol index, it can be configured via higher-layer signaling (PBCH and / or RMSI and / or OSI) and / or DCI indication, or it can be configured by the last symbol of the slot. More specifically, in the time-domain resource allocation of the above scheme, the scheduling DCI can belong to a common search space or a group common search space. The common search space can be a search space used for RMSI and / or OSI transmissions.

[0177] In future wireless communication systems, PDSCH or PUSCH can be scheduled across multiple time slots through multi-slot aggregation. In this case, it may be necessary to extend the time-domain resource allocation to indicate the aggregated time slots. The following is a more specific example of a time-domain resource allocation method in the case of multi-slot aggregation.

[0178] 1) Configure a set of time-domain resources on multiple time slots via RRC signaling. Each of the above sets may include a mapping of PDSCH or PUSCH, a starting time slot index and / or a last time slot index, and / or a number of time slots to be aggregated and / or a starting symbol and / or a last symbol index for each aggregated time slot, etc. RRC configuration can be configured when multi-time-slot aggregation operations are configured, and can be configured independently of the RRC configuration for time-domain resource allocation for a single time slot, or can be configured as a superset including it.

[0179] 2) A set of time-domain resources for a time slot can be used for aggregation time slots. The starting symbol index in the set characterized (finally indicated by DCI) can be applied together to each aggregation time slot. In the case of CORESET intervals, this may be considered a suitable method because it may not be considered to be changed in aggregation time slots. The last symbol index of the next indicating set can be applied to a specific aggregation time slot. Typically, a specific time slot can be the last or first time slot of an aggregation time slot. The last time slot index of the remaining aggregation time slots can be configured by at least one of (1) RRC signaling, (2) RRC signaling and DCI indication (which may be in the form of SFI or SFI pattern), (3) SFI for the corresponding time slot (received from the group common PDCCH), and (4) SFI pattern for the corresponding time slot (received from the group common PDCCH).

[0180] <Compact Frequency Resource Allocation>

[0181] Future wireless communication systems can support applications requiring high reliability. In such cases, the amount of DCI transmitted on the PDCCH can be reduced. More typically, it is necessary to effectively reduce the size of specific fields within the DCI content (especially the resource allocation field).

[0182] Resource allocation can be expressed using the RIV scheme (i.e., a scheme expressed by the number of RBs consecutive to the starting RB index or the number of RB sets consecutive to the starting RB set for a given RB set). This scheme reduces the bit size required for resource allocation by only expressing consecutive resource allocations.

[0183] To effectively manage the multiplexing between different PDSCHs or PUSCHs from a network perspective, it is necessary to configure the scheduling granularity to RBG size. In a specific example, in an LTE system, information about the step size or the RBG size during compact resource allocation can be configured to have a specific RBG size (e.g., an RBG size configured to interact with bandwidth) or can be indicated to the UE by the BS (via at least one of higher-layer signaling, group common PDCCH, or third DCI). Depending on the size of the system bandwidth, terminal bandwidth, or bandwidth portion, a specific RBG can be larger or smaller than the configured RBG size. A specific RBG can also be processed / indicated by resources allocated in the same manner as other RBGs. That is, when allocating resources, RBGs allocated regardless of RBG size can be indicated, and PRBs can be allocated to the indicated RBGs based on the size of each RBG. In cases where RBG sizes can be flexibly changed, the total bit size can be set based on a specific RBG size (e.g., the maximum or minimum value among candidate values ​​or the value indicated by the BS) to maintain the total bit size used for compact resource allocation.

[0184] The scheduling unit in the RIV scheme can be modified based on the RBG size indicated in the above case. Therefore, if the indicated RBG size is larger than a specific RBG size referenced in the size setting, a specific value (e.g., 0) can be padded into the MSB or LSB to fit the total bit field size in the bit field used for RIV. Conversely, if the value is small, a configuration can be assumed where a single bit or multiple bits of the MSB or LSB are cut from the bit field used for RIV and the cut bits are padded with a specific value (e.g., 0).

[0185] Distributed resource allocation and / or frequency hopping may be required to guarantee frequency diversity, which can be easily performed by applying interleaving after compact resource allocation. In the case of interleaving schemes, a scheme (or block interleaver scheme) that inputs data row-by-row or column-by-column in a matrix of a specific size and extracts it column-by-column (or row-by-column) can be used. Alternatively, interleaving can be performed based on a pseudo-random function. In the above cases, the location of frequency resources can be shifted based on random numbers. More typically, interleaving can be performed within the size of the effective bandwidth portion of the scheduling PDSCH or PUSCH, or it can be performed in a separate specific frequency domain (e.g., an area indicated by the BS (via higher-level signaling and / or DCI)).

[0186] In the above situation, the same transition pattern and the multiplexing of the transmission channel can be ensured by matching the transition regions equally between terminals with different bandwidth portions.

[0187] However, in the above scheme, the throughput may be reduced when the difference between the bandwidth portion and the transition region of a particular UE is significant, and it is also possible to consider configuring the transition region orthogonally in a different way.

[0188] More specifically, the transition regions can be configured to be non-contiguous, thereby preventing overlap of transition resources between different bandwidth sections.

[0189] In another approach, the size of the blocks interleaver's rows can be configured during the block interleaving process, regardless of the size of the partial bandwidth (e.g., when using third-layer signaling). More specifically, this can be configured via PBCH or RMSI and can be updated by RRC.

[0190] In the above scenario, the row size of the block interleaver can be configured to be the same across different partial bandwidths. More specifically, the UE's bandwidth can be divided into X partial regions, and the number of partial regions can be defined as the number of rows in the block interleaver matrix. In this case, the values ​​of specific regions of the matrix can be filled with NULL, and NULL portions can be skipped when the index is extracted column-by-column. That is, skipping regions can be performed by bypassing specific regions using the method described above. More specifically, specifying NULL can be done by selecting a specific row (and / or offset of an element) in the block interleaver matrix, or by indicating the start and end elements. This information can be indicated by the base station (e.g., higher-layer signaling).

[0191] Figure 10 The diagram illustrates an example of a transition area configuration.

[0192] A pseudo-random scheme can be implemented based on cell identifier (ID), band-specific information, or third signaling (e.g., virtual ID). This scheme can effectively support multiplexing between UEs in a cell or a portion of a band, while also supporting randomization between cells or portions of a band. When considering multiplexing between different PDSCHs or PUSCHs (specifically, performing RBG-based resource allocation), allocating resources in RBG cells even after interleaving may still be useful. That is, interleaving cells can typically be RBG cells. The RBG can be the same as or different from the RBG size at the time of resource allocation indication. In other words, the BS can separately indicate to the UE the RBG size assumed at resource allocation and the RBG size assumed at interleaving (e.g., via higher-layer signaling, group common PDCCH, or third DCI).

[0193] Furthermore, the frequency hopping domain / resources can be different based on inter-slot transitions and / or by the time slot or symbol group based on inter-slot transitions. When performing resource allocation in the above scheme, transitions can be performed based on the time slot or symbol index starting at the PRB position of the PDSCH or PUSCH, or resource allocation can be performed based on the PRB index of the transition calculated at a specific time point (e.g., the start subframe, the start frame, etc.) for multiplexing between several UEs in a cell.

[0194] More specifically, considering multiplexing among multiple terminals, the hopping interval in the time domain can be configured in a fixed form (e.g., based on the midpoint of a time slot or the interval between the seventh and eighth symbols). More typically, considering the different multiplexing between PDSCH or PUSCH in terms of the number of configured symbols, the hopping interval in the time domain can be configured via higher-layer signaling (e.g., at least one of PBCH, RMSI, and RRC) and / or in DCI. In the case of performing non-time-slot-based scheduling, intra-slot frequency hopping can be applied, and hopping may not be performed in non-time-slot intervals.

[0195] Alternatively, resource allocation can be performed based on a specific offset within a predetermined transition area (e.g., a portion of the effective uplink bandwidth) or within a transition area signaled by a higher layer (e.g., PBCH, RMSI, or RRC).

[0196] For example, a PUSCH or PDSCH transmitted in PRB N during the first hop interval can be transmitted in the second hop interval in the portion of the bandwidth of the uplink bandwidth modulo {(PRB N + offset) modulo uplink bandwidth}. More typically, considering multiplexing among multiple terminals, the hop interval in the time domain can be configured in a fixed form (e.g., based on the midpoint in the time slot or the interval division between the seventh and eighth symbols), and more typically, considering the different multiplexing between PDSCH or PUSCH in terms of the number of configured symbols, the hop interval in the time domain can be configured via higher-layer signaling (e.g., PBCH, RMSI, and RRC) and / or in the DCI.

[0197] Offset can be a value signaled / configured by higher-layer signaling in a cell-specific manner, an offset value set for each bandwidth portion, or a value configured by setting hopping regions via parameters (e.g., by multiples of 1 / N, 2 / N, ... (N-1) / N of the hopping regions).

[0198] And / or, multiple offsets can be configured semi-statically, and the final applied value can be indicated in the DCI.

[0199] Several subband sizes / offsets and hopping patterns can be configured in frequency hopping. The corresponding configurations can be set to differ based on the configured bandwidth portion (BWP). Typically, the subband size and offset can be configured for each hopping pattern, and the corresponding values ​​can be set differently for each bandwidth portion.

[0200] Because the effective value of the transition pattern can vary depending on the frequency diversity gain and the multiplexing between terminals, the transition pattern to be used can be set differently for each bandwidth portion, or one of several transition patterns can be dynamically set. An example of such a transition pattern is as follows.

[0201] 1) Type 1: The index of RB or RBG can be incremented by a cell-specific offset value. This allows terminals to use the same hopping pattern, even though the terminals have different bandwidth portions, thus minimizing conflicts due to hopping between terminals. Alternatively, it can be thought of that the offset setting is performed for each bandwidth portion, and the network sets the same value for multiple bandwidth portions.

[0202] 2) Type 2: Similar to LTE PUCCH Type 1, the hopping bandwidth configured for the terminal can be divided in half, and the RB or RBG index can be incremented accordingly. Because terminals with different bandwidth portions perform hopping with different offsets, collisions may increase, but diversity gain can be achieved. When using the appropriate scheme, it is possible to use an offset with a specific value instead of dividing the hopping band in half.

[0203] 3) Type 3: Similar to LTE PUCCH Type 2, the hopping is applied to a hopping bandwidth greater than its own bandwidth. If the hopping is applied to an RB or RBG index greater than its own bandwidth, the absolute frequency position of the uplink bandwidth portion can be moved according to the hopping. Alternatively, multi-level hopping can be performed when applying the hopping. For example, an uplink bandwidth portion can be divided into several subbands, Type 1 or Type 2 can be performed within each subband, and Type 1 or Type 2 can be performed again for each subband.

[0204] The hopping in the initial uplink bandwidth portion of message 3 can also follow the above method, and the hopping scheme can be sent in the Random Access Response (RAR). When sending message 3, considering the small initial uplink bandwidth portion and applying at least inter-slot hopping, the absolute frequency position of the uplink bandwidth portion can be considered to have changed. In other words, frequency hopping can be performed within the frequency hopping bandwidth configured based on the public PRB index, and the corresponding frequency hopping bandwidth can be configured through RSMI, etc. The physical position of the initial uplink bandwidth portion can be changed by the corresponding hopping. This can be applied only to inter-slot hopping, or only to the initial transmission or retransmission of message 3.

[0205] More generally, inter-slot hopping can be performed within the cell common or group common frequency hopping bandwidth based on the common PRB index, and intra-slot hopping can be performed within the active bandwidth portion of the terminal.

[0206] The advantage of the above scheme is that when supporting a small RBG size (e.g., 1 RB granularity), it executes 1 RB granularity to allocate resources in the RIV scheme, and thereafter, only interleaving can be performed at the RBG size granularity. The advantage of the above scheme is that although the resource allocation performed is smaller than the RBG size, it can distribute the simultaneously allocated RBs while considering reuse with other PDSCHs or PUSCHs (i.e., maintaining the RBG mesh).

[0207] In the case of compact resource allocation, reducing the possible combinations of allocated resources can be considered to further reduce the corresponding bit field size. For example, the relationships between possible combinations of allocated resources may have a nested structure. For instance, the initial RB may be constrained.

[0208] <Resource allocation scheme based on waveform>

[0209] In future wireless communication systems, different waveforms such as CP-OFDM and DFT-S-OFDM can be supported. And / or, in some cases, when performing resource allocation, only continuous resource allocation may be allowed, or discontinuous resource allocation and / or continuous resource allocation may be allowed.

[0210] For example, in the case of uplink transmission, by supporting CP-OFDM and DFT-S-OFDM, the resource allocation type or method can be configured differently based on the waveform. The waveform selection can follow the configuration of higher-layer signaling. In this case, the DCI size and / or resource allocation field size can be set to be different from each other for different waveforms. However, if the waveform is flexibly changed, it is necessary to match the DCI size and / or resource allocation field size equally.

[0211] Alternatively, the resource allocation field can be configured to be the same regardless of the waveform.

[0212] If a scheme can support non-continuous resource allocation, continuous resource allocation can be displayed based on the settings.

[0213] Additionally, the above scheme can be extended to balance the size and / or resource allocation fields between the DCI used for PDSCH scheduling and the DCI used for PUSCH scheduling.

[0214] For types that only support contiguous resource allocation and types that can support both contiguous and non - contiguous resource allocation, the size of the resource allocation field and / or the DCI size can be different. In this case, the DCI for scheduling the PDSCH that is independent of the transmission mode (TM) and the DCI for scheduling the PUSCH that only supports contiguous resource allocation or has a DFT - S - OFDM waveform can be configured to have the same size, and the DCI for scheduling the PDSCH related to TM and the DCI for scheduling the PUSCH that supports even non - contiguous resource allocation or has a CP - OFDM waveform can be configured to have the same size.

[0215] Additionally, if the terminal can detect the DCI that can schedule multiple types of PUSCH, the waveform can be changed according to the detected DCI or the resource allocation type included therein. For example, if the resource allocation in the DCI only allows contiguous resource allocation, the waveform of the corresponding PUSCH can be DFT - S - OFDM, otherwise it is CP - OFDM.

[0216] <Alignment between RBG and PRG>

[0217] For the RBG, when allocating frequency resources, a bitmap can be used as the basic unit. The PRG is the precoder granularity, and it can be assumed that the same precoder is applied to the PRBs within the same PRG. Moreover, the PRG can be used as the basic unit for channel estimation based on it.

[0218] In NR, considering multi - user MIMO (MU - MIMO) between terminals configured with different bandwidth parts, the PRG can be configured based on common resource blocks regardless of the bandwidth part. In future wireless communication systems, considering terminal implementation complexity, when the RBG size = 2RB, it is not expected that the PRG size is 4RB. The reason is that if the actual PRG size is changed according to resource allocation, the complexity increases when performing channel estimation. Additionally, according to scheduling, due to limited interpolation, the channel estimation performance between the scheduled RBs is different, reducing the demodulation performance.

[0219] If the boundary between the RBG and the PRG is not aligned, the situation where a single PRG overlaps with multiple RBGs as described above may occur. Similar to the above - mentioned situation, due to limited interpolation according to scheduling, the channel estimation performance may be reduced.

[0220] Therefore, RBGs and PRGs can be defined / configured based on common resource blocks (CRBs or system frequency bands). For example, the RBs that make up an RBG can be configured in ascending order of frequency from CRB#0. In this case, the first RBG in the bandwidth portion can be set to {(indicated RBG size - bandwidth portion start) mod indicated RBG size}. The indicated RBG size can be a value set according to the bandwidth portion size and / or by a table configured by a higher layer and / or the indicated bandwidth portion and / or the bandwidth portion for transmitting DCI. The last RBG can be {(bandwidth portion start + bandwidth portion size) mod (indicated RBG size or indicated RBG size)}. The result of the above equation can be 0. The remaining RBGs can be the indicated RBG size.

[0221] Alternatively, the starting CRB index for the bandwidth portion can be restricted. More specifically, the starting CRB index for the bandwidth portion can be configured as a multiple of a specific PRG size (e.g., 2 or 4). That is, it can be expected that the starting CRB index for the bandwidth portion is configured such that the RBG and PRG are aligned on the boundary side.

[0222] The number of RBGs can be determined based on the starting RB of the bandwidth segment, the bandwidth segment size, and the indicated RBG size. If the starting RB of the bandwidth segment can be divided according to the indicated RBG size, the number of RBGs in the bandwidth segment can be set to the rounded-up value of {bandwidth segment size / indicated RBG}. If the starting RB of the bandwidth segment cannot be divided according to the RBG size, the number of RBGs can be the rounded-up value of {bandwidth segment size / indicated RBG} + 1.

[0223] In another example, the number of RBGs (N) in the bandwidth portion RBG The reference bandwidth portion can be represented by Ceiling((bandwidth portion size / indicated RBG size) + Ceiling(bandwidth portion start index mod indicated RBG size / indicated RBG size)) and can also be Ceiling((bandwidth portion size + bandwidth portion start index mod indicated RBG size) / indicated RBG size). The bit field size for frequency domain resource allocation type 0 can be determined based on the number of RBGs. In this case, the reference bandwidth portion can be the largest of the configured bandwidth portion, the bandwidth portion for transmitting DCI, or the bandwidth portion for transmitting scheduled PDSCH or PUSCH.

[0224] Figure 11 The diagram illustrates terminal operations related to downlink resource allocation.

[0225] refer to Figure 11The terminal receives resource block allocation (assignment) information including a bitmap (S101), and in the bandwidth portion (BWP), it can receive downlink signals, such as PDSCH (or send PUSCH) through the resource block group indicated by the bitmap (S102).

[0226] In this case, the total number of resource block groups in the bandwidth section can be determined based on the index of the starting resource block of the bandwidth section, the size of the bandwidth section, and the size of a resource block group.

[0227] For example, when the bandwidth component is the i-th bandwidth component (i is 0 or a natural number) and includes N... size BWP,i When there are 1 PRBs, the total number of resource block groups can be determined by the following equation.

[0228] [Equation 1]

[0229]

[0230] In the equation above, N start BWP,i It can be the index of the starting resource block of the i-th bandwidth segment, N size BWP,i P can be the size of the i-th bandwidth segment, and P can be the size of a configured resource block group. P can be selected / determined based on the size of the bandwidth segment from among the candidate values ​​previously set via Radio Resource Control (RRC) messages. Candidate values ​​can be provided in tabular form via RRC messages.

[0231] Furthermore, the number of bits in the bitmap can be equal to the total number of resource block groups (N). RBG Each bit of the bitmap corresponds to each resource block group in the bandwidth portion in a one-to-one manner to indicate whether each resource block group is allocated.

[0232] More specifically, it will be described below. Figure 11 Each step. In downlink resource allocation type 0 in NR, resource block allocation (assignment) information includes a bitmap indicating the RBGs allocated to the UE. An RBG, as a set of contiguous (virtual) resource blocks, can be defined by the size of the bandwidth portion and parameters configured by higher-layer signaling.

[0233] The table below illustrates the RBG size P based on the bandwidth portion.

[0234] [Table 6]

[0235] Bandwidth portion size Configuration 1 Configuration 2 1–36 2 4 37–72 4 8 73–144 8 16 145–275 16 16

[0236] Figure 12 The diagram confirms that N is included. size BWP,iThe number of RBGs (N) of the downlink carrier bandwidth portion i of each PRB RBG Examples of ).

[0237] As described above, in this disclosure, the number of RBGs (N) RBG ) can be determined as Ceiling((N size BWP,i +(N start BWP,i mod P)) / P).

[0238] More specifically, N start BWP,i The starting position of the i-th BWP (e.g., the starting resource block index) can be indicated based on a reference point (e.g., CRB 0), and N size BWP,i It can indicate the size of the i-th BWP in the frequency domain (i.e., the number of resource blocks constituting the i-th BWP, in other words, the size of the i-th BWP). And P is the size of the indicated RBG. It can be based on the number of RBGs (N). RBG The size of the bitmap for resource allocation type 0 (frequency domain) is determined by this. All remaining RBGs except the first and last RBGs can have the same size P, while the first and last RBGs can have sizes other than P, depending on N. size BWP,i The value of . For example, the size of the first RBG can be PN. start BWP,I mod P, and if (N) start BWP,i +N size BWP,i If mod P is greater than 0, then the final size of RBG can be (N) start BWP,i +N size BWP,i )mod P.

[0239] Meanwhile, in resource allocation type 1, when the interleaved VRB is mapped to the PRB, interleaving can be performed on a per-RB bundle basis, and the corresponding RB bundles need to be set / defined similarly based on the CRB. RB bundles can be defined as contiguous resource blocks. That is, after interleaving, the boundaries of the RB bundles can be aligned with the PRG, thereby reducing the complexity of channel estimation and enhancing performance.

[0240] Figure 13 The illustration shows an example of aligning the boundary between the RB bundle and the CRB used for interleaving in resource allocation type 1.

[0241] refer to Figure 13The boundary between the RB bundles and CRBs used for interleaving is configured / defined as aligned. CRBs can be the same as PRBs. After interleaving, the boundary of the RB bundle can be aligned with the PRG, which is a set of PRBs.

[0242] The UE may assume that the same precoding is used in the frequency domain within an RRB bundle. The UE does not assume that the same precoding is used in bundles of different CRBs.

[0243] At the same time, since information about the Common Resource Block (CRB) grid is provided by RMSI, it is necessary to define whether or how to perform interleaved VRB to PRB mapping in the common search space of CORSET 0 on the PDSCH (hereinafter referred to as RMS-PDSCH) that includes RMSI and is scheduled via DCI format 1_0.

[0244] Specifically, in a public resource block grid, N can be defined. start BWP,i and N size BWP,i The UE may not be aware of the above values ​​until it receives the RMSI. For simplicity, RMSI-PDSCH could be designed to support only non-interleaved VRB-PRB mapping. In this case, RMSI reception performance may be degraded due to insufficient frequency diversity.

[0245] Alternatively, resource block bundles for RMSI-PDSCH can be defined in the initial downlink bandwidth portion of the grid. Specifically, resource block bundles begin with the first resource block index of the initial downlink bandwidth portion, and all resource block bundles can consist of, for example, two consecutive resource blocks.

[0246] Proposal 1: Interleaved VRB-to-PRB mapping can be used for PDSCH including RMSI in the initial downlink bandwidth portion. Resource block bundling can be defined in the initial downlink bandwidth portion without considering the common resource block grid.

[0247] After receiving the RMSI, the common resource block grid is notified to the UE. Then, all technologies based on the common resource block grid become available for use. In this case, if a PDSCH including the RMSI is received in a downlink bandwidth portion other than the initial downlink bandwidth portion, the resource block bundle used for VRB-to-PRB mapping during interleaving can be defined as aligned with the common resource block grid.

[0248] The UE can receive another PDSCH (i.e., a PDSCH excluding RMSI) in the initial downlink bandwidth portion. In this case, when considering multiplexing of multiple terminals, it is preferable to make the definition of resource block bundles the same, regardless of the RNTI applied to the PDSCH. In other words, regardless of the RNTI, without considering the common resource block grid, it can be assumed that all PDSCH mappings in the initial downlink bandwidth portion are defined in the initial downlink bandwidth portion.

[0249] Furthermore, in the initial downlink bandwidth portion, the RBG can be defined without considering the common resource block grid.

[0250] Proposal 2: For PDSCH including OSI, paging, random access response (RAR) in the initial downlink bandwidth section, resource block bundling can be defined in the initial downlink bandwidth section without considering the common resource block grid.

[0251] In other words, when mapping interleaved VRBs to PRBs, the boundaries of interleaving bundles can be defined / configured based on the (initial) bandwidth portion instead of the CRB in the following exceptional cases: These exceptions include cases where the DCI schedules the RMSI, the DCI belongs to CORESET#0 associated with the Common Search Space (CSS) while the DCI is scheduling the RMSI, the DCI belongs to the CSS, the DCI belongs to the CSS of the initial downlink bandwidth portion, and the DCI belongs to the initial downlink bandwidth portion. More specifically, RBGs in resource allocation for bitmap schemes can also be configured to be aligned at boundaries based on the bandwidth portion instead of the CRB, with exceptions.

[0252] Alternatively, it can be indicated whether the DCI scrambled by SI-RNTI constitutes a resource block bundle for interleaving VRB to PRB mapping.

[0253] Specifically, because the size of the resource block bundle is set to 2 before the RRC configuration, the DCI can indicate whether the size of the first resource block bundle is 1 or 2 based on the starting RB index of the initial downlink bandwidth portion (using one of the reserved bits). In this case, the resource block bundle can also be aligned with the common resource block grid in the RMSI-PDSCH.

[0254] The DCI scrambled to SI-RNTI can indicate (N start BWP,i mod 2), that is, the method for configuring resource block bundles, the size of the first resource block bundle, the offset value between the PRB at the start of the resource block bundle and the common resource block grid in the DCI of the PDSCH scheduling.

[0255] <Misalignment between the RA bandwidth and the actual BWP size)>

[0256] In a future wireless communication system, the number of DCI sizes that a UE has to monitor can be restricted to reduce the complexity of the UE. More specifically, when DCI format 1_0 and DCI format 0_0 are transmitted in a specific search space (e.g., UE-specific search space), the resource allocation bit fields of DCI format 1_0 and DCI format 0_0 (hereinafter referred to as "fallback DCI") can be configured based on the activated bandwidth part in which the corresponding fallback DCI is transmitted (when the number of DCI sizes is sufficient) or based on the initial (downlink) bandwidth part size (when the number of DCI sizes exceeds or is about to exceed a predetermined level).

[0257] According to the above, it can be considered that the frequency ranges that can be indicated by the resource allocation bit fields are configured differently. Basically, when the bit size of the resource allocation field is equal to the size of the resource allocation field required in the bandwidth part to which the DCI belongs (or when the bit size of the resource allocation field is configured to be larger), the lowest resource block (RB) index corresponding to the resource allocation field matches the smallest RB index of the corresponding bandwidth part, and the highest RB index can match the largest RB index of the corresponding bandwidth part. The above regions can be equally applied to the interleaving target regions.

[0258] Meanwhile, when the bit size of the resource allocation field is smaller than the size of the resource allocation field required in the bandwidth part, the lowest RB index corresponding to the resource allocation field matches the smallest RB index of the corresponding bandwidth part, and the highest RB index can match the RB index of the initial (downlink) bandwidth part that is away from the smallest RB index of the corresponding bandwidth part. This is to perform resource allocation more efficiently due to the limitation of the bit size of the resource allocation field. Here, the interleaving target region can also be set based on a region that is set to be smaller than the actual bandwidth part. Alternatively, as a method of taking advantage of a relatively large activated bandwidth part, it can be considered that the interleaving target region is still configured as the activated bandwidth part.

[0259] If the region corresponding to the resource allocation field is still configured as the activated bandwidth part even when the bit size of the resource allocation field is smaller than the size of the resource allocation field required in the bandwidth part, zero-padding can be performed on the LSB or MSB before interpreting the corresponding bit field.

[0260] Figure 14 is a block diagram of a device implementing an embodiment of the present disclosure.

[0261] Reference Figure 14The device 100 includes a processor 110, a memory 120, and a transceiver 130. The processor 110 implements the proposed functions, processes, and / or methods. The memory 120 is connected to the processor 110 and stores various types of information used to drive the processor 110. The transceiver 130 is connected to the processor 110 and transmits and / or receives wireless signals.

[0262] Device 100 may be a base station (BS) or a terminal (or user equipment (UE)).

[0263] Processor 110 may include application-specific integrated circuits (ASICs), other chipsets, logic circuits, data processors, and / or converters that convert baseband signals and wireless signals. Memory 120 may include read-only memory (ROM), random access memory (RAM), flash memory, memory cards, storage media, and / or other storage devices. Transceiver 130 may include at least one antenna for transmitting and / or receiving wireless signals. When implementing embodiments in software, the above-described scheme can be implemented using modules (procedures or functions) that perform the above functions. Modules may be stored in memory 120 and executed by processor 110. Memory 120 may be arranged inside or outside processor 110 and connected to processor using various known means.

Claims

1. A method for transmitting downlink signals in a wireless communication system, the method being performed by a base station and comprising: Send resource block assignment information, including bitmaps; as well as Downlink signals are transmitted via resource block groups (RBGs) indicated by the bitmap within the bandwidth portion. The total number of Resource Block Groups (RBGs) for the bandwidth portion is determined based on the index of the starting resource block of the bandwidth portion, the size of the bandwidth portion, and the size of a configured RBG. Wherein: the bandwidth portion is bandwidth portion i, where i is 0 or a natural number, and N is based on the index of the starting resource block representing the bandwidth portion i. start BWP,i N represents the size of the bandwidth portion i. size BWP,i And P, representing the size of an RBG of the configuration. The total number N of the RBGs used for the bandwidth portion i is determined based on the following equation. RBG , 2. The method according to claim 1, wherein, The number of bits in the bitmap is equal to the total number N of the RBGs. RBG .

3. The method according to claim 1, further comprising: Send a higher-level signal that notifies the size of an RBG as configured.

4. The method according to claim 1, wherein, The bits of the bitmap correspond to the RBGs used for the bandwidth portion, indicating whether each RBG is allocated.

5. A base station, comprising: A transceiver that transmits and receives wireless signals; and A processor, coupled to the transceiver for operation. Wherein, the processor Send resource block assignment information including bitmaps, and Downlink signals are transmitted via resource block groups (RBGs) indicated by the bitmap within the bandwidth portion. The total number of Resource Block Groups (RBGs) for the bandwidth portion is determined based on the index of the starting resource block of the bandwidth portion, the size of the bandwidth portion, and the size of a configured RBG. Wherein: the bandwidth portion is bandwidth portion i, where i is 0 or a natural number, and N is based on the index of the starting resource block representing the bandwidth portion i. start BWP,i N represents the size of the bandwidth portion i. size BWP,i And P, representing the size of an RBG of the configuration. The total number N of the RBGs used for the bandwidth portion i is determined based on the following equation. RBG , 6. The base station according to claim 5, wherein, The number of bits in the bitmap is equal to the total number N of the RBGs. RBG .

7. The base station according to claim 5, wherein, The processor further sends a higher-level signal to notify the size of an RBG configured.

8. The base station according to claim 5, wherein, The bits of the bitmap correspond to the RBGs used for the bandwidth portion, indicating whether each RBG is allocated.

Images