WO2022154490A1

WO2022154490A1 - Method and apparatus for providing multicasting and broadcasting in communication system

Info

Publication number: WO2022154490A1
Application number: PCT/KR2022/000581
Authority: WO
Inventors: 윤수하; 김현정; 명세호; 여정호; 정의창
Original assignee: 삼성전자 주식회사
Priority date: 2021-01-14
Filing date: 2022-01-12
Publication date: 2022-07-21
Also published as: KR20220102956A

Abstract

The present disclosure relates to a 5th generation (5G) or pre-5G communication system for supporting a higher data transmission rate than a 4th generation (4G) communication system such as long term evolution (LTE). A method carried out by a terminal in a communication system, according to the present disclosure, comprises the steps of: receiving configuration information regarding a group common resource from a base station; receiving downlink control information (DCI) from the base station on the basis of the configuration information; checking whether or not a group common radio network temporary identifier (RNTI) has been used for scrambling of cyclic redundancy check (CRC) attached to the DCI; and, if the group common RNTI has been used, carrying out deinterleaving on the basis of a resource block (RB) group which has been classified on the basis of a group common frequency resource.

Description

Method and apparatus for providing multicasting and broadcasting in a communication system

The present disclosure relates to a mobile communication system, and more particularly, to a method of transmitting data to a plurality of terminals.

Efforts are being made to develop an improved 5G communication system or pre-5G communication system in order to meet the increasing demand for wireless data traffic after commercialization of the 4G communication system. For this reason, a 5G communication system or a pre-5G communication system is called a system after a 4G network (Beyond 4G Network) communication system or a long term evolution (LTE) system after (Post LTE). In order to achieve a high data rate, the 5G communication system is being considered for implementation in a very high frequency (mmWave) band (eg, such as a 60 gigabyte (60 GHz) band). In order to alleviate the path loss of radio waves and increase the propagation distance of radio waves in the very high frequency band, in the 5G communication system, beamforming, massive MIMO, and Full Dimensional MIMO (FD-MIMO) are used. ), array antenna, analog beam-forming, and large scale antenna technologies are being discussed. In addition, for network improvement of the system, in the 5G communication system, an evolved small cell, an advanced small cell, a cloud radio access network (cloud RAN), and an ultra-dense network (ultra-dense network) , Device to Device communication (D2D), wireless backhaul, moving network, cooperative communication, Coordinated Multi-Points (CoMP), and interference cancellation Technology development is underway. In addition, in the 5G system, the advanced coding modulation (ACM) methods FQAM (Hybrid FSK and QAM Modulation) and SWSC (Sliding Window Superposition Coding), and advanced access technologies FBMC (Filter Bank Multi Carrier), NOMA (non orthogonal multiple access), and sparse code multiple access (SCMA) are being developed.

On the other hand, the Internet is evolving from a human-centered connection network where humans create and consume information to an Internet of Things (IoT) network that exchanges and processes information between distributed components such as objects. Internet of Everything (IoE) technology, which combines big data processing technology through connection with cloud servers, etc. with IoT technology, is also emerging. In order to implement IoT, technology elements such as sensing technology, wired and wireless communication and network infrastructure, service interface technology, and security technology are required. , M2M), and MTC (Machine Type Communication) are being studied. In the IoT environment, an intelligent IT (Internet Technology) service that collects and analyzes data generated from connected objects and creates new values in human life can be provided. IoT is a field of smart home, smart building, smart city, smart car or connected car, smart grid, health care, smart home appliance, advanced medical service, etc. can be applied to

Accordingly, various attempts are being made to apply the 5G communication system to the IoT network. For example, in technologies such as sensor network, machine to machine (M2M), and MTC (Machine Type Communication), 5G communication technology is implemented by techniques such as beam forming, MIMO, and array antenna. there will be The application of a cloud radio access network (cloud RAN) as the big data processing technology described above is an example of the convergence of 5G technology and IoT technology.

The present disclosure provides a virtual RB to physical RB (VRB-to-PRB) mapping/configuration method and apparatus for transmission of a group common physical downlink shared channel (PDSCH) in a communication system.

The present disclosure provides a method and apparatus for transmitting/receiving a group common PDSCH and unicast PDSCH in a communication system.

According to various embodiments of the present disclosure, there is provided a method performed by a terminal in a communication system, the method comprising: receiving configuration information for a group common resource from a base station; receiving downlink control information (DCI) from the base station based on the configuration information; checking whether a group common radio network temporary identifier (RNTI) is used for scrambling of a cyclic redundancy check (CRC) attached to the DCI; and performing deinterleaving based on a resource block (RB) group divided based on a group common frequency resource when the group common RNTI is used.

In addition, according to various embodiments of the present disclosure, in a method performed by a base station in a communication system, the method comprising: transmitting configuration information for a group common resource to a terminal; transmitting the downlink control information (DCI) based on the configuration information; and when a group common radio network temporary identifier (RNTI) is used for scrambling of a cyclic redundancy check (CRC) attached to the DCI, interleaving is performed based on a resource block (RB) group divided based on a group common frequency resource. It is characterized in that it comprises the step of

In addition, according to various embodiments of the present disclosure, in a terminal in a communication system, a transceiver; And it is connected to the transceiver, receives configuration information for group common resources from the base station, receives downlink control information (DCI) from the base station based on the configuration information, and is attached to the DCI. Check whether a group common radio network temporary identifier (RNTI) is used for scrambling of a cyclic redundancy check (CRC), and when the group common RNTI is used, based on a resource block (RB) group divided based on a group common frequency resource to include a control unit for performing deinterleaving.

In addition, according to various embodiments of the present disclosure, in a base station in a communication system, a transceiver; And it is connected to the transceiver, transmits configuration information for group common resources to the terminal, transmits the downlink control information (DCI) based on the configuration information, and CRC attached to the DCI ( When a group common radio network temporary identifier (RNTI) is used for scrambling of cyclic redundancy check) do.

According to the present disclosure, when data is transmitted to a plurality of terminals through a common PDSCH in a communication system, by providing a VRB-to-PRB mapping/configuration method of the PDSCH, more efficient data transmission and reception can be performed.

In addition, according to the present disclosure, by providing a method for transmitting/receiving a group common PDSCH and a unicast PDSCH, a terminal and a base station can smoothly communicate.

1 is a diagram illustrating a structure of a next-generation mobile communication system according to an embodiment of the present disclosure.

2 is a diagram illustrating a radio protocol structure of a next-generation mobile communication system according to an embodiment of the present disclosure.

3 is a diagram illustrating a basic structure of a time-frequency domain, which is a radio resource domain in which data or a control channel is transmitted in a 5G communication system according to an embodiment of the present disclosure.

4 is a diagram illustrating an example of a slot structure considered in a 5G system according to an embodiment of the present disclosure.

5 is a diagram illustrating an example of setting a bandwidth portion in a 5G communication system according to an embodiment of the present disclosure.

6 is a diagram for explaining carrier aggregation (CA) according to an embodiment of the present disclosure.

7 is a diagram illustrating an example of a cross-carrier scheduling method according to an embodiment of the present disclosure.

8 is a diagram illustrating an example of setting a control resource set (CORESET) of a downlink control channel in a wireless communication system according to an embodiment of the present disclosure.

9 is a diagram illustrating an example of downlink data channel processing in a wireless communication system according to an embodiment of the present disclosure.

10 is a diagram illustrating an example of a group common frequency resource in a wireless communication system according to an embodiment of the present disclosure.

11A is a diagram illustrating an example of an operation of a terminal according to an embodiment of the present disclosure.

11B is a diagram illustrating an example of an operation of a base station according to an embodiment of the present disclosure.

12 is a diagram illustrating an example of a group common frequency resource in a wireless communication system according to an embodiment of the present disclosure.

13 is a diagram illustrating a structure of a terminal according to an embodiment of the present disclosure.

14 is a diagram illustrating a structure of a base station according to an embodiment of the present disclosure.

Hereinafter, embodiments of the present invention will be described in detail with reference to the accompanying drawings.

In describing the embodiments, descriptions of technical contents that are well known in the technical field to which the present invention pertains and are not directly related to the present invention will be omitted. This is to more clearly convey the gist of the present invention by omitting unnecessary description.

For the same reason, some components are exaggerated, omitted, or schematically illustrated in the accompanying drawings. In addition, the size of each component does not fully reflect the actual size. In each figure, the same or corresponding elements are assigned the same reference numerals.

Advantages and features of the present invention and methods of achieving them will become apparent with reference to the embodiments described below in detail in conjunction with the accompanying drawings. However, the present invention is not limited to the embodiments disclosed below, but may be implemented in various different forms, and only the embodiments of the present disclosure make the present disclosure complete, and common knowledge in the art to which the present invention pertains It is provided to fully inform those who have the scope of the invention, and the present disclosure is only defined by the scope of the claims. Like reference numerals refer to like elements throughout.

At this time, it will be understood that each block of the flowchart diagrams and combinations of the flowchart diagrams may be performed by computer program instructions. These computer program instructions may be embodied in a processor of a general purpose computer, special purpose computer, or other programmable data processing equipment, such that the instructions performed by the processor of the computer or other programmable data processing equipment are not described in the flowchart block(s). It creates a means to perform functions. These computer program instructions may also be stored in a computer-usable or computer-readable memory that may direct a computer or other programmable data processing equipment to implement a function in a particular manner, and thus the computer-usable or computer-readable memory. It may also be possible for the instructions stored in the flowchart block(s) to produce an article of manufacture containing instruction means for performing the function described in the flowchart block(s). The computer program instructions may also be mounted on a computer or other programmable data processing equipment, such that a series of operational steps are performed on the computer or other programmable data processing equipment to create a computer-executed process to create a computer or other programmable data processing equipment. It may also be possible for instructions to perform the processing equipment to provide steps for performing the functions described in the flowchart block(s).

Additionally, each block may represent a module, segment, or portion of code that includes one or more executable instructions for executing specified logical function(s). It should also be noted that in some alternative implementations it is also possible for the functions recited in the blocks to occur out of order. For example, two blocks shown one after another may in fact be performed substantially simultaneously, or it may be possible that the blocks are sometimes performed in a reverse order according to a corresponding function.

At this time, the term '~ unit' used in this embodiment means software or hardware components such as FPGA (Field Programmable Gate Array) or ASIC (Application Specific Integrated Circuit), and '~ unit' performs certain roles do. However, '-part' is not limited to software or hardware. '~unit' may be configured to reside in an addressable storage medium or may be configured to refresh one or more processors. Accordingly, according to some embodiments, '~ part' refers to components such as software components, object-oriented software components, class components, and task components, and processes, functions, properties, and programs. Includes procedures, subroutines, segments of program code, drivers, firmware, microcode, circuitry, data, databases, data structures, tables, arrays, and variables. The functions provided in the components and '~ units' may be combined into a smaller number of components and '~ units' or further separated into additional components and '~ units'. In addition, components and '~ units' may be implemented to play one or more CPUs in a device or secure multimedia card. Also, according to some embodiments, '~ unit' may include one or more processors.

Hereinafter, the operating principle of the present invention will be described in detail with reference to the accompanying drawings. In the following description of the present invention, if it is determined that a detailed description of a related well-known function or configuration may unnecessarily obscure the gist of the present invention, the detailed description thereof will be omitted. In addition, the terms described below are terms defined in consideration of functions in the present invention, which may vary according to intentions or customs of users and operators. Therefore, the definition should be made based on the content throughout this specification. Hereinafter, the base station is a subject performing resource allocation of the terminal, and may be at least one of gNode B, eNode B, Node B, base station (BS), radio access unit, base station controller, or a node on a network. The terminal may include a user equipment (UE), a mobile station (MS), a cellular phone, a smart phone, a computer, or a multimedia system capable of performing a communication function. Of course, it is not limited to the above example. Hereinafter, the present disclosure describes a technique for a terminal to receive broadcast information from a base station in a wireless communication system. The present disclosure relates to a communication technique that converges a 5 ^th generation (5G) communication system for supporting a higher data rate after a 4 ^th generation (4G) system with an Internet of Things (IoT) technology, and a system thereof. The present disclosure provides intelligent services (eg, smart home, smart building, smart city, smart car or connected car, healthcare, digital education, retail business, security and safety related services, etc.) based on 5G communication technology and IoT-related technology. ) can be applied to

A term referring to broadcast information, a term referring to control information, a term related to communication coverage, a term referring to a state change (eg, an event), and network entities used in the following description Terms referring to, terms referring to messages, terms referring to components of an apparatus, and the like are exemplified for convenience of description. Accordingly, the present invention is not limited to the terms described below, and other terms having equivalent technical meanings may be used.

For convenience of description below, some terms and names defined in 3GPP LTE (3rd generation partnership project long term evolution) standard or 3GPP NR (new radio or new radio access technology) may be used. However, the present invention is not limited by the above terms and names, and may be equally applied to systems conforming to other standards.

1, the radio access network of the next-generation mobile communication system (hereinafter NR or 5g) is a next-generation base station (new radio node B, hereinafter, NR gNB or NR base station) 110 and a next-generation radio core network (new radio core network, NR CN) 105 . A new radio user equipment (NR UE or terminal) 115 may access an external network through the NR gNB 110 and the NR CN 105 .

In FIG. 1 , the NR gNB 110 may correspond to an evolved node B (eNB) of the existing LTE system. The NR gNB is connected to the NR UE 115 through a radio channel, and can provide a more improved service than the existing Node B. In the next-generation mobile communication system, all user traffic may be serviced through a shared channel. Accordingly, an apparatus for scheduling by collecting status information such as buffer status, available transmission power status, and channel status of UEs is required, and the NR gNB 110 may be responsible for this. One NR gNB can control multiple cells. In a next-generation mobile communication system, a bandwidth greater than or equal to the current maximum bandwidth may be applied to implement ultra-high-speed data transmission compared to current LTE. In addition, beamforming technology may be additionally grafted by using orthogonal frequency division multiplexing (OFDM) as a radio access technology. In addition, an adaptive modulation & doding (AMC) scheme for determining a modulation scheme and a channel coding rate according to the channel state of the terminal may be applied.

The NR CN 105 may perform functions such as mobility support, bearer establishment, and QoS establishment. The NR CN is a device in charge of various control functions as well as a mobility management function for the terminal, and can be connected to a plurality of base stations. In addition, the next-generation mobile communication system may be interlocked with the existing LTE system, and the NR CN may be connected to the MME 125 through a network interface. The MME may be connected to the existing base station, the eNB 130 .

Referring to FIG. 2, radio protocols of the next-generation mobile communication system are NR service data adaptation protocol (SDAP) 201 and 245,

NR PDCP

205, 240, and NR RLC ( 210, 235), NR MAC (215, 230), and NR PHY (220, 225).

The main functions of the NR SDAPs 201 and 245 may include some of the following functions.

- Transfer of user plane data

- Mapping between a QoS flow and a DRB for both DL and UL for uplink and downlink

- Marking QoS flow ID in both DL and UL packets for uplink and downlink

- A function of mapping a reflective QoS flow to a data bearer for uplink SDAP PDUs (reflective QoS flow to DRB mapping for the UL SDAP PDUs).

For the SDAP layer device, the UE uses the header of the SDAP layer device for each PDCP layer device or for each bearer or for each logical channel as a radio resource control (RRC) message or whether to use the function of the SDAP layer device can be set. When the SDAP header is set, the terminal reflects the non-access stratum (NAS) quality of service (QoS) reflection setting 1-bit indicator (NAS reflective QoS) of the SDAP header and the access layer (access stratum, AS) QoS reflection As a set 1-bit indicator (AS reflective QoS), it can be instructed so that the UE can update or reconfigure mapping information for uplink and downlink QoS flows and data bearers. The SDAP header may include QoS flow ID information indicating QoS. The QoS information may be used as data processing priority, scheduling information, etc. to support a smooth service.

The main functions of the

NR PDCPs

205 and 240 may include some of the following functions.

- Header compression and decompression (ROHC only)

- Transfer of user data

- In-sequence delivery of upper layer PDUs

- Out-of-sequence delivery of upper layer PDUs

- Order reordering function (PDCP PDU reordering for reception)

- Duplicate detection of lower layer SDUs

- Retransmission of PDCP SDUs

- Encryption and decryption function (Ciphering and deciphering)

- Timer-based SDU discard in uplink.

In the above description, the reordering function of the NR PDCP device may refer to a function of reordering PDCP PDUs received from a lower layer in order based on a PDCP sequence number (SN). The reordering function of the NR PDCP device may include a function of delivering data to a higher layer in the rearranged order, and may include a function of directly delivering data without considering the order, It may include a function of recording PDCP PDUs, a function of reporting a status on the lost PDCP PDUs to the transmitting side, and a function of requesting retransmission of the lost PDCP PDUs. .

The main functions of the

NR RLCs

210 and 235 may include some of the following functions.

- Data transfer function (Transfer of upper layer PDUs)

- In-sequence delivery of upper layer PDUs

- Out-of-sequence delivery of upper layer PDUs

- ARQ function (Error Correction through ARQ)

- Concatenation, segmentation and reassembly of RLC SDUs

- Re-segmentation of RLC data PDUs

- Reordering of RLC data PDUs

- Duplicate detection

- Protocol error detection

- RLC SDU discard function (RLC SDU discard)

- RLC re-establishment function (RLC re-establishment)

In the above description, in-sequence delivery of the NR RLC device may refer to a function of sequentially delivering RLC SDUs received from a lower layer to a higher layer. When one RLC SDU is originally divided into several RLC SDUs and received, the in-sequence delivery function of the NR RLC device may include a function of reassembling it and delivering it.

In-sequence delivery of the NR RLC device may include a function of rearranging the received RLC PDUs based on an RLC sequence number (SN) or a PDCP sequence number (SN), and may be lost by rearranging the order It may include a function of recording the lost RLC PDUs, a function of reporting a status on the lost RLC PDUs to the transmitting side, and a function of requesting retransmission of the lost RLC PDUs. have.

The in-sequence delivery function of the NR RLC (210, 235) device may include a function of sequentially delivering only RLC SDUs before the lost RLC SDU to a higher layer when there is a lost RLC SDU. can In addition, the in-sequence delivery function of the NR RLC device includes a function of sequentially delivering all RLC SDUs received before the timer starts to a higher layer if a predetermined timer expires even if there are lost RLC SDUs. can do. In addition, the in-sequence delivery function of the NR RLC device may include a function of sequentially delivering all RLC SDUs received so far to a higher layer if a predetermined timer expires even if there are lost RLC SDUs. .

The NR RLC (210, 235) device may process the RLC PDUs in the order in which they are received, regardless of the sequence number (Out of sequence delivery), and deliver it to the NR PDCP (205, 240) device.

When the NR RLC (210, 235) device receives a segment, it receives the segments stored in the buffer or to be received later, reconstructs it into one complete RLC PDU, and then delivers it to the NR PDCP device. have.

The NR RLC layer may not include a concatenation function, and may perform a function in the NR MAC layer or may be replaced with a multiplexing function of the NR MAC layer.

In the above description, the out-of-sequence delivery function of the NR RLC device may refer to a function of directly delivering RLC SDUs received from a lower layer to a higher layer regardless of order. The out-of-sequence delivery function of the NR RLC device may include a function of reassembling and delivering when one RLC SDU is originally divided into several RLC SDUs and received. The out of sequence delivery function of the NR RLC device may include a function of storing the RLC SN or PDCP SN of the received RLC PDUs and arranging the order to record the lost RLC PDUs.

The

NR MACs

215 and 230 may be connected to several NR RLC layer devices configured in one terminal, and the main function of the NR MAC may include some of the following functions.

- Mapping function (Mapping between logical channels and transport channels)

- Multiplexing/demultiplexing of MAC SDUs

- Scheduling information reporting function

- HARQ function (Error correction through HARQ (hybrid automatic repeat request))

- Priority handling between logical channels of one UE

- Priority handling between UEs by means of dynamic scheduling

- MBMS service identification

- Transport format selection

- Padding function

The NR PHY layers 220 and 225 channel-code and modulate the upper layer data, make an OFDM symbol and transmit it to the radio channel, or demodulate the OFDM symbol received through the radio channel, decode the channel, and deliver the operation to the upper layer. can be done

Hereinafter, the frame structure of the 5G system will be described in more detail with reference to the drawings.

3 is a diagram illustrating a basic structure of a time-frequency domain, which is a radio resource domain in which data or a control channel is transmitted in a 5G system.

3 , the horizontal axis represents the time domain, and the vertical axis represents the frequency domain. A basic unit of resources in the time and frequency domain is a resource element (RE) 301 as 1 orthogonal frequency division multiplexing (OFDM) symbol 302 on the time axis and 1 subcarrier 303 on the frequency axis. can be defined. in the frequency domain

(for example, 12) consecutive REs may constitute one resource block (RB) 304 .

4 is a diagram illustrating an example of a slot structure considered in a 5G system.

4 shows an example of a structure of a frame 400 , a subframe 401 , and a slot 402 . One frame 400 may be defined as 10 ms. One subframe 401 may be defined as 1 ms, and therefore, one frame 400 may consist of a total of 10 subframes 401 . One slot (402, 403) may be defined as 14 OFDM symbols (that is, the number of symbols per slot (

)=14). One subframe 401 may consist of one or a plurality of

slots

402 and 403, and the number of

slots

402 and 403 per one subframe 401 is a set value μ(404, 405) for the subcarrier spacing. ) may vary depending on In the example of FIG. 4 , a case of μ=0 (404) and a case of μ=1 (405) are illustrated as subcarrier spacing setting values. When μ=0 (404), one subframe 401 may consist of one slot 402, and when μ=1 (405), one subframe 401 may consist of two slots 403. can be composed of That is, the number of slots per subframe (

) may vary, and accordingly, the number of slots per frame (

) may be different. According to each subcarrier spacing setting μ

and

may be defined in Table 1 below.

[Table 1]

Next, a bandwidth part (BWP) setting in the 5G communication system will be described in detail with reference to FIG. 5 .

5 is a diagram illustrating an example of setting a bandwidth portion in a 5G communication system.

5 shows an example in which the UE bandwidth 500 is set to two bandwidth parts, that is, a bandwidth part #1 (BWP#1) 501 and a bandwidth part #2 (BWP#2) 502. has been The base station may set one or a plurality of bandwidth portions to the terminal, and may set information as shown in Table 2 below for each bandwidth portion, for example. The following BWP may be referred to as BWP setting information.

[Table 2]

Of course, it is not limited to the above example, and in addition to the configuration information, various parameters related to the bandwidth portion may be configured in the terminal. The information may be transmitted from the base station to the terminal through higher layer signaling, for example, RRC signaling. At least one bandwidth portion among the set one or a plurality of bandwidth portions may be activated. Whether to activate the set bandwidth portion may be semi-statically transmitted from the base station to the terminal through RRC signaling or may be dynamically transmitted through downlink control information (DCI).

According to some embodiments, the terminal before the RRC connection may receive an initial bandwidth portion (initial BWP) for the initial connection from the base station through a master information block (MIB). More specifically, the terminal in the initial access stage through the MIB required for the initial access system information (remaining system information; RMSI or system information block 1; may correspond to SIB1) PDCCH for reception of which can be transmitted. Setting information for a control resource set (CORESET) and a search space may be received. The control resource set and search space set by the MIB may be regarded as an identifier (identity, ID) 0, respectively. The base station may notify the terminal of configuration information such as frequency allocation information, time allocation information, and numerology for the control resource set #0 through the MIB. In addition, the base station may notify the terminal through the MIB of configuration information on the monitoring period and occasion for the control resource set #0, that is, configuration information on the search space #0. The UE may regard the frequency domain set as the control resource set #0 obtained from the MIB as an initial bandwidth portion for initial access. In this case, the identifier (ID) of the initial bandwidth portion may be regarded as 0.

The configuration of the bandwidth part supported by the 5G may be used for various purposes.

According to some embodiments, when the bandwidth supported by the terminal is smaller than the system bandwidth, this may be supported through the bandwidth part setting. For example, when the base station sets the frequency position (setting information 2) of the bandwidth portion to the terminal, the terminal can transmit/receive data at a specific frequency location within the system bandwidth.

Also, according to some embodiments, the base station may set a plurality of bandwidth portions to the terminal for the purpose of supporting different numerologies. For example, in order to support both data transmission and reception using a subcarrier interval of 15 kHz and a subcarrier interval of 30 kHz to a certain terminal, two bandwidth portions may be set to a subcarrier interval of 15 kHz and 30 kHz, respectively. Different bandwidth portions may be frequency division multiplexed, and when data is to be transmitted/received at a specific subcarrier interval, a bandwidth portion set to the corresponding subcarrier interval may be activated.

Also, according to some embodiments, for the purpose of reducing power consumption of the terminal, the base station may set a bandwidth portion having different sizes of bandwidths to the terminal. For example, when the terminal supports a very large bandwidth, for example, a bandwidth of 100 MHz and always transmits and receives data using the corresponding bandwidth, very large power consumption may occur. In particular, monitoring an unnecessary downlink control channel with a large bandwidth of 100 MHz in a situation in which there is no traffic may be very inefficient in terms of power consumption. For the purpose of reducing power consumption of the terminal, the base station may set a relatively small bandwidth portion for the terminal, for example, a bandwidth portion of 20 MHz. In a situation in which there is no traffic, the terminal may perform a monitoring operation in the 20 MHz bandwidth portion, and when data is generated, it may transmit/receive data in the 100 MHz bandwidth portion according to the instruction of the base station.

In the method of setting the bandwidth part, terminals before RRC connection (connected) may receive configuration information for the initial bandwidth part through the MIB in the initial access step. More specifically, the UE may receive a control resource set (CORESET) for a downlink control channel through which DCI scheduling SIB may be transmitted from the MIB of a physical broadcast channel (PBCH). The bandwidth of the control resource set set as the MIB may be regarded as an initial bandwidth portion, and the terminal may receive the PDSCH through which the SIB is transmitted through the configured initial bandwidth portion. The initial bandwidth portion may be utilized for other system information (OSI), paging, and random access in addition to the purpose of receiving the SIB.

Referring to FIG. 6 , when CA is configured ( 600 ), a primary cell (PCell) and a secondary cell (SCell) may be configured in the terminal.

PCell is included in PCC (primary component carrier), RRC connection establishment/re-establishment, measurement, mobility procedure, random access procedure and selection, system information acquisition, initial random access, security key change and non-access stratum (NAS) function etc. can be provided.

Since the UE performs system information monitoring through the PCell, the PCell is not deactivated, and the PCC in the UL is carried through a physical uplink control channel (PUCCH) for transmitting control information. In addition, only one RRC connection is possible between the UE and the PCell, and PDCCH/PDSCH/PUSCH (physical uplink shared channel)/PUCCH transmission is possible. Also, in the secondary cell group, a spcell of a secondary cell group (PSCell) may be configured and operated as the PCell. The operation for the PCell described below may also be performed by the PSCell.

A maximum of 31 SCells can be added, and when additional radio resource provision is required, the SCell can be configured through an RRC message message (eg, dedicated signaling). The RRC message may include a physical cell ID for each cell, and may include a DL carrier frequency (absolute radio frequency channel number: ARFCN). PDCCH/PDSCH/PUSCH transmission is possible through the SCell. Supports dynamic activation and deactivation procedures of SCell for battery conservation of UE through MAC layer.

Cross-carrier scheduling may mean allocating at least one (eg, PDCCH) of all L1 control channels or L2 control channels for at least one other CC (component carrier) to one CC. A carrier indicator field (CIF) may be used to transmit data information of another CC through the PDCCH of one CC.

Resources (PDSCH, PUSCH) for data transmission of the CC or resources (PDSCH, PUSCH) for data transmission of another CC may be allocated through control information transmitted through the PDCCH of one CC.

The n-bit CIF is added to the DCI format by applying the cross-carrier scheduling, the bit size may be different depending on the upper layer configuration or the DCI format, and the position of the CIF in the DCI format may be fixed.

Referring to 710 of FIG. 7 , PDSCH or PUSCH for two CCs may be scheduled through the PDCCH 701 of one CC.

In addition, referring to 720 of FIG. 7 , when a total of four CCs are configured, the PDSCH or PUSCH of each CC may be scheduled using the

PDCCHs

721 and 723 of the two CCs.

Each CC may be mapped to a CI (carrier indicator) value for CIF application, which may be transmitted from the base station to the terminal through a dedicated RRC signal as a UE-specific configuration.

Each PDSCH/PUSCH CC may be scheduled from one DL CC. Accordingly, the UE only needs to monitor the PDCCH for the DL CC for each PDSCH/PUSCH CC. The UE may monitor the PDCCH in the DL CC to obtain PUSCH scheduling information in the linked UL carrier. The UE may monitor the PDCCH in the DL CC to obtain PDSCH scheduling information in the linked DL carrier.

8 is a diagram illustrating an example of setting a control area (CORESET) of a downlink control channel in a wireless communication system according to an embodiment of the present disclosure.

Referring to FIG. 8 , in FIG. 8 , there are two control regions (control region #1 (CORESET #1) 801) in a bandwidth part 810 of the terminal on the frequency axis and one slot 820 on the time axis. An example in which #2 (CORESET #2) 802) is set is shown. The control regions 801 and 802 may be set in a specific frequency resource 803 within the entire terminal bandwidth portion 810 on the frequency axis. The control regions 801 and 802 may be set with one or a plurality of OFDM symbols on the time axis, which may be defined as a control resource set duration (804). In the example of FIG. 8 , the control region #1 801 is set to a control region length of two symbols, and the control region #2 802 is set to a control region length of one symbol.

The control region in 5G described above may be configured by the base station through higher layer signaling (eg, system information, MIB, RRC signaling) to the terminal. Setting the control region to the terminal means to provide the terminal with information such as a control region identity, a frequency position of the control region, and a symbol length of the control region. For example, the information in Table 3 may be included.

[Table 3]

The number of CCEs required to transmit the PDCCH may be 1, 2, 4, 8, or 16 according to an aggregation level (AL), and the number of different CCEs is based on link adaptation of the downlink control channel. can be used to implement For example, when AL=L, one downlink control channel may be transmitted through L CCEs. The UE must detect a signal (blind decoding) without knowing information about the downlink control channel, and a search space indicating a set of CCEs is defined for blind decoding. The search space is a set of downlink control channel candidates consisting of CCEs that the UE should attempt to decode on a given aggregation level, and various aggregations that make one bundle with 1, 2, 4, 8, or 16 CCEs Since there is a level, the terminal may have a plurality of search spaces. A search space set may be defined as a set of search spaces in all set aggregation levels.

The search space may be classified into a common search space and a UE-specific search space. A group of terminals or all terminals may search the common search space of the PDCCH in order to receive control information common to cells such as dynamic scheduling for system information or a paging message. For example, the PDSCH scheduling assignment information for transmission of the SIB including the operator information of the cell may be received by examining the common search space of the PDCCH. In the case of the common search space, since terminals of a certain group or all terminals need to receive the PDCCH, it may be defined as a set of promised CCEs. The UE-specific scheduling assignment information for PDSCH or PUSCH may be received by examining the UE-specific search space of the PDCCH. The UE-specific search space may be UE-specifically defined as a function of UE identity and various system parameters.

In 5G, the parameter for the search space for the PDCCH may be set from the base station to the terminal through higher layer signaling (eg, SIB, MIB, RRC signaling). For example, the base station is the number of PDCCH candidates in each aggregation level L, the monitoring period for the search space, the monitoring occasion in symbol units in the slot for the search space, the search space type (common search space or terminal-specific search space), A combination of a DCI format and a radio network temporary identifier (RNTI) to be monitored in the corresponding search space, a control resource set index for monitoring the search space, etc. may be set to the UE. For example, the parameter for the search space for the PDCCH may include, for example, at least a part of information as shown in Table 4 below.

[Table 4]

The base station may set one or a plurality of search space sets to the terminal. According to some embodiments, the base station may set the search space set 1 and the search space set 2 to the terminal. In search space set 1, the UE may be configured to monitor DCI format A scrambled with X-RNTI in the common search space, and in search space set 2, the UE uses DCI format B scrambled with Y-RNTI in the UE-specific search space. can be set to monitor.

According to the configuration information, one or a plurality of search space sets may exist in the common search space or the terminal-specific search space. For example, the search space set #1 and the search space set #2 may be set as the common search space, and the search space set #3 and the search space set #4 may be set as the terminal-specific search space.

In the common search space, a combination of the following DCI format and RNTI may be monitored. Of course, it is not limited to the following examples.

DCI format 0_0/1_0 with CRC (cyclic redundancy check) scrambled by C-RNTI, CS-RNTI, SP-CSI-RNTI, RA-RNTI, TC-RNTI, P-RNTI, SI-RNTI

DCI format 2_0 with CRC scrambled by SFI-RNTI

DCI format 2_1 with CRC scrambled by INT-RNTI

DCI format 2_2 with CRC scrambled by TPC-PUSCH-RNTI, TPC-PUCCH-RNTI

DCI format 2_3 with CRC scrambled by TPC-SRS-RNTI

In the UE-specific search space, a combination of the following DCI format and RNTI may be monitored. Of course, it is not limited to the following examples.

DCI format 0_0/1_0 with CRC scrambled by C-RNTI, CS-RNTI, TC-RNTI

DCI format 1_0/1_1 with CRC scrambled by C-RNTI, CS-RNTI, TC-RNTI

The specified RNTIs may follow the definitions and uses below.

C-RNTI (Cell RNTI): UE-specific PDSCH scheduling purpose

TC-RNTI (Temporary Cell RNTI): UE-specific PDSCH scheduling purpose

CS-RNTI (Configured Scheduling RNTI): semi-statically configured UE-specific PDSCH scheduling purpose

RA-RNTI (Random Access RNTI): Used for scheduling PDSCH in the random access phase

P-RNTI (Paging RNTI): Used for scheduling PDSCH in which paging is transmitted

SI-RNTI (System Information RNTI): Used for scheduling PDSCH in which system information is transmitted

INT-RNTI (Interruption RNTI): Used to indicate whether PDSCH is pucturing

TPC-PUSCH-RNTI (Transmit Power Control for PUSCH RNTI): Used to indicate power control command for PUSCH

TPC-PUCCH-RNTI (Transmit Power Control for PUCCH RNTI): Used to indicate power control command for PUCCH

TPC-SRS-RNTI (Transmit Power Control for SRS RNTI): Used to indicate power control command for SRS

In 5G, the search space of the aggregation level L in the control resource set p and the search space set s may be expressed as in Equation 1 below.

[Equation 1]

The value may correspond to 0 in the case of a common search space.

In the case of a terminal-specific search space, the value may correspond to a value that changes depending on the terminal's identity (C-RNTI or ID set for the terminal by the base station) and the time index.

Accordingly, the terminal may monitor the PDCCH in the control region configured by the base station, and may transmit/receive data based on the received control information.

In the 5G system, scheduling information for uplink data (or physical uplink data channel (PUSCH)) or downlink data (or physical downlink data channel (PDSCH)) may be transmitted from the base station to the terminal through DCI. The UE may monitor a DCI format for fallback and a DCI format for non-fallback for PUSCH or PDSCH. The DCI format for countermeasures may be composed of a fixed field predetermined between the base station and the terminal, and the DCI format for non-prevention may include a configurable field.

DCI may be transmitted through a PDCCH, which is a physical downlink control channel, through channel coding and modulation. A CRC is added to the DCI message payload, and the CRC may be scrambling based on the RNTI corresponding to the identity of the UE. Different RNTIs may be used according to the purpose of the DCI message, for example, UE-specific data transmission, a power control command, or a random access response. That is, the RNTI is not explicitly transmitted, but included in the CRC calculation process and transmitted. Upon receiving the DCI message transmitted on the PDCCH, the UE checks the CRC using the assigned RNTI. If the CRC check result is correct, the UE can know that the message has been transmitted to the UE.

For example, DCI scheduling PDSCH for system information (SI) may be scrambled with SI-RNTI. DCI scheduling a PDSCH for a random access response (RAR) message may be scrambled with an RA-RNTI. DCI scheduling a PDSCH for a paging message may be scrambled with a P-RNTI. DCI notifying a slot format indicator (SFI) may be scrambled with an SFI-RNTI. DCI notifying transmit power control (TPC) may be scrambled with TPC-RNTI. DCI for scheduling UE-specific PDSCH or PUSCH may be scrambled with C-RNTI (cell RNTI).

Meanwhile, in NR, various types of DCI formats may be provided as shown in Table 5 below for efficient reception of control information of the UE.

[Table 5]

For example, the base station may use DCI format 1_0, DCI format 1_1, or DCI format 1_2 to allocate (scheduling) the PDSCH for one cell to the terminal. For another example, the base station may use DCI format 0_0, DCI format 0_1, or DCI format 0_2 to allocate (scheduling) the PUSCH for one cell to the terminal. DCI format 1_0 is C-RNTI Alternatively, when transmitted together with a CRC scrambled by CS-RNTI, MCS-C-RNTI, or new-RNTI, it may include, for example, at least the information shown in Table 6:

[Table 6]

DCI format 1_1 is transmitted together with CRC scrambled by cell radio network temporary identifier (C-RNTI) or configured scheduling RNTI (CS-RNTI) or MCS-C-RNTI or new-RNTI, for example, at least the table It may include information such as 7.

[Table 7]

When DCI format 1_2 is transmitted together with CRC scrambled by C-RNTI (cell radio network temporary identifier) or CS-RNTI (configured scheduling RNTI) or MCS-C-RNTI or new-RNTI, for example, at least the table It may include information such as 8.

[Table 8]

The maximum number of DCIs of different sizes that the UE can receive per slot in the corresponding cell is 4. The maximum number of DCIs of different sizes scrambled with C-RNTI per slot in the cell by the UE is 3. The base station provides the UE with time domain resources for a downlink data channel (PDSCH) and an uplink data channel (PUSCH). Allocation information (eg, may be information configured in the form of a table) may be configured through higher layer signaling (eg, RRC signaling). The base station can set resource allocation information (for example, composed of table-type information) consisting of a maximum of maxNrofDL-Allocations = 16 entries for the PDSCH, and a maximum of maxNrofUL-Allocations = 16 entries for the PUSCH ( Entry), resource allocation information (eg, table-type information) can be set. The time domain resource allocation information includes, for example, the PDCCH-to-PDSCH slot timing (corresponding to the time interval in slot units between the time when the PDCCH is received and the time when the PDSCH scheduled by the received PDCCH is transmitted, denoted by K0) or PDCCH-to-PUSCH slot timing (corresponding to the time interval in slot units between the time when the PDCCH is received and the time when the PUSCH scheduled by the received PDCCH is transmitted, denoted by K2), the PDSCH or PUSCH scheduled within the slot Information on the position and length of the start symbol, the mapping type of PDSCH or PUSCH, etc. may be included. For example, information as shown in Table 9 or Table 10 below may be notified from the base station to the terminal.

[Table 9]

[Table 10]

The base station may notify the UE of one of the entries in the table for the time domain resource allocation information through L1 signaling (eg, DCI) (eg, it may be indicated by the time domain resource allocation field in DCI). The UE may acquire time domain resource allocation information for the PDSCH or PUSCH based on the DCI received from the base station.

Hereinafter, a method of allocating a frequency domain resource for a data channel in a 5G communication system will be described.

In 5G, two types, resource allocation type 0 and resource allocation type 1, are supported as a method of indicating frequency domain resource allocation information for a downlink data channel (PDSCH) and an uplink data channel (PUSCH).

In resource allocation type 0, RB allocation information may be notified from the base station to the terminal in the form of a bitmap for a resource block group (RBG). In this case, the RBG may be composed of a set of consecutive VRBs, and the size P of the RBG is based on a value set as a higher layer parameter (rbg-Size) and a size value of the bandwidth part defined as shown in Table 11 below. can be determined by

[Table 11] Nominal RBG size P

size

the total number of RBGs in bandwidth part i (

) may be defined as follows.

, where

the size of the first RBG is

,

the size of last RBG is

if

and P otherwise,

the size of all other RBGs is P.

Each bit of the bit-sized bitmap may correspond to each RBG. RBGs may be indexed in the order of increasing frequency, starting from the lowest frequency position of the bandwidth part. within the bandwidth

For RBGs, from RBG#0 to RBG#(

) may be mapped from the MSB to the LSB of the RBG bitmap. When a specific bit value in the bitmap is 1, the UE can determine that the RBG corresponding to the bit value is allocated, and when the specific bit value in the bitmap is 0, the RBG corresponding to the bit value is not allocated. can judge

In resource allocation type 1, RB allocation information may be notified from the base station to the terminal as information on the start position and length of the continuously allocated VRBs. In this case, interleaving or non-interleaving may be additionally applied to consecutively allocated VRBs. The resource allocation field of resource allocation type 1 may consist of a resource indication value (RIV), and the RIV is the starting point of the VRB (

) and the length of consecutively allocated RBs (

) may consist of More specifically,

The RIV in the bandwidth part of the size may be defined as follows.

A scrambling process may be performed for each of one codeword or two codewords ( S901 ). length

a sequence of codewords q with

A scrambling sequence obtained through initialization as in Equation 3

A sequence scrambled through the same process as in Equation 2 using

can be obtained.

The value is set through the upper layer parameter, or otherwise as the cell ID value.

can be determined,

may mean an RNTI associated with PDSCH transmission.

sequence of scrambled bits

and using one of various modulation schemes supported by the wireless communication system.

A modulation symbol sequence with a length of

may be generated (902).

For each layer in v layers

Each modulation symbol may be mapped (903), which represents

same as Table 12 shows the relationship between the number of layers, the number of codewords, and the codeword-layer mapping.

[Table 12]

The modulation symbols mapped to the layer may be mapped to an antenna port as shown in Equation (4).

may be determined by information included in the DCI format (904).

[Equation 4]

completed the above process

Symbols may be mapped to REs that satisfy conditions that can be used for PDSCH transmission among REs in VRBs allocated for transmission (eg, mapping impossible to DM-RS resources, etc.) (905).

VRBs that have completed the above process may be mapped to PRBs through an interleaving mapping method or a non-interleaving mapping method ( 906 ). The mapping method may be indicated through the VRB-to-PRB mapping field in DCI. If there is no indication of the mapping method, it may mean a non-interleaving mapping method.

When a non-interleaving mapping method is used, VRB n may be mapped to PRB n except in specific cases. For example, in the specific case, VRB n of a PDSCH scheduled using DCI format 1_0 through a common search space is PRB

(

may include a case in which the DCI is mapped to the first PRB of the transmitted CORESET).

When the interleaving mapping method is used, RBs in the BWP are

RB bundles are divided into RB bundles, and the RB bundles may be mapped in the manner shown in Table 13.

RBs in BWP

One example of dividing into RB bundles may be as follows. starting point

within the BWP with

A set of RBs is

It is divided into RB bundles, and the RB bundles may be indexed in an increasing order. Here, L _i means a bundle size in BWP i, which may be transmitted to the UE by the higher layer parameter vrb-ToPRB-Interleaver. And, RB bundle 0 is

Consists of RBs, RB bundle

Is

If you are satisfied with

RBs, otherwise it may be composed of L _i RBs. And the remaining RB bundles may be composed of L _i RBs.

[Table 13]

According to an embodiment of the present disclosure, the base station may transmit data to the terminal in a 1:1 relationship (uni-cast) or may transmit data in a 1:N relationship (multi-cast, group-cast, broad -cast, etc.).

According to an embodiment of the present disclosure, a DCI to which a scrambled CRC (CRC generated using DCI information) is attached based on a group-common RNTI (RNTI) is a group-common PDCCH (PDCCH). can be transmitted through The DCI may schedule a group-common PDSCH (PDSCH). In this case, the RNTI used in Equation 3 of step 901 may be a group-common RNTI (RNTI), and the same value may be set for the group-common RNTI for the terminals of the group. Meanwhile, the group common RNTI of the present disclosure may be a newly defined RNTI for group communication, or an RNTI configured to be used for group communication among RNTIs configured in the terminal.

According to an embodiment of the present disclosure, a DCI to which a scrambled CRC (CRC generated using DCI information) is attached based on a UE-specific RNTI (eg, C-RNTI) for each UE is a PDCCH ( UE-specific PDCCH). The DCI may schedule a group-common PDSCH (PDSCH). In this case, the RNTI used in Equation 3 of step 901 may be a group-common RNTI (RNTI), and the same value may be set for the terminals of the group.

According to an embodiment of the present disclosure, at least one group common frequency resource for transmission of a group common PDCCH and a group common PDSCH may be defined. The group common frequency resource may be configured in the terminal through group common resource configuration. The group common resource configuration may be transmitted through RRC, MIB, or SIB, and may be transmitted as a separate information element or included in configuration information (eg, BWP configuration information) transmitted to the terminal. Specific details will be described later.

Referring to FIG. 10 , a group common frequency resource 1030 is included in a bandwidth 1000 of UE#1, a bandwidth 1010 of UE#2, and a bandwidth 1020 of UE#3. can In the present disclosure, the bandwidth may refer to the entire bandwidth or a portion of the bandwidth indicating a portion of the total bandwidth. Specific details of the bandwidth portion are the same as those described with reference to FIG. 5 .

Meanwhile, configuration information for downlink BWP (BWP-Downlink) and configuration information for uplink BWP (BWP-Uplink) may be configured in the terminal. The downlink BWP may include configuration information for a downlink common BWP (BWP-DownlinkCommon) and a downlink dedicated BWP (BWP-DownlinkDedicated). The downlink common BWP is a cell-specific BWP, and the downlink common BWP configuration information may include parameters commonly applied to terminals located in the cell. The downlink-specific BWP is a UE-specific BWP, and the downlink-specific BWP configuration information may include a UE-specific (dedicated) parameter.

The group common frequency resource may consist of some or all of the BWP resources, may be configured in the terminal, and in the present disclosure, the BWP related to the group common frequency may be referred to as a group common BWP. In the present disclosure, the group common BWP is described as an example of a BWP used for multicast or broadcast, but the scope of the present disclosure is not limited thereto. That is, the present disclosure can be applied to various methods for 1: multiple communication.

The group common BWP may be set in the terminal as a BWP separate from the previously configured BWP (legacy BWP), or some frequency resources of the BWP configured in the terminal may be set in the terminal as a group common BWP.

When configured in the terminal as a BWP separate from the legacy BWP, configuration information for the group common BWP is included in the downlink common BWP, or configuration information for the group common BWP may be defined separately. The configuration information for the group common BWP may include information on the group common PDCCH region and information on the group common PDSCH region.

When a specific frequency resource among BWPs set in the terminal is set in the terminal as the group common BWP, for example, the terminal may use all or part of the downlink common BWP as the group common BWP. Alternatively, some BWPs or frequency resources among a plurality of BWPs set in the terminal may be used as the group common BWP.

Specifically, according to an embodiment of the present disclosure, the group common frequency resource may be configured in the terminal as a specific BWP (hereinafter, group common BWP). The group common frequency resource set through the group common BWP is included in the frequency resource of the BWP (eg, unicast BWP, initial BWP, default BWP, etc.) set in the terminal or may be set as a separate frequency resource. . When the group common BWP is included in the frequency resource of the BWP configured in the terminal, the subcarrierSpacing and the cyclicPrefix of the group common BWP have the same size (or value) as the subcarrierSpacing and the cyclicPrefix of the other BWP configured in the terminal. It can be characterized. Meanwhile, when the group common BWP is configured separately from the frequency resource of the BWP configured in the terminal, subcarrierSpacing and cyclicPrefix for the group common BWP may be included in the group common BWP configuration information. The group common BWP configuration information may be the same information as the above-described group common resource configuration information or information included in the group common resource configuration information. When the number of BWPs that can be set in the terminal is n, the specific BWP(s) may be excluded from counting the number of BWPs. Alternatively, the specific BWP(s) may also be included in counting the number of BWPs. The configuration information may be delivered to a connected terminal (RRC-connected UE) through an RRC message or the like, or may be included in cell broadcasting information (eg, SIB) and delivered to the terminal.

According to an embodiment of the present disclosure, the group common frequency resource may be set in the terminal as a specific frequency resource in the BWP (eg, unicast BWP, initial BWP, default BWP, etc.) configured in the terminal. It may be characterized in that the BWP configured in the terminal and the subcarrierSpacing and the cyclicPrefix of the group common frequency resource have the same size (or value). The configuration information may be delivered to a connected terminal (RRC-connected UE) through an RRC message or the like, or may be included in cell broadcasting information (eg, SIB) and delivered to the terminal.

Referring to FIG. 10 , the size and/or location of a bandwidth and/or a bandwidth portion (BWP) may be different for each terminal. Accordingly, when the VRB-to-PRB mapping process is applied to the group common frequency resource, a problem in which resources are mapped for each terminal may be different. Accordingly, the present disclosure proposes a method of mapping resources in order to solve the above problem.

According to an embodiment of the present disclosure, in the VRB-to-PRB mapping operation 906 of the group common PDSCH scheduled on the group common frequency resource, only a non-interleaving mapping method may be provided. That is, more specifically, VRB n included in the group common frequency resource may be mapped to PRB n.

According to an embodiment of the present disclosure, in the VRB-to-PRB mapping operation 906 of the group common PDSCH scheduled on the group common frequency resource, an interleaving mapping and a non-interleaving mapping method may be provided.

According to an embodiment of the present disclosure, the VRB-to-PRB mapping operation (interleaving mapping or not) of the group common PDSCH scheduled on the group common frequency resource is a field in the DCI transmitted through the group common PDCCH (eg For example, it may be determined by the VRB-to-PRB mapping field). The DCI may be DCI format 1_0, 1_1, 1_2 or a new DCI format. If the field does not exist, it may mean a non-interleaving mapping method.

According to an embodiment of the present disclosure, the non-interleaving mapping method may mean that VRB n included in the group common frequency resource is mapped to PRB n.

According to an embodiment of the present disclosure, when the interleaving mapping scheme is used, RBs in the group common frequency resource are divided into at least one RB bundle, and the RB bundle is an interleaver (eg, Equation 5) through an interleaver).

According to an embodiment of the present disclosure, a group common frequency resource may be configured through group common BWP configuration information. As described above, the group common BWP configuration information may be BWP information configured for the terminal group(s) or frequency resource information configured for a specific terminal group in the BWP configured for a specific terminal. The group common BWP configuration information may be the same information as the group common resource configuration information or information included in the group common resource configuration information.

Based on the group common BWP configuration information, resource information of a group common frequency resource (eg, the number of start RBs and RBs (or sizes)) may be configured. Accordingly, the UE may classify RBs included in the group common frequency resource into at least one RB group (or RB bundle). This may be defined as at least one or more VRBs for applying interleaving mapping. In this way, by classifying RB groups based on the group common frequency resource information, when the VRB-to-PRB mapping process is applied because the bandwidth or the size and location of the bandwidth is different for each terminal, the problem of different resources mapped for each terminal is prevented. can do.

The at least RB groups may be indexed in ascending order, and the bundle size (L _i ) may be set through RRC signaling for each UE, or may be multicast or broadcast to UEs belonging to the group.

The number of RBs of the first RB bundle (first RB bundle or RB bundle 0) may be determined based on at least one of information such as the size of the bundle (L _i ) or the start position of the group common frequency resource, and the bundle's may be different from the size (L _i ). In addition, the number of RBs of the last RB bundle may be determined based on at least one of information such as the size (L _i ) of the bundle, the start position of the group common frequency resource, or the size, and the bundle may be different from the size of (L _i ). In this case, the method of determining the number of RBs of the first RB bundle and the method of determining the number of RBs of the last RB bundle may be different, and may be predefined or set by the base station. Specific details will be described below.

According to an embodiment of the present disclosure, a starting point (or starting RB)

within the group common frequency resource i with

A set of RBs includes at least one RB bundle (

), the at least one or more RB bundles may be indexed in an ascending order. here

denotes a bundle size in the group common frequency resource i, which may be signaled for each terminal to terminals belonging to the group through a higher layer, or may be multicast or broadcast to terminals belonging to the group. or applied to the group common frequency resource.

may be fixed to a specific value (eg 2 or 4). Meanwhile, the specific value may include a value other than 2 or 4.

And, the number of RBs included in RB bundle 0 is the size of the bundle.

, or may be determined based on at least one of information such as the start position of the group common frequency resource, for example,

It may be composed of RBs.

Also, RB bundle

(last RB bundle, or last RB bundle) may be determined based on at least one of the size L _i of the bundle, the start position of the group common frequency resource, or the size, for example,

If you are satisfied with

RBs, otherwise it may be composed of L _i RBs.

And the remaining RB bundles may be composed of L _i RBs.

and,

VRBs in may be mapped to PRBs as follows. VRB Bundle

Silver PRB Bundle

can be mapped to rest of the VRB bundles

may be mapped to the PRB bundle f(j) based on a predetermined (or defined) method (eg, a method such as Equation 5).

According to an embodiment of the present disclosure, the

means the starting point (or starting RB) of the group common BWP i set for a specific group,

may mean the number of RBs included in the specific BWP i configured for the specific group.

Or according to an embodiment of the present disclosure, the

Means the starting point of the frequency resource i set for a specific group within the BWP,

may mean the number of RBs included in the frequency resource i ' configured for a specific group in the BWP.

Referring to FIG. 11A , the terminal may receive configuration information from the base station. The configuration information may be received through RRC signaling, MIB, or SIB.

The configuration information may include information on the BWP, and in the present disclosure, the configuration information may include group common resource configuration information (eg, group common BWP configuration information) for group communication, and the like. As described above, the group common BWP configuration information may be set separately from the BWP configured in the terminal, or some frequency resources of the BWP configured in the terminal may be set as the group common BWP.

The UE may monitor the PDCCH in at least one search space according to the above embodiments ( 1101 ). The search space may include a common search space. The common search space may include a group search space commonly set only to a specific group i for group communication. Also, the search space may include a UE-specific search space. The UE-specific search space may include a group search space commonly configured only for a specific group i for group communication.

More specifically, the group search space commonly set only to the group i can be obtained by setting the Y _p,-1 value of Equation 1 to the group common RNTI and substituting it in Equation 1 . The terminal included in the group may monitor the PDCCH in the group search space, and information included in the DCI received in the group search space may be used for group communication of the terminal.

Alternatively, the base station may transmit information on the group search space to the terminal. The base station may configure information on the PDCCH in which the group search space is located (or to be used for group communication) to the terminal through RRC signaling or SIB. In this case, time resource information and frequency resource information for the CORESET may be directly indicated through RRC signaling, MIB, or SIB. Alternatively, the time resource information and the frequency resource information for the PDCCH indicate any one of predetermined information (eg, information configured in the form of a table) through information included in RRC signaling, MIB, or SIB. can make it In addition, the CCE index of the common search space included in the PDCCH may be determined based on Equation 1 above.

As a result of monitoring of the terminal, DCI may be detected ( 1102 ). That is, the UE may receive DCI through the PDCCH as a result of monitoring the PDCCH.

When the DCI is received, the UE may check whether the RNTI used for scrambling the CRC of the DCI transmitted through the PDCCH is the first RNTI or the second RNTI (1103). As described above, the terminal included in group i may be assigned a group common RNTI (received through higher layer signaling, MIB, or SIB), and when the group common RNTI is assigned, step 1103 may be performed. . In the present disclosure, the second RNTI may refer to a group common RNTI, and the first RNTI may refer to an RNTI other than the group common RNTI configured in the UE. Meanwhile, in the present disclosure, step 1103 may be a step of confirming whether the RNTI used for scrambling the CRC of the DCI is the second RNTI. That is, the terminal may determine whether a scrambled CRC is attached based on the group common RNTI, and may determine whether scheduling information for group communication is received based on this.

However, since the group search space is a search space commonly set only to group i based on the group common RNTI, when the terminal receives DCI in the group search space, step 1103 may be omitted and step 1105 may be performed.

If the RNTI is the first RNTI, the UE may process the PDSCH scheduled by the received DCI using the first VRB-to-PRB mapping scheme (1104). That is, the UE may check the PRB to which data is mapped based on the RB group (or bundle) divided in the frequency resource domain of the BWP allocated to the UE, and may check the data based on this. Alternatively, the UE may perform deinterleaving based on the allocated frequency resource of the BWP.

Meanwhile, when the RNTI is the second RNTI, the UE may process the PDSCH scheduled by the received DCI using the second VRB-to-PRB mapping scheme (1105). That is, a PRB to which data is mapped may be checked based on an RB group (bundle) divided according to a group common frequency resource, and data may be checked based on this. Alternatively, the UE may perform deinterleaving based on a group common frequency resource.

Meanwhile, the group search space may not be identified as a group common RNTI, and as described above, the base station may directly configure the terminal. Accordingly, the UE may monitor the PDCCH in a region configured as the group search space (1101), and may receive a DCI as a result of the PDCCH monitoring (1102). In the above embodiment, the UE may receive and use the group common RNTI defined for the UE group. Alternatively, the UE may use the RNTI configured in the UE for the group search space. In addition, the UE may receive data through the PDSCH scheduled by the DCI received through the group search space. In this case, as described above in the step of mapping the VRB to the PRB, the UE may determine the VRB based on the RBs included in the group common frequency resource and map it to the PRB. Through this method, data mapped to the PRB can be appropriately received even when the bandwidth or the size and location of the bandwidth portion are different for each terminal.

Referring to FIG. 11B , the base station may transmit configuration information to the terminal ( 1110 ). The configuration information may refer to information transmitted through RRC signaling, MIB, or SIB.

The setting information may include information on BWP, and in the present disclosure, group common BWP setting information for group communication may be included. As described above, the group common BWP configuration information may be set separately from the BWP configured in the terminal, or some frequency resources of the BWP configured in the terminal may be set as the group common BWP.

The base station may transmit control information through at least one search space according to the above embodiments ( 1111 ). The search space may include a common search space. The common search space may include a group search space commonly set only to a specific group i for group communication. Also, the search space may include a UE-specific search space. The UE-specific search space may include a group search space commonly set only to a specific group i for group communication.

More specifically, the group search space commonly set only to the group i can be obtained by setting the Y _p,-1 value of Equation 1 to the group common RNTI and substituting it in Equation 1 .

As described above, the base station may allocate a group common RNTI to the terminal included in group j (transmitting it through higher layer signaling, MIB, or SIB). Accordingly, when the base station transmits the DCI through the group search space, the base station may use the group common RNTI for scrambling the CRC of the DCI. In the present disclosure, the group common RNTI may be referred to as a second RNTI, and RNTIs other than the group common RNTI may be referred to as a first RNTI.

When the base station scrambles the DCI CRC with the first RNTI, the base station may transmit data using the first VRB-to-PRB mapping scheme ( 1112 ). That is, the base station may perform VRB-to-PRB mapping based on the RB group divided in the frequency resource region of the BWP allocated to the terminal, and may transmit data based thereon.

Meanwhile, when the base station scrambles the DCI CRC with the second RNTI, the base station may transmit data using the second VRB-to-PRB mapping scheme ( 1113 ). That is, VRB-to-PRB mapping may be performed based on an RB group divided according to a group common frequency resource, and data may be transmitted based on this.

Meanwhile, the group search space may not be identified as a group common RNTI, and as described above, the base station may directly configure the terminal. Accordingly, the base station may transmit DCI in the area set as the group search space. In the above embodiment, the base station may allocate the group common RNTI defined for the terminal group to the terminal and use it. Alternatively, the base station may use the RNTI configured in the terminal for the group search space. In addition, the base station may transmit data through the PDSCH scheduled by the DCI received through the group search space. In this case, the base station may determine the VRB based on the RBs included in the group common frequency resource as described above in the step of mapping the VRB to the PRB, and map it to the PRB. Through this method, the base station can appropriately transmit data mapped to the PRB even when the bandwidth or the size and location of the bandwidth portion are different for each terminal.

Meanwhile, according to an embodiment of the present disclosure, the UE may receive the unicast PDSCH and the group common PDSCH in one slot according to the UE capability.

According to an embodiment of the present disclosure, the base station may determine whether to schedule unicast PDSCH to a terminal belonging to the group in a slot in which a group common PDSCH is scheduled based on the UE capability of the terminal. Specific details will be described below.

Referring to FIG. 12 , an example in which a group common frequency resource 1210 is configured in the BWP 1200 of UE #1 is shown according to the embodiment.

According to the description of the above embodiment, the unicast PDSCH scheduled using the interleaving method in the VRP-to-PRB mapping method may be located in the BWP 1200 of UE #1. For example, the unicast PDSCH may be located in a spanned BWP 1200 of UE #1. Also, according to the description of the embodiment, a group common PDSCH (PDSCH) scheduled using an interleaving scheme in a VRP-to-PRB mapping scheme may be located in the group common frequency resource 1210 . For example, the group common PDSCH may be located in a spanned group common frequency resource 1210 . Accordingly, the PRB resource to which the unicast PDSCH is mapped and at least a part of the PRB resource to which the group common PDSCH is mapped may overlap.

According to an embodiment of the present disclosure, when at least a portion of the PRB resource to which the unicast PDSCH is mapped and the PRB resource to which the group common PDSCH is mapped overlap, the UE maps the unicast PDSCH to the overlap region (overlap region or overlap area) can be understood and dealt with. According to an embodiment of the present disclosure, when the PRB resource to which the unicast PDSCH is mapped and at least a part of the PRB resource to which the group common PDSCH is mapped overlap, the base station may map and transmit at least a part of the unicast PDSCH to the overlapping area. .

The base station generates a DCI including information on the overlapping region, and uses a CRC generated based on the generated DCI, for example, INT-RNTI (or may be another RNTI, for example, the group common RNTI) The scrambled PDCCH may be transmitted to UEs belonging to a group corresponding to the group common PDSCH. The DCI may be DCI format 2_1, but this is only an embodiment of the present disclosure, and another DCI format or a newly defined format may be used. Each of the terminals belonging to the group that has received the DCI through the PDCCH identifies a radio resource corresponding to the overlapping area through the DCI, and the corresponding area (resource) is the terminal (the terminal belonging to the group). It is understood that it is not a resource used for group communication for , and can be processed. Alternatively, each of the terminals belonging to the group that has received the DCI through the PDCCH identifies a radio resource corresponding to the overlapping area through the DCI, and the corresponding area (resource) is a resource used for unicast PDSCH. , can be processed.

For example, the terminal does not perform decoding (or stops decoding) on a code block mapped to the region, and a code block group including the code block or TB (transport) block) may be determined as NACK to transmit feedback on the group common PDSCH to the base station.

The frequency resource that can be indicated as the overlapping region through DCI information (eg, DCI format 2_1) includes B _INT PRBs included in the group common frequency resource or included in the group common frequency resource. It may be equal to B _INT PRBs. The time resources that can be indicated as the overlapping region through the DCI information may be OFDM symbols included in the monitoring period of the DCI.

According to an embodiment of the present disclosure, when the PRB resource to which the unicast PDSCH is mapped and at least a part of the PRB resource to which the group common PDSCH is mapped overlap, the UE understands that the group common PDSCH is mapped to the overlapping area and processes it can do. According to an embodiment of the present disclosure, when the PRB resource to which the unicast PDSCH is mapped and at least a part of the PRB resource to which the group common PDSCH is mapped overlap, the base station maps at least a part of the group common PDSCH to the overlapping area and transmits it can

The UE identifies a radio resource corresponding to an overlapping region through resource information in DCI transmitted through a PDCCH for scheduling the group common PDSCH, and the corresponding region (resource) transmits the unicast PDSCH to the UE. It is understood that it is not used for and can be processed. Alternatively, the terminal identifies a radio resource corresponding to an overlapping area through resource information in DCI transmitted through a PDCCH for scheduling the group common PDSCH, and the corresponding area (resource) is the group common to the terminal It can be understood that it is used for PDSCH transmission and can be processed.

For example, the terminal does not perform decoding (or stops decoding) on a code block mapped to the region, and a code block group including the code block or TB (transport) block) may be determined as NACK to transmit feedback on the unicast PDSCH to the base station.

According to an embodiment of the present disclosure, when the frequency resource to which the unicast PDSCH is mapped (hereinafter, the PRB resource) and at least a part of the PRB resource to which the group common PDSCH is mapped overlap, the terminal is the PDSCH scheduled by the PDCCH transmitted later It can be understood and processed as being mapped to the overlapping region. According to an embodiment of the present disclosure, when the PRB resource to which the unicast PDSCH is mapped and at least a part of the PRB resource to which the group common PDSCH is mapped overlap, the base station is at least a part of the PDSCH scheduled by the PDCCH transmitted later in the overlapping area. can be mapped and transmitted.

For example, if the PDSCH scheduled by the PDCCH transmitted later is a unicast PDSCH, the UE may understand and process the unicast PDSCH as mapped to the overlapping area, and the base station may map at least a part of the unicast PDSCH to the overlapping area. can be transmitted

The base station generates a DCI including information on the overlapping region, and uses a CRC generated based on the generated DCI, for example, INT-RNTI (or may be another RNTI, for example, the group common RNTI) The scrambled PDCCH may be transmitted to UEs belonging to a group corresponding to the group common PDSCH. The DCI may be DCI format 2_1, but this is only an embodiment of the present disclosure, and another DCI format or a newly defined format may be used. Each of the terminals belonging to the group that has received the DCI through the PDCCH identifies a radio resource corresponding to the overlapping area through the DCI, and the corresponding area (resource) is the terminal (the terminal belonging to the group). It is understood that it is not a resource used for group communication for , and can be processed. Alternatively, each of the terminals belonging to the group that has received the DCI through the PDCCH identifies a radio resource corresponding to the overlapping area through the DCI, and the corresponding area (resource) is the terminal belonging to the group. It can be understood and processed as a resource used for unicast PDSCH for UEs).

For example, the terminal does not perform decoding (or stops decoding) on a code block mapped to the region, and a code block group or TB (transport block) including the code block. ), by determining the HARQ-ACK information corresponding to NACK as NACK, feedback for the group common PDSCH may be transmitted to the base station.

Or, for example, when the PDSCH scheduled by the PDCCH transmitted later is a group common PDSCH, the UE may understand and process the group common PDSCH as mapped to the overlapping area, and the base station may process the group common PDSCH in the overlapping area. At least a part of the PDSCH may be mapped and transmitted. The UE identifies a radio resource corresponding to an overlapping region through resource information in DCI transmitted through a PDCCH for scheduling the group common PDSCH, and the corresponding region (resource) transmits the unicast PDSCH to the UE. It is understood that it is not used for and can be processed. Alternatively, the terminal identifies a radio resource corresponding to an overlapping area through resource information in DCI transmitted through a PDCCH for scheduling the group common PDSCH, and the corresponding area (resource) is the group communication to the terminal It can be understood and processed as a resource used for For example, the terminal does not perform decoding (or stops decoding) on a code block mapped to the region, and a code block group or TB (transport block) including the code block. ), the HARQ-ACK information corresponding to the NACK may be determined to transmit feedback on the unicast PDSCH to the base station.

According to an embodiment of the present disclosure, when the PRB resource to which the unicast PDSCH is mapped and at least a part of the PRB resource to which the group common PDSCH is mapped overlap, the UE treats both the unicast PDSCH and the group common PDSCH transmission as an error. can

Meanwhile, the embodiment of FIG. 12 may be implemented by combining some or all of the contents included in each embodiment within a range that does not impair the essence of the present disclosure. For example, in the present disclosure, a method of transmitting information on an overlapping region through DCI has been described as an example, but the UE may receive DCI for scheduling a group common PDSCH or unicast PDSCH, respectively, included in DCI Based on the resource allocation information, it can be checked whether the group common PDSCH and the unicast PDSCH overlap. In addition, a method of configuring resource configuration information (eg, BWP configuration information) related to the group common PDSCH and unicast PDSCH may be the same as described above.

According to an embodiment of the present disclosure, when interleaving is configured in VRB-to-PRB mapping of unicast PDSCH, the base station configures or schedules for group common PDSCH transmission to the terminal (eg, group common resource configuration or scheduling, etc.) According to an embodiment of the present disclosure, when interleaving is configured to be impossible in VRB-to-PRB mapping of unicast PDSCH, the base station configures or schedules for group common PDSCH transmission to the terminal (eg, group common resource configuration or scheduling, etc.). In this case, VRB-to-PRB mapping of the group common PDSCH may follow the above embodiments.

Therefore, according to an embodiment of the present disclosure, when group common PDSCH transmission is scheduled on slot n and unicast PDSCH transmission is scheduled on slot n for one terminal in the group, the base station is the VRB- of the unicast PDSCH. The to-PRB mapping may be mapped and transmitted in a non-interleaving manner.

According to an embodiment of the present disclosure, when VRB-to-PRB mapping of a group common PDSCH scheduled to be transmitted in slot n is non-interleaving, unicast PDSCH transmission in slot n is scheduled for one terminal in the group. In this case, the VRB-to-PRB mapping of the unicast PDSCH may be a non-interleaving method.

According to an embodiment of the present disclosure, when VRB-to-PRB mapping of a group common PDSCH scheduled to be transmitted in slot n is interleaving, the terminal belonging to the group does not expect a unicast PDSCH to be scheduled in slot n. it may not be

According to an embodiment of the present disclosure, when unicast PDSCH transmission is scheduled to terminal 1 in slot n and group common PDSCH transmission is scheduled in slot n in group A including the terminal 1, the base station performs the group common The VRB-to-PRB mapping of the PDSCH of may be mapped and transmitted in a non-interleaving manner.

According to an embodiment of the present disclosure, when VRB-to-PRB mapping of a unicast PDSCH scheduled to be transmitted to terminal 1 in slot n is non-interleaving, group A including terminal 1 is group common in slot n. PDSCH transmission may be scheduled, and in this case, VRB-to-PRB mapping of the group common PDSCH may be a non-interleaving method.

According to an embodiment of the present disclosure, when VRB-to-PRB mapping of a unicast PDSCH scheduled to be transmitted to terminal ₁ in slot n is interleaving, the base station is group common to group _A including terminal 1 in slot n It is possible to schedule the PDSCH in a different slot without scheduling the PDSCH.

Referring to FIG. 13 , the terminal may include a transceiver 1310 , a controller 1320 , and a storage 1330 . In the present invention, the controller may be defined as a circuit or an application specific integrated circuit or at least one processor.

The transceiver 1310 may transmit/receive signals to and from other network entities. The transceiver 1310 may receive, for example, group common resource configuration information from the base station, and may receive DCI through the group common PDCCH. Also, the transceiver 1310 may receive data from the base station.

The controller 1320 may control the overall operation of the terminal according to the embodiment proposed in the present invention. For example, the controller 1320 may control a signal flow between blocks to perform an operation according to the above-described flowchart. For example, the controller 1320 may check whether the received DCI CRC is scrambled based on the group common RNTI. In addition, when the DCI CRC is scrambled based on the group common RNTI, the controller 1320 may perform deinterleaving based on the group common frequency resource. Also, when the CRC of the DCI is scrambled based on an RNTI other than the group common RNTI, the controller 1320 may perform deinterleaving based on the frequency resource of the BWP configured in the terminal. In addition, when the group common PDSCH overlaps with a unicast PDSCH scheduled for unicast communication, the controller 1320 may prioritize one of the group common PDSCH and unicast PDSCH according to a predetermined method. In addition, when interleaving is configured for a physical resource block (PRB) mapping of a unicast PDSCH, the controller 1320 may not expect a group common PDSCH to be scheduled. Alternatively, when interleaving is set to be impossible for a physical resource block (PRB) mapping of a unicast PDSCH, the controller 1320 can expect a group common PDSCH to be scheduled. In addition, the operation of the terminal described above may be controlled by the controller 1320 , and detailed description thereof will be omitted.

The storage unit 1330 may store at least one of information transmitted/received through the transceiver 1310 and information generated through the control unit 1320 .

Referring to FIG. 14 , the base station may include a transceiver 1410 , a controller 1420 , and a storage 1430 . In the present invention, the controller may be defined as a circuit or an application specific integrated circuit or at least one processor.

The transceiver 1410 may transmit/receive signals to and from other network entities. The transceiver 1410 may transmit group common resource configuration information to the terminal, and may transmit DCI through the group common PDCCH. Also, the transceiver 1410 may transmit data to the terminal.

The controller 1420 may control the overall operation of the base station according to the embodiment proposed in the present invention. For example, the controller 1420 may control a signal flow between blocks to perform an operation according to the above-described flowchart. For example, the controller 1420 may scramble and transmit the DCI CRC based on the group common RNTI according to an embodiment of the present disclosure. In addition, when the DCI CRC is scrambled based on the group common RNTI, the controller 1420 may perform interleaving based on the group common frequency resource. Also, when the DCI CRC is scrambled based on an RNTI other than the group common RNTI, the controller 1420 may perform interleaving based on the frequency resource of the BWP configured in the UE. In addition, when the group common PDSCH overlaps with a unicast PDSCH scheduled for unicast communication, the controller 1420 may preferentially transmit either the group common PDSCH or the unicast PDSCH according to a predetermined method. In addition, when interleaving is configured for a physical resource block (PRB) mapping of a unicast PDSCH, the controller 1420 may not schedule the group common PDSCH. Alternatively, the controller 1420 may schedule a group common PDSCH when interleaving is set to be impossible for a physical resource block (PRB) mapping of a unicast PDSCH. In addition, the above-described operation of the base station may be controlled by the controller 1420, and detailed description thereof will be omitted.

The storage unit 1430 may store at least one of information transmitted/received through the transceiver 1410 and information generated through the control unit 1420 .

Accordingly, according to various embodiments of the present disclosure, in a method performed by a terminal in a communication system, the method comprising: receiving configuration information for a group common resource from a base station; receiving downlink control information (DCI) from the base station based on the configuration information; checking whether a group common radio network temporary identifier (RNTI) is used for scrambling of a cyclic redundancy check (CRC) attached to the DCI; and performing deinterleaving based on a resource block (RB) group divided based on a group common frequency resource when the group common RNTI is used.

On the other hand, in the drawings for explaining the method of the present invention, the order of description does not necessarily correspond to the order of execution, and the precedence relationship may be changed or may be executed in parallel.

Alternatively, some components may be omitted and only some components may be included in the drawings for explaining the method of the present invention without impairing the essence of the present invention.

In addition, the method of the present invention may be implemented in a combination of some or all of the contents included in each embodiment within a range that does not impair the essence of the invention.

Claims

A method performed by a terminal in a communication system, comprising:

Receiving configuration information for a group common resource from the base station;

receiving downlink control information (DCI) from the base station based on the configuration information;

checking whether a group common radio network temporary identifier (RNTI) is used for scrambling of a cyclic redundancy check (CRC) attached to the DCI; and

and performing deinterleaving based on a resource block (RB) group divided based on a group common frequency resource when the group common RNTI is used.
According to claim 1,

When the group common RNTI is not used, the method further comprising the step of performing deinterleaving based on the RB group divided based on the frequency resource of the bandwidth portion set in the terminal.
According to claim 1,

When the group common RNTI is used, the DCI includes information for scheduling a group common physical downlink shared channel (PDSCH),

When the group common PDSCH overlaps with a unicast PDSCH scheduled for unicast communication, one of the group common PDSCH and unicast PDSCH is preferentially processed according to a predetermined method.
According to claim 1,

When interleaving is set to enable interleaving for PRB (physical resource block) mapping of unicast PDSCH, a method characterized in that the group common PDSCH is not scheduled.
A method performed by a base station in a communication system, comprising:

transmitting configuration information for a group common resource to the terminal;

transmitting downlink control information (DCI) based on the configuration information;

When a group common radio network temporary identifier (RNTI) is used for scrambling of a cyclic redundancy check (CRC) attached to the DCI, interleaving is performed based on a resource block (RB) group divided based on a group common frequency resource. A method comprising the steps of.
6. The method of claim 5,

When the group common RNTI is not used, the method further comprising the step of performing interleaving based on the RB group divided based on the frequency resource of the bandwidth portion configured in the terminal.
6. The method of claim 5,

When the group common RNTI is used, the DCI includes information for scheduling a group common physical downlink shared channel (PDSCH),

When the group common PDSCH overlaps with a unicast PDSCH scheduled for unicast communication, one of the group common PDSCH or unicast PDSCH is preferentially processed according to a predetermined method.
6. The method of claim 5,

When interleaving is set to enable interleaving for PRB (physical resource block) mapping of unicast PDSCH, a method characterized in that the group common PDSCH is not scheduled.
In a terminal in a communication system,

transceiver; and

connected to the transceiver,

Receive configuration information for group common resources from the base station,

Receive downlink control information (DCI) from the base station based on the configuration information,

Check whether a group common radio network temporary identifier (RNTI) is used for scrambling of a cyclic redundancy check (CRC) attached to the DCI,

and a controller configured to perform deinterleaving based on a resource block (RB) group divided based on a group common frequency resource when the group common RNTI is used.
10. The method of claim 9,

The control unit is

When the group common RNTI is not used, deinterleaving is performed based on an RB group divided based on a frequency resource of a bandwidth portion configured in the terminal.
10. The method of claim 9,

When the group common RNTI is used, the DCI includes information for scheduling a group common physical downlink shared channel (PDSCH),

When the group common PDSCH overlaps with a unicast PDSCH scheduled for unicast communication, one of the group common PDSCH and unicast PDSCH is preferentially processed according to a predetermined method.
10. The method of claim 9,

When interleaving is set to enable interleaving for PRB (physical resource block) mapping of unicast PDSCH, a group common PDSCH is not scheduled.
In a base station in a communication system,

transceiver; and

connected to the transceiver,

Transmitting configuration information for group common resources to the terminal,

Transmitting downlink control information (DCI) based on the configuration information,

When a group common radio network temporary identifier (RNTI) is used for scrambling of a cyclic redundancy check (CRC) attached to the DCI, interleaving is performed based on a resource block (RB) group divided based on a group common frequency resource. A base station comprising a control unit.
14. The method of claim 13,

The control unit is

When the group common RNTI is not used, the base station, characterized in that interleaving is performed based on the RB group divided based on the frequency resource of the bandwidth part configured in the terminal.
14. The method of claim 13,

When the group common RNTI is used, the DCI includes information for scheduling a group common physical downlink shared channel (PDSCH),

When the group common PDSCH overlaps with a unicast PDSCH scheduled for unicast communication, one of the group common PDSCH or unicast PDSCH is prioritized and processed according to a predetermined method,

When interleaving is set to enable interleaving for PRB (physical resource block) mapping of unicast PDSCH, the base station, characterized in that the group common PDSCH is not scheduled.