KR102364058B1 - Method and apparatus for handling collisions in next-generation communication systems - Google Patents

Abstract

A communication method and system for convergence of a 5th generation (5G) communication system supporting a data rate higher than that of a 4th generation (4G) system using Internet of Things (IOT) technology are provided. The system can be applied to intelligent services based on 5G communication technology and IoT-related technologies, such as smart home, smart building, smart city, smart car, connected car, healthcare, digital education, smart retail, security and safety services. The method includes receiving, from a base station, scheduling information for a first uplink packet transmission in a first time slot, wherein the first uplink packet transmission in the first time slot is second uplink in a first time slot of another terminal. determining whether the transmission is restricted based on information corresponding to the link packet transmission, and if the transmission of the first uplink packet in the first time slot is restricted, skipping the transmission of the first uplink packet in the first time slot. includes steps.

Description

Method and apparatus for handling collisions in next-generation communication systems

The present disclosure relates to a method and apparatus for handling collision in a next-generation communication system. In particular, the present disclosure relates to a method and apparatus for channel quality measurement and terminal signal transmission based on coexistence between different systems based on cellular communication using an authorized shared band.

Efforts have been made to develop an improved 5G or pre-5G communication system to meet the demand for increased wireless data traffic after deployment of the 4G communication system. Therefore, the 5G or pre-5G communication system is also referred to as 'Beyond 4G Network' or 'Post LTE'.

The 5G communication system is considered to be implemented in a high frequency (mmWave) band, for example, a 60 GHz band to achieve higher data rates. In order to reduce the propagation loss of radio waves and increase the transmission distance, beamforming, mass MIMO, FD-MIMO, array antenna, analog beamforming, and large-scale antenna technologies are discussed in the 5G communication system.

In addition, in the 5G communication system, advanced (advanced) small cell, cloud radio access network (RAN), ultra-dense network (ultra-dense network), D2D (device-to-device) communication, wireless backhaul, mobile network, cooperative communication , Coordinated Multi-Point (CoMP), and reception end interference cancellation, etc. are being developed to improve the system network. In the 5G system, hybrid FSK and QAM Modulation (FQAM) as advanced coding modulation (ACM), and filter bank multi carrier (FBMC), non-orthogonal multiple access (NOMA) and sparse code multiple access (SCMA) as advanced access technologies are was developed

The Internet, a human-centered, connected network in which humans generate and consume information, is now evolving into the Internet of Things (IoT), in which distributed entities such as things exchange and process information without human intervention. The Internet of Everything (IoE), a combination of IoT technology and Big Data processing technology, has emerged through connection with a cloud server. As technology elements such as “sensing technology”, “wired/wireless communication and network infrastructure”, “service interface technology” and “security technology” are required for IoT implementation, sensor networks, machine-to-machine (M2M) communication , MTC (Machine Type Communication), etc. have been studied recently. Such an IoT environment can provide intelligent Internet technology services that create new values in human life by collecting and analyzing data generated between connected objects. IoT is a smart home, smart building, smart city, smart car or connected car, smart grid, health It can be applied to various fields including care, smart home appliances, and advanced medical services.

Accordingly, various attempts have been made to apply the 5G communication system to the IoT network. For example, technologies such as sensor networks, Machine Type Communication (MTC) and Machine-to-Machine (M2M) communication may be implemented by beamforming, MIMO, and array antennas. The application of the above-described cloud radio access network (RAN) as a big data processing technology can also be considered as an example of convergence between 5G technology and IoT technology.

Compared to the existing 4G system, the 5G system is expected to support more diverse services. For example, representative services include enhanced mobile broad band (eMBB), ultra-reliable and low latency communication (URLLC), massive machine type communication (mMTC), and evolved multimedia broadcast/multicast service (eMBMS). A system providing a URLLC service may be referred to as a URLLC system, a system providing an eMBB service may be referred to as an eMMB system, and a system providing an mMTC service may be referred to as an mMTC system. The terms "service" and "system" may be used interchangeably.

The above information is provided as background information to aid in understanding the present disclosure. No determination has been made, and no claim has been made as to which of the foregoing may apply as prior art with respect to the present disclosure.

It is an aspect of the present disclosure to solve at least the problems and/or disadvantages described above, and to provide at least the advantages described below. Accordingly, an aspect of the present disclosure is to provide a method for handling packet collisions in a next-generation communication system.

Another aspect of the present disclosure is to provide a method and apparatus for channel quality measurement and terminal signal transmission based on coexistence between different systems based on cellular communication using an authorized shared band.

According to an aspect of the present disclosure, a communication method of a terminal is provided. The method includes receiving, from a base station, scheduling information for a first uplink packet transmission in a first time slot, wherein the first uplink packet transmission in the first time slot is second uplink in a first time slot of another terminal. determining whether the transmission is restricted based on information corresponding to the link packet transmission, and if the transmission of the first uplink packet in the first time slot is limited, skipping the transmission of the first uplink packet in the first time slot ( skip) step.

The method further includes receiving, from the base station, information corresponding to a second uplink packet transmission in a first time slot of another terminal in a second time slot preceding the first time slot.

In the method, the information corresponding to the second uplink packet transmission in the first time slot of the other terminal includes an indication indicating that the terminal skips the first uplink packet transmission in the first time slot.

In the method, the information corresponding to the second uplink packet transmission in the first time slot of the other terminal includes information indicating that the first time slot is scheduled for the second uplink packet transmission of the other terminal.

According to an aspect of the present disclosure, a communication method of a base station is provided. The method includes transmitting first scheduling information for a first uplink packet transmission in a first time slot to a first terminal, sending second scheduling information for a second uplink packet transmission in a first time slot to a second transmitting to the terminal, determining whether the transmission of the first uplink packet in the first time slot is restricted based on the second scheduling information; if the transmission of the first uplink packet in the first time slot is restricted, the second receiving a second uplink packet transmission in the first time slot from the second terminal.

In the method, further comprising: transmitting information corresponding to a second uplink packet transmission in a first time slot of a second terminal to the first terminal in a second time slot preceding the first time slot, a second The information corresponding to the second uplink packet transmission in the first time slot of the terminal includes an indication indicating that the first terminal skips the first uplink packet transmission in the first time slot.

In the method, further comprising: transmitting, in the broadcast signal, information corresponding to a second uplink packet transmission in a first time slot of the second terminal to the first terminal, in the first time slot of the second terminal The information corresponding to the second uplink packet transmission includes information indicating that the first time slot is scheduled for the second uplink packet transmission of the second terminal.

According to an aspect of the present disclosure, a terminal is provided. The terminal receives scheduling information for transmission of a first uplink packet in a first time slot from a transceiver configured to transmit and receive a signal, and a base station, wherein the transmission of the first uplink packet in the first time slot is a first of another terminal determine whether the first uplink packet transmission in the first time slot is restricted based on information corresponding to the second uplink packet transmission in the time slot; and at least one processor configured to skip packet transmission.

According to an aspect of the present disclosure, a base station is provided. The base station transmits to the first terminal a transceiver configured to transmit and receive a signal, and first scheduling information for a first uplink packet transmission in a first time slot, and a second uplink packet transmission method in the first time slot. transmit the second scheduling information to the second terminal, determine whether the first uplink packet transmission in the first time slot is limited based on the second scheduling information, and transmit the first uplink packet in the first time slot if constrained, comprising at least one processor configured to receive a second uplink packet transmission in the first time slot from the second terminal.

It is an aspect of the present disclosure that it is possible to provide a method and apparatus for handling packet collisions in a next-generation communication system.

Other aspects, advantages and salient features of the present disclosure will become apparent to those skilled in the art from the following detailed description taken in conjunction with the accompanying drawings, which discloses various embodiments of the present disclosure.

1 illustrates an operation of handling a conflict according to an embodiment of the present disclosure;
2 illustrates a message flow between a user equipment (UE) and a 5G NodeB/base station (gNB/BS) for collision handling in case of dynamic scheduling according to an embodiment of the present disclosure;
3 illustrates a message flow between a UE and a gNB/BS for collision handling in case of dynamic scheduling according to an embodiment of the present disclosure.
4 illustrates a conflict handling operation according to an embodiment of the present disclosure.
5 illustrates a message flow between a UE and gNB/BS for collision handling in the case of semi-persistently scheduled (SPS) according to an embodiment of the present disclosure.
6 illustrates a conflict handling operation according to an embodiment of the present disclosure.
7 illustrates a message flow between a UE and a gNB/BS for collision handling in case of dynamic scheduling according to an embodiment of the present disclosure.
8 illustrates a message flow between a UE and a gNB/BS for collision handling in the case of SPS according to an embodiment of the present disclosure.
9 illustrates a conflict handling operation according to an embodiment of the present disclosure.
10 illustrates a collision handling operation in a downlink according to an embodiment of the present disclosure.
11 illustrates a collision handling operation in a downlink according to an embodiment of the present disclosure.
12 illustrates an indication method according to an embodiment of the present disclosure.
13 illustrates a message flow between a UE and a gNB/BS for collision handling in case of dynamic scheduling according to an embodiment of the present disclosure.
14 illustrates a collision processing operation between a channel state information reference signal (CSI-RS) and ultra-reliable and low latency communication (URLLC) according to an embodiment of the present disclosure.
15 is a block diagram of a user device according to an embodiment of the present disclosure.
16 is a block diagram of a base station according to an embodiment of the present disclosure.
It should be noted that throughout the drawings, the same reference numbers are used to refer to the same or similar elements, features, and structures.

The following description with reference to the accompanying drawings is provided to provide a comprehensive understanding of the various embodiments of the present disclosure as defined by the claims and their equivalents. It includes various specific details to aid in that understanding, but it should be considered as illustrative only. Accordingly, those skilled in the art will recognize that various changes and modifications of the various embodiments described herein can be made without departing from the scope and spirit of the present disclosure. In addition, descriptions of well-known functions and configurations may be omitted for the sake of clarity and conciseness.

The terms and words used in the following description and claims are not limited to the meaning of the bibliography, but are used only to enable the inventor to have a clear and consistent understanding of the present disclosure. Accordingly, it will be apparent to those skilled in the art that the following description of various embodiments of the present disclosure is provided for illustrative purposes only, and not to limit the present disclosure as defined by the appended claims and their equivalents. Should be.

It should be understood that the singular forms "a", "an" and "the" include the plural object unless the context clearly dictates otherwise. Thus, for example, reference to “a component surface” includes reference to one or more of such surfaces.

The term "substantially" means that the recited characteristic, parameter or value need not be precisely achieved, but that deviations or variations including, for example, tolerances, measurement errors, limits of measurement accuracy, and other factors known to those skilled in the art are subject to change. This means that it can occur to a degree that does not exclude the effect to be provided.

In the drawings, some elements are exaggerated, omitted, or simply summarized, and thus may not be drawn to scale. The same or similar reference symbols are used throughout the drawings to refer to the same or similar parts.

On the other hand, it is known to those skilled in the art that blocks of a flowchart (or sequence diagram) and combinations of flowcharts may be represented and executed by computer program instructions. These computer program instructions may be loaded onto the processor of a general purpose computer, special purpose computer, or programmable data processing device. When the loaded program instructions are executed by the processor, they create means for performing the functions described in the flowcharts. Since the computer program instructions may be stored in a computer readable memory usable in a specialized computer or programmable data processing device, it is also possible to create a product that performs the functions described in the flowcharts. Since computer program instructions may be loaded onto a computer or programmable data processing device, when executed as a process, it may perform the operations of the functions described in the flowcharts.

A block in a flowchart may correspond to a module, segment, or code, or portion thereof, comprising one or more executable instructions that implement one or more logical functions. In some cases, functions described as blocks may be executed in an order different from the order in which they are listed. For example, two blocks listed in a sequence may be executed concurrently or in reverse order.

In the description, words such as "unit", "module", etc. may refer to software components or hardware components, such as field-programmable gate arrays (FPGAs), or application specific integrated circuits (ASICs) capable of executing functions or operations. can However, "unit" and the like are not limited to hardware or software. A unit or the like may reside on an addressable storage medium or may be configured to drive one or more processors. Units include software components, object-oriented software components, class components, task components, processes, functions, properties, procedures, subroutines, program code segments, drivers, firmware, microcode, circuits, data, databases, data It may refer to a structure, table, array, or variable. The functions provided by the components and units may be a combination of smaller components and units, and may be combined with other components to form larger components and units. The components and units may be configured to drive one or more processors or devices in a secure multimedia card. A component or unit may include one or more processors.

Prior to the detailed description, terms or definitions necessary for understanding the present disclosure are set forth. However, these terms should be interpreted in a non-limiting manner.

A "base station" (BS) is an entity that communicates with user equipment, and is an entity that communicates with a BS, a base transceiver station (BTS), a NodeB (NB), an eNodeB (eNB), an access point (AP) or a 5G NodeB (gNB). ). A “user equipment” (UE) is an entity that communicates with a base station and may be referred to as a UE, device, mobile station (MS), mobile equipment (ME), or terminal. The symbol refers to an orthogonal frequency-division multiplexing (OFDM) symbol in the description.

In recent years, several broadband wireless technologies have been developed to meet more and more broadband subscribers and provide more and better applications and services. The second-generation wireless communication system was developed to provide a voice service while guaranteeing user mobility. The 3G wireless communication system supports not only voice service but also data service. Recently, 4G wireless communication systems have been developed to provide high-speed data services. However, at present, the 4G wireless communication system lacks resources to meet the increasing demand for high-speed data services. Therefore, 5G wireless communication systems are being developed to meet the increasing demand for high-speed data services, support ultra-reliable and low-latency applications, and support large-scale MTC.

For uplink (UL) packet transmission, (UE, terminal) (eg, UE1) sends a scheduling control channel (eg, physical downlink common control channel) in time slot (eg, subframe) N It is the first allocated resource using a physical downlink common control channel (PDCCH)), and the UE (UE1) transmits using the allocated resource in time slot N+P. The value of 'P' is different for different types of services/packets. In the case of an enhanced mobile broad band (eMBB) service/packet, 'P' is greater than an ultra-low latency (URLL) (eg, ultra-reliable and low latency communication (URLLC)) service/packet. To support low latency, 'P' is smaller for URLLC packets. This may result in collisions between URLLC and eMBB packet transmissions from different UEs (eg UE1 and UE3).

In another scenario, the UE (eg, UE2) may be allocated an SPS resource. The allocated SPS resource occurs periodically at every SPS interval. In this case, URLLC packet resources allocated to another UE (eg, UE3) using dynamic scheduling may collide with SPS resources.

Therefore, there is a need for a method for handling packet collisions.

UL's Collision Handling

Method 1:

1 illustrates a conflict handling operation according to an embodiment of the present disclosure;

Referring to FIG. 1 , in method 1, a URLLC packet 135 scheduled in a time slot (eg, subframe) 'X' (eg, N+4 subframe) 130 is one or more eMBB packets. (131, 133), skip the UL transmission of the URLLC symbol (ie, eMBB packet) in time slot 'X' 130 or UL packet transmission in time slot 'X' 130 (ie, eMBB packet) gNB / BS (base station) to drop (drop) the indication (eg, skip indication or pre-emption indication) 150 time slot 'X-P' (P > 0) (eg, N+3 subframes) to eMBB UEs (eg, UE1 and UE2) in 120 (broadcast or dedicated manner). UE (i.e., UE1 and/or UE2) skips UL transmission (i.e., eMBB packet) in a URLLC symbol that overlaps with UL packet transmission, or UE (i.e., UE1 and/or UE2) overlaps with URLLC symbol Drop UL packet transmission (ie eMBB packet). In an embodiment of the present disclosure, if the number of conflicting symbols exceeds a threshold, the UE (ie, UE1 and/or UE2) skips the entire packet transmission, otherwise it skips only the transmission in the conflicting symbols. The threshold may be signaled by the gNB/BS in indication 150 and/or in broadcast and/or dedicated signaling.

In an embodiment of the present disclosure, 'P' may be a unit of a symbol and/or a subframe and/or a time slot. In an embodiment of the present disclosure, information of 'P' may be broadcast and/or explicitly indicated in RRC signaling. In an alternative embodiment, 'P' may be at a fixed offset from time slot 'X' 130 in which the UL (uplink) eMBB packet is transmitted. In an embodiment of the present disclosure, the gNB/BS may configure the UE to monitor the indication (ie, skip indication or preemption indication) 150 in the time slot 'X-P' 120 . This may be determined by UE capabilities. In one embodiment of the present disclosure, the UE sends an indication 150 from the time slot 110 in which the UL packet is scheduled (ie, the PDCCH scheduling packet is received) to the time slot 130 in which the UL packet is scheduled to be transmitted. monitor for The gNB/BS may configure the UE to monitor the indication (ie, skip or preempt indication) 150 . In another embodiment of the present disclosure, the UE monitors for an indication 150 within a time interval including the 'X1' slot prior to the time slot in which the UL packet is scheduled to be transmitted. 'X1' may be signaled by gNB/BS or predefined. The gNB/BS may configure the UE to monitor the indication (ie, skip or preempt indication) 150 .

In an embodiment of the present disclosure, one or more time slots 'X' 130 may be explicitly indicated in the indication 150 . In an alternative embodiment of the present disclosure, the one or more time slots 'X' 130 may be at a fixed offset from the time slot 120 in which the indication 150 is transmitted by the gNB/BS.

In an embodiment of the present disclosure, one or more URLLC symbols skipped in one or more time slots 'X' 130 may be explicitly indicated in indication 150 by the gNB/BS. In an alternative embodiment of the present disclosure, one or more URLLC symbols may be predefined. In another embodiment of the present disclosure, one or more URLL symbols may be broadcast as system information by the gNB/BS.

In an embodiment of the present disclosure, the indication 150 may be signaled in a broadcast or dedicated manner. In the case of dedicated signaling, the indication 150 may be addressed to the UE's C-RNTI. For example, if only the scheduled resource for UE1 and the scheduled resource for UE3 overlap, and the scheduled resource for UE2 and the scheduled resource for UE3 do not overlap, the indication 150 indicates UE1's C- It can be addressed with an RNTI. Depending on whether the collision involves one or multiple UEs, an appropriate signaling method may be used by the gNB/BS. In the case of broadcast signaling, the indication 150 may be addressed as a broadcast RNTI. Alternatively, in the case of broadcast signaling, the indication 150 may be addressed with a new RNTI (eg, skip-RNTI). A UE scheduling a UL packet (and/or a UL packet (eg, eMBB) having a lower priority compared to other packets (eg, URLLC)) monitors only the indication 150 addressed with skip-RNTI can do. In an embodiment of the present disclosure, the indication 150 is a medium access control (MAC) control element (CE) or downlink control information (DCI) in a PDCCH included in an RRC message or a DL MAC packet data unit (PDU). Or it may be a group common DCI in the PDCCH. In an embodiment of the present disclosure, the group common DCI for the skip indication may be transmitted separately from the group common DCI for the slot format indication. In an embodiment of the present disclosure, control resource set (CORESET) information for monitoring group common DCI for skip indication may be signaled in system information or RRC signaling. In an embodiment of the present disclosure, a monitoring interval for monitoring group common DCI for skip indication may be signaled in system information or RRC signaling. In an embodiment of the present disclosure, the indication 150 may also be signaled using a broadcast channel (BCH).

Referring to FIG. 1 , an example of handling conflicts using method 1 is shown. 1 , the gNB schedules UE1 and UE2 in subframe N+4 130 by transmitting scheduling control information (ie, PDCCH) 115 in subframe N 110 (eg, , uplink eMBB packet transmission (131, 133)). There is an urgent need to schedule UE3 (eg URLLC service) later. UE3 is scheduled in the same subframe N+4 130 by transmitting scheduling control information (ie, PDCCH) 125 in subframe N+3 120 . In this case, gNB/BS knows that it has already scheduled UE1 and UE2 in subframe N+4 130 . To avoid conflicts, URLLC services are prioritized over eMBB services. gNB/BS indicates UE1 and UE2 before subframe N+4 130 to skip transmission (of uplink eMBB packet) of URLLC symbols 135 in SF (subframe) N+4 130 cation 150 is transmitted. Alternatively, the gNB/BS transmits the indication 150 before subframe N+4 130 indicating UE1 and UE2 to drop the UL packet transmission in SF N+4 130 .

2 illustrates a message flow between a UE and a gNB/BS for collision handling in case of dynamic scheduling according to an embodiment of the present disclosure.

Referring to FIG. 2 , in operation 250 , the gNB/BS 210 determines scheduling of UE1 220 for uplink eMBB packet transmission, and determines packet scheduling information for UE1 220 . In operation 255 , UE1 220 first schedules the eMBB packet by scheduling the control information transmitted by gNB/BS 210 in subframe N1 . At operation 260 , UE1 220 prepares an uplink eMBB packet for transmission.

In operation 265 , gNB/BS 210 determines scheduling of UE3 230 for URLLC packet transmission, and determines packet scheduling information for UE3 230 . In operation 270 , UE3 230 schedules a URLLC packet in SF X by scheduling the control information transmitted by gNB/BS 210 in subframe N2 , where N2>N1 .

In operation 275 , the gNB/BS 210 determines whether to transmit the skip indication 150 to the UE1 220 . In operation 280 , skip indication 150 is transmitted from gNB/BS 210 to UE1 220 in subframe N3 , where the eMBB packet scheduled to UE1 220 and scheduling to UE3 230 . If there is a collision between the URLLC packets, N3>N2.

If skip indication 150 is received by UE1 220 , in operation 285 , UE1 220 determines whether skip indication 150 corresponds to its UL packet transmission. If UE1 220 is applicable to its UL packet transmission, in operation 290 , UE1 220 skips the UL transmission in the URLLC symbol or drops the UL packet transmission. Skip indication 150 is applicable to UE1 220 , and skip indication 150 is addressed to UE1 220 and/or its UL packet transmission collides with a URLLC symbol.

3 illustrates a message flow between a UE and a gNB/BS for collision handling in case of dynamic scheduling according to an embodiment of the present disclosure.

Referring to FIG. 3 , this is the same as in FIG. 2 , except that the skip indication 150 is transmitted in the same subframe N3 as N3 is N2.

At operation 310 , the gNB/BS 210 determines scheduling of UE1 220 for uplink eMBB packet transmission, and determines packet scheduling information for UE1 220 . In operation 320 , UE1 220 first schedules the eMBB packet in SF X by scheduling the control information transmitted by gNB/BS 210 in subframe N1 . In operation 330 , UE1 220 prepares an uplink eMBB packet for transmission.

In operation 340 , gNB/BS 210 determines scheduling of UE3 230 for URLLC packet transmission, and determines packet scheduling information for UE3 230 . The gNB/BS 210 determines whether to transmit the skip indication 150 to the UE1 220 .

In operation 355 , UE3 230 schedules the URLLC packet in SF X by scheduling the control information transmitted by gNB/BS 210 in subframe N2 where N2>N1. In operation 350 , skip indication 150 is transmitted from gNB/BS 210 to UE1 220 in subframe N3 , where the eMBB packet scheduled to UE1 220 and scheduling to UE3 230 . If there is a collision between the URLLC packets, N3 = N2.

If skip indication 150 is received by UE1 220 , in operation 360 , UE1 220 determines whether skip indication 150 corresponds to its UL packet transmission. If UE1 220 is applicable to its UL packet transmission, in operation 370 , UE1 220 skips the UL transmission in the URLLC symbol or drops the UL packet transmission. Skip indication 150 is applicable to UE1 220 , and skip indication 150 is addressed to UE1 220 and/or its UL packet transmission collides with a URLLC symbol.

4 shows a collision handling operation according to an embodiment of the present disclosure, and FIG. 5 shows a message flow between a UE and a gNB/BS for collision handling in the case of SPS according to an embodiment of the present disclosure.

Referring to FIG. 4 , SPS resources 415 and 417 may be allocated to a UE (eg, UE1) 220 . The allocated SPS resources 415 and 417 occur periodically at every SPS interval 410 . There is an urgent need to schedule UE3 230 (eg, URLLC service). Accordingly, scheduling is performed in the same subframe N+4 430 by transmitting scheduling control information (ie, PDCCH) 425 in subframe N+3 420 . URLLC packet resource 417 allocated to another UE (eg UE3) 230 using dynamic scheduling may collide with SPS resource 417 .

In this case, if the URLLC packet 435 scheduled in the time slot (eg, subframe) 'X' (eg, N+4 subframe) 430 overlaps with one or more SPS resources 417 , , to skip UL transmission of a URLLC symbol in time slot 'X' 430 or drop UL packet transmission in time slot 'X' 430, gNB/BS 210 sends an indication (eg, skip in ) 450 (broadcast or dedicated manner) to UE1 220 in time slot 'X-P' (P>0) (eg, N+3 subframe) 420 . UE1 220 skips UL transmissions in URLLC symbols that overlap with UL packet transmissions, or UE1 220 drops UL packet transmissions if overlapping URLLC symbols. The indication 450 is almost the same as the above-described example.

Referring to FIG. 5 , in operation 510 , UE1 220 first schedules SPS resource activation by gNB/BS 210 . In an embodiment of the present disclosure, UE1 220 schedules SPS resource activation in SF X by scheduling control information transmitted by gNB/BS 210 in subframe N1. In operation 520 , UE1 220 prepares and transmits an uplink packet in the SPS resource scheduled by gNB/BS 210 . UE1 220 monitors for skip indication 450 . The skip indication 450 may exist only in a subframe designated before the SPS subframe.

In operation 530 , gNB/BS 210 determines scheduling of UE3 230 for URLLC packet transmission, and determines packet scheduling information for UE3 230 . In operation 540 , UE3 230 schedules the URLLC packet in SF X by scheduling the control information transmitted by gNB/BS 210 in subframe N2 . In one embodiment of the present disclosure, N2 is greater than N1.

In operation 550 , the gNB/BS 210 determines whether to transmit the skip indication 450 to the UE1 220 . In an embodiment of the present disclosure, the gNB/BS 210 determines the scheduling of the UE3 230 for transmitting the URLLC packet, and determines whether to transmit the skip indication 450 to the UE1 220 at the same time.

In operation 560 , if there is a conflict between the SPS resource scheduled to UE1 220 and the URLLC packet scheduled to UE3 230 , the skip indication 450 is sent to UE1 from gNB/BS 210 in subframe N3. is sent to 220 . In an embodiment of the present disclosure, N3 is greater than or equal to N2. For example, the gNB/BS 210 transmits scheduling information of a URLLC packet to UE3 and simultaneously transmits a skip indication 450 .

If skip indication 450 is received by UE1 220 , in operation 570 , UE1 220 determines whether skip indication 450 corresponds to its UL packet transmission. If UE1 220 is applicable to its UL packet transmission, in operation 580 , UE1 220 skips the UL transmission in the URLLC symbol or drops the UL packet transmission. Skip indication 450 is applicable to UE1 220 , and skip indication 450 is addressed to UE1 220 and/or its UL packet transmission collides with a URLLC symbol.

In one embodiment, it may be signaled by the gNB/BS 210 whether the UE should apply a skip/drop rule for a scheduled UL packet. Only when this is signaled, the UE skips and drops based on the skip indication 150 , 450 .

1. Whether the UE should apply the skip rule or process the skip indication may be indicated in dedicated signaling.

2. Whether the UE should apply the skip rule or process the skip indication may be specified for each logical channel or logical channel group (LCG). Scheduling information may be specific to a logical channel or an LCG. Accordingly, the UE applies a skip rule or processes a skip indication for a UL packet of an allowed logical channel or LCG.

3. Whether to apply a skip rule or process a skip indication may be specified for each radio access network (RAN) slice.

4. The scheduling information may have a packet type. Whether to apply the skip rule or process the skip indication may be applied to a specific packet type. Accordingly, the UE applies a skip rule or processes a skip indication for an UL packet of an allowed packet type.

In an embodiment of the present disclosure, the skip indications 150 and 450 may be named as URLLC usage indications or overlap indications. The gNB/BS 210 transmits (in a broadcast or dedicated manner) an indication that the UL URLLC symbol in time slot 'X' is used. The UE skips the UL transmission in a URLLC symbol that overlaps its UL packet transmission, or the UE drops the UL packet transmission if it overlaps the URLLC symbol. In an embodiment of the present disclosure, one or more time slots 'X' may be explicitly indicated in indications 150 and 450 . In an alternative embodiment of the present disclosure, the one or more time slots 'X' may be at a fixed offset from the time slot in which the indications 150 , 450 are transmitted by the gNB/BS 210 . In an embodiment of the present disclosure, one or more URLLC symbols used in one or more time slots 'X' may be explicitly indicated in indications 150 , 450 by gNB/BS 210 . In an alternative embodiment of the present disclosure, one or more URLLC symbols may be predefined. In another embodiment of the present disclosure, one or more URLLC symbols may be broadcast by the gNB/BS 210 as system information.

Method 2

6 illustrates a conflict handling operation according to an embodiment of the present disclosure.

Referring to FIG. 6 , in method 2, time slot X 630 is a URLLC time slot or a time slot with a URLLC symbol, and UL packets 631 and 633 are transmitted to UEs (UE1 and/or When the resources scheduled for UE2) and allocated to the UL packets 631 and 633 overlap with the URLLC resource 635 , the UE (eg, UE1 and/or UE2) has time slot X (eg, N +4 subframe) 630 skip transmission in one or more URLLC symbols 635 . In an embodiment of the present disclosure, one or more URLLC time slots 630 are signaled by the gNB/BS in broadcast signaling. In an embodiment of the present disclosure, one or more URLLC symbols 635 within a URLLC time slot 630 may be predefined in the system. Alternatively, one or more URLLC symbols 635 within a URLLC time slot 630 may also be signaled by the gNB/BS in broadcast signaling. Frequency resources within the URLLC symbol 635 may also be signaled when the symbol is partially used for URLLC.

Referring to FIG. 6 , an example of handling conflicts using method 2 is shown. As shown in FIG. 6 , the gNB/BS schedules UE1 and UE2 in subframe N+4 630 by transmitting scheduling control information (ie, PDCCH) 615 in subframe N 610 (eg For example, uplink eMBB packet transmission (631, 633). There is an urgent need to schedule UE3 (eg, URLLC service). Accordingly, UE3 is scheduled in the same subframe N+4 630 by transmitting scheduling control information (ie, PDCCH) 625 in subframe N+3 620 . Alternatively, UE3 may autonomously use the URLLC resource 635 in subframe N+4 630 . To avoid conflicts, URLLC services are prioritized over eMBB services. UE1 and/or UE2, if this is a URLLC subframe, and the resources allocated to the UL packets 631 and 633 in SF N+4 630 overlap with the URLLC resource 635, SF N+4 ( In 630, the transmission of the URLLC symbol 635 is skipped. Alternatively, when SF N+4 (630) is a URLLC subframe, and the resources allocated to UL packets (631, 633) of SF N+4 (630) overlap URLLC resource (635), UE1 and UE2 are Drop UL packet transmission in SF N+4 (630).

7 illustrates a message flow between a UE and a gNB/BS for collision handling in case of dynamic scheduling according to an embodiment of the present disclosure.

Referring to FIG. 7 , in operation 710 , URLLC configuration information (eg, subframe, OFDM symbol, physical resource block (PRB) or subcarrier, etc.) is broadcast by the gNB/BS 210 . In operation 720 , the gNB/BS 210 determines scheduling of UE1 220 for uplink Embb packet transmission, and determines packet scheduling information for UE1 220 . In operation 730 , UE1 220 schedules the eMBB packet in SF X 630 by first scheduling control information transmitted by gNB/BS 210 . In operation 740 , UE1 220 prepares a packet for transmission.

In operation 750 , UE1 220 determines whether SF X is a URLLC subframe.

In operation 760 , UE1 220 indicates that this (scheduled subframe of UE1 220 ) is a URLLC subframe, and the resource allocated to the UL packet in SF X 630 is determined in that subframe 630 . In the case of overlapping with the URLLC resource 635 of , the transmission of the URLLC symbol 635 in the SF X 630 is skipped. Alternatively, UE1 220, if this is a URLLC subframe, and the resource allocated to the UL packet in SF X 630 overlaps with the URLLC resource 635 in that subframe 630, SF X ( 630) drop the UL packet transmission.

8 illustrates a message flow between a UE and a gNB/BS for collision handling in the case of an SPS according to an embodiment of the present disclosure.

Referring to FIG. 8 , in operation 810 , URLLC configuration information (eg, subframe, OFDM symbol, PRB or subcarrier, etc.) is broadcast by the gNB/BS 210 . In operation 820 , UE1 220 is first scheduled for SPS resource activation by gNB/BS 210 . In an embodiment of the present disclosure, UE1 220 schedules SPS resource activation in SF X. In operation 830 , UE1 220 prepares and transmits an uplink packet in the SPS resource scheduled by gNB/BS 210 .

In operation 840 , UE1 220 determines whether SF X is a URLLC subframe.

In operation 850 , UE1 220 indicates that this (scheduled SPS subframe X of UE1 220 ) is a URLLC subframe, and the SPS resource allocated to the UL packet in SF X is URLLC in that subframe. In case of overlapping with resource, transmission of URLLC symbol in SF X is skipped. Alternatively, UE1 220 drops the UL packet transmission in SF X if this is a URLLC subframe and the resource allocated to the UL packet in SF X overlaps the URLLC resource in that subframe.

In an embodiment of the present disclosure, whether the UE should apply a skip/drop rule for a scheduled UL packet may be signaled by the gNB/BS. Only when this is signaled, only the UE skips and drops the resource allocated to the UL packet in SF X when it overlaps with the URLLC resource in the corresponding subframe.

1. Whether the UE should apply the skip rule may be indicated in dedicated signaling.

2. Whether the UE should apply the skip rule may be specified for each logical channel or LCG. Scheduling information may be specific to a logical channel or an LCG. Therefore, the UE applies the skip rule for the UL packet of the allowed logical channel or LCG.

3. Whether to apply the skip rule may be specified for each RAN slice.

4. The scheduling information may have a packet type. Whether to apply the skip rule may be applied to a specific packet type. Accordingly, the UE applies the skip rule to the UL packet of the allowed packet type.

Method 3

9 illustrates a conflict handling operation according to an embodiment of the present disclosure.

Referring to FIG. 9 , in method 3, UL packets 931 and 933 are scheduled to UEs (UE1 and/or UE2) in time slot X 930 , and scheduling information 915 includes one or more URLLC symbols 935 . indicates to skip, the UE (eg, UE1 and/or UE2) skips transmission in one or more URLLC symbols 935 in time slot X (eg, N+4 subframes) 930 . In an embodiment of the present disclosure, the skipped URLLC symbol 935 is indicated in the scheduling information.

Referring to FIG. 9 , an example of handling conflicts using the proposed method is shown. As shown in FIG. 9 , the gNB/BS schedules UE1 and UE2 in subframe N+4 930 by transmitting scheduling control information (ie, PDCCH) 915 in subframe N 910 (eg For example, uplink eMBB packet transmission (931, 933)). There is an urgent need to schedule UE3 (eg, URLLC service). Accordingly, UE3 is scheduled in the same subframe N+4 930 by transmitting the scheduling control information (ie, PDCCH) 925 in subframe N+3 920 . Alternatively, UE3 may autonomously use the URLLC resource 935 in subframe N+4 930 . To avoid conflicts, URLLC services are prioritized over eMBB services. UE1 and/or UE2 skip transmission of URLLC symbol 935 in SF N+4 930 if this is indicated in scheduling information 915 transmitted in subframe N 910 . This method may be wasteful if the URLLC symbol 935 is not used for the URLLC service of UE3. However, the signaling overhead of broadcasting URLLC setting and skip indication is reduced.

The method described above has been described for handling collisions between URLLC and eMBB across UEs. In case of collision between URLLC and eMBB transmission within the same UE, since the UE knows both URLLC and eMBB transmission resources, the UE can skip transmission of either the URLLC packet or the eMBB packet in the collision resource. In the embodiment of the present disclosure, the UE skips the transmission of the URLL packet or the eMBB packet only in symbols with collision. In an embodiment of the present disclosure, the UE may skip transmission of a complete URLL packet or an EMBB packet in case of collision. In an embodiment of the present disclosure, URLLC is prioritized, and eMBB transmission is skipped. In another embodiment of the present disclosure, whether to prioritize eMBB or URLLC may be indicated by the network.

In the above-described methods (Methods 1 to 3), whether to skip only a symbol or an entire packet when there is a collision may be determined based on the number of symbols with a collision. If the number of colliding symbols is greater than or equal to the threshold, the UE skips transmitting the entire packet. Otherwise, the UE only skips the transmission of the collision symbol. The threshold may be signaled by the gNB/BS in broadcast or dedicated signaling to the UE.

DL collision handling

Method 1:

10 illustrates a collision handling operation in a downlink according to an embodiment of the present disclosure.

Referring to FIG. 10 , in method 1, a resource for URLLC 1040 is reserved and indicated to the UE by broadcast or dedicated signaling. The gNB/BS receives an indication 1010, indicating whether the reserved resource in the corresponding time slot (eg, subframe, transmission time interval (TTI), etc.) is used (ie, whether URLLC traffic is scheduled). 1015) is sent. In an embodiment of the present disclosure, the indications 1010 and 1015 may be in a grant or DCI. In an embodiment of the present disclosure, the indications 1010 , 1015 may be for a group of UEs, for example, an eMBB UE. In an embodiment of the present disclosure, the gNB/BS may inform the UE to monitor the indications 1010 , 1015 by RRC signaling. In an embodiment of the present disclosure, the indications 1010 and 1015 may be transmitted on a dedicated channel or a normal PDCCH at a predefined location. In an embodiment of the present disclosure, a special RNTI may be reserved to mask the PDCCH for these indications 1010 and 1015 . This method is illustrated in FIG. 10 . The gNB/BS schedules the UE (eg, downlink eMBB packet transmission 1030 ) by transmitting scheduling control information (ie, PDCCH) 1020 . If the UE DL packet resource (eg, eMBB resource) 1030 collides with the URLLC resource 1040 and the URLLC reserved resource is in use, the gNB/BS indicates that the URLLC resource 1040 is used ( 1015) is sent. Then, during decoding, the UE does not consider this information in the collision resource. In an embodiment of the present disclosure, if the UE DL packet resource 1030 collides with the URLLC resource 1040 and the URLLC reservation resource is not in use, the gNB/BS indicates that the URLLC resource 1040 is not used. cation 1010 is transmitted. In an embodiment of the present disclosure, the indication is transmitted only when the URLLC reserved resource is used.

Method 2:

11 illustrates a collision handling operation in a downlink according to an embodiment of the present disclosure.

Referring to FIG. 11 , in method 2, a resource for URLLC 1140 is dynamically scheduled. The gNB/BS sends an indication 1115 indicating which resources (OFDM symbols and/or PRBs) are used for URLLC in the subframe. The URLLC resource 1140 may be predefined or indicated in the indication 1110 or broadcast. In an embodiment of the present disclosure, for the URLLC resource usage indication 1110 , the UE may read the PDCCH region for URLLC. The gNB/BS schedules the UE (eg, downlink eMBB packet transmission 1130 ) by transmitting scheduling control information (ie, PDCCH) 1120 . If the UE DL packet resource (eg, eMBB resource) 1130 collides with the URLLC resource 1140 , the gNB/BS transmits an indication 1115 indicating that the URLLC resource 1140 is used. Then, during decoding, the UE does not consider this information in the collision resource 1140 . This method is illustrated in FIG. 11 .

The method described above has been described for handling conflicts between URLLC and eMBB transmissions across UEs. In case of collision between URLLC and eMBB transmission within the same UE, since the UE knows both URLLC and eMBB reception resources, the UE can skip the received information of either URLLC packets or eMBB packets in the collision resources during decoding. In an embodiment of the present disclosure, URLLC is prioritized, and eMBB information is skipped. In another embodiment of the present disclosure, whether to prioritize eMBB or URLLC may be indicated by the network.

Indication information

The purpose of the indication is, for example, when resources are allocated to the UE for URLLC service, some UEs (eg, that a certain amount of resources in a time slot are pre-empted and not used in actual transmission). For example, one or more UEs with eMBB service) are informed. If there is a collision between the preemption resource and the resource allocated for eMBB data scheduling in DCI, the UE may assume that the preemption resource is punctured or rate-matched from the allocated resource. Pre-empted resources may include resources in both time domain and frequency domain. For time domain resources, the indication may be a time slot with a predefined duration, eg, an OFDM symbol of 7 symbols or 14 symbol slots targeted to the eMBB service based on system settings. For example, a symbol bitmap can be used to indicate which symbols need to be preempted. For frequency domain resources, this may basically be the entire bandwidth or a set bandwidth portion of the system bandwidth. Alternatively, the indication may be based on a resource block (RB) group. There may be multiple RB groups in the entire bandwidth based on predefined rules. For example, the size of the RB group (eg, M RBs) may be predefined or set by higher layer signaling. If the total bandwidth is represented by N RBs, there is a ceil(N/M) RB group. It may be indicated which RB group needs to be preempted. The UE may obtain how many bits are used to indicate the preemption information of the RB group in the frequency domain. Alternatively, the bitmap size of the indication may be predefined or set by higher layer signaling, for example, X bits, and the size of the RB group is determined by the total number of RBs and the predefined/indicated bitmap size; For example, it may be derived based on M=ceil(N/X).

indication method

12 illustrates an indication method according to an embodiment of the present disclosure.

Referring to FIG. 12 , a pre-emption indication may be for a group of UEs, for example, one or more eMBB UEs. The gNB/BS may inform the UE whether to monitor the preemption indication by RRC signaling. The preemption indication may be transmitted on a dedicated channel or a normal PDCCH at a predefined location. This indication may be addressed by a specific RNTI assigned by the gNB/BS. For example, it may be addressed by a skip-RNTI with a predefined or set value.

In an embodiment of the present disclosure, the preemption indication or skip indication may be a DCI of a MAC CE or PDCCH or a group common DCI of a PDCCH included in an RRC message or a DL MAC PDU. In an embodiment of the present disclosure, the group common DCI for the preemption indication or the skip indication may be transmitted separately from the group common DCI for the slot format indication. In an embodiment of the present disclosure, CORESET information for monitoring group common DCI for preemption indication or skip indication may be signaled in system information or RRC signaling. In an embodiment of the present disclosure, a monitoring interval for monitoring group common DCI for preemption indication or skip indication may be signaled in system information or RRC signaling.

The preemption indication transmitted in time slot m may be applied to the current time slot or a previous time slot, for example, m-P(P>=0). The information of P may be predefined as a fixed offset or may be set by higher layer signaling. The exact value may be represented from a predefined set of values, for example {0, 1, 2, 3}. On the other hand, if the UE is scheduled in the nth time slot, the UE assumes that there may be a preemption indication in the time slot n+P. If the UE fails to decode the downlink data transmission, it may decode one or more times after receiving the preemption indication, for example, by puncturing the preempted resource indicated from the allocated resource. The value P may be explicitly indicated to the UE by dedicated signaling. gNB/BS may set different P values for different UEs. This may be determined by UE capabilities. When the UE reports performance related to PDCCH blind decoding and physical downlink shared channel (PDSCH) processing, the gNB/BS may determine an appropriate P value in consideration of processing performance of the UE. 12 , P=0 and P= to illustrate that the preemption indication may be for the current time slot (ie, P=0), or may be for a previous time slot (ie, P=1) An example of 1 is shown.

13 illustrates a message flow between a UE and a gNB/BS for collision handling in case of dynamic scheduling according to an embodiment of the present disclosure.

Referring to FIG. 13 , in operation 1310 , the gNB/BS 210 determines scheduling of UE1 220 for downlink eMBB packet transmission, and determines packet scheduling information for UE1 220 . In operation 1320 , UE1 220 first schedules the eMBB packet in subframe N1 by scheduling the control information transmitted by gNB/BS 210 in subframe N1 .

At operation 1330 , the gNB/BS 210 determines scheduling of UE3 230 for downlink URLLC packet transmission, and determines packet scheduling information for UE3 230 . In operation 1340 , UE3 230 schedules the URLLC packet in SF N1 by scheduling the control information transmitted by gNB/BS 210 in subframe N1 .

At operation 1350 , gNB/BS 210 determines whether to transmit a preemption indication to UE1 220 . In operation 1360 , if there is a conflict between the eMBB packet scheduled to UE1 220 and the scheduling URLLC packet to UE3 230 , the preemption indication s is gNB/BS in subframe N2 where N2 is greater than or equal to N1 . from 210 to UE1 220 .

If the preemption indication is received by UE1 220 , in operation 1370 , UE1 220 determines whether the preemption indication 150 corresponds to its DL packet transmission. If the preemption indication 150 corresponds to its DL packet transmission, then at operation 1380 , UE1 220 punctures and decodes again the resource preempted during the DL packet transmission in subframe N1 .

Channel state information reference signal (CSI RS )Wow URLLC Conflict handling between senders

14 illustrates a collision processing operation between CSI-RS and URLLC according to an embodiment of the present disclosure.

Referring to FIG. 14 , in order to support low latency, fast data scheduling is required. As a result, there may be a collision between CSI-RS and URLLC transmission. 'P' is the delay between the transmission of the CSI-RS trigger 1410 and the CSI-RS 1430 . 'Q' is the delay between the URLL trigger 1420 and the transmission of the URLLC packet 1410 . In this case, the CSI-RS transmission is dropped and the URLLC packet is transmitted. URLLC packet transmission is more urgent than CSI-RS transmission. In an embodiment of the present disclosure, CSI-RS transmission and CSI-RS reporting may be triggered again by the gNB/BS.

In case of collision, since URLLC packets are transmitted instead of CSI-RS, the UE measuring the CSI-RS will have an inaccurate measurement, and the CSI report will not be accurate. When the CSI-RS is transmitted periodically, and there is no measurement restriction, the UE may transmit a CSI report based on the measurement of any CSI-RS transmission. Therefore, the CSI report should be based on measurements of the latest N CSI-RS transmissions. In an embodiment of the present disclosure, N may be 1. We will know whether the CSI report is correct because we know that the CSI-RS has collided based on this gNB/BS. In an embodiment of the present disclosure, whether to apply the restriction may be signaled. This may also be implicit, ie the UE applies when URLLC is established.

15 is a block diagram of a user device according to an embodiment of the present disclosure.

Referring to FIG. 15 , the UE may include a transceiver 1510 and a controller 1520 for controlling the entire operation thereof.

The transceiver 1510 may transmit signals to and receive signals from other network entities.

The controller 1520 may control the UE to perform a function according to one of the above-described embodiments. For example, the controller 1520 receives the scheduling information for the first uplink packet transmission in the first time slot from the base station, and the first uplink packet transmission in the first time slot at the first time of the other terminal determine whether the first uplink packet transmission in the first time slot is restricted based on information corresponding to the second uplink packet transmission in the slot, and if the first uplink packet transmission in the first time slot is restricted, the first uplink packet transmission in the first time slot can be skipped.

Although controller 1520 and transceiver 1510 are shown as separate entities, they may be implemented as a single entity, such as a single chip. The controller 1520 and the transceiver 1510 may be electrically connected to each other.

The controller 1520 may be a circuit, an application specific circuit, or at least one processor. UE operation may be implemented using a memory unit that stores the corresponding program code. Specifically, the UE may have a memory unit that stores program codes for implementing desired operations, and the controller 1520 may read and execute the program codes stored in the memory unit.

16 is a block diagram of a base station according to an embodiment of the present disclosure.

Referring to FIG. 16 , the base station may include a transceiver 1610 and a controller 1620 for controlling overall operations thereof.

The transceiver 1610 may transmit signals to and receive signals from other network entities.

The controller 1620 may control the base station to perform a function according to one of the above-described embodiments. For example, the controller 1620 transmits the first scheduling information for the first uplink packet transmission in the first time slot to the first terminal, and transmits the first scheduling information for the second uplink packet transmission in the first time slot. 2 send the scheduling information to the second terminal, determine whether the first uplink packet transmission in the first time slot is limited based on the second scheduling information, and the first uplink packet transmission in the first time slot is If limited, it may receive a second uplink packet transmission in the first time slot from the second terminal.

Although controller 1620 and transceiver 1610 are shown as separate entities, this may be realized as a single entity, such as a single chip. The controller 1620 and the transceiver 1610 may be electrically connected to each other.

The controller 1620 may be a circuit, an application specific circuit, or at least one processor. The base station operation may be implemented using a memory unit that stores the corresponding program code. Specifically, the base station may have a memory unit that stores program codes for implementing desired operations, and the controller 1620 may read and execute the program codes stored in the memory unit.

It should be understood that the manner or method and device or component shown in FIGS. 1-16 are not intended to limit the scope of the present disclosure. In addition, it will be apparent to those skilled in the art that the present disclosure may be practiced with only some of the aspects including the components, entities, and operations illustrated in FIGS. 1 to 16 .

The BS operations and UE operations described herein may be implemented using a memory unit that stores corresponding program codes. Specifically, the BS or UE may have a memory unit that stores program codes for implementing desired operations. In order to perform a desired operation, the controller of the BS or UE may read and execute the program code stored in the memory unit by using at least one processor or central processing unit (CPU).

The various components and modules of an entity, base station, or user device described herein may include hardware (such as complementary metal oxide semiconductor (CMOS) logic circuits), software (such as software stored on a machine-readable medium), firmware (such as software stored on a machine-readable medium), or its It can be implemented by use of a combination. For example, various electrical structures and schemes may be realized by the use of electrical circuits such as transistors, logic gates, and ASICs.

While the present disclosure has been shown and described with reference to various embodiments, those skilled in the art will recognize that various changes in form and detail may be made therein without departing from the spirit and scope of the disclosure as defined by the appended claims and their equivalents. you will understand that you can

Claims (16)

A method performed by a terminal of a wireless communication system, comprising:
Receiving, from a base station, information on a pre-emption-related radio network temporary identifier (RNTI) dedicated for monitoring a pre-emption indication in a physical downlink control channel (PDCCH);
receiving, from the base station, the preemption indication in the PDCCH by monitoring the PDCCH based on the preemption-related RNTI; and
Receiving downlink data from the base station by determining that there is no downlink transmission intended for the terminal within the resource indicated by the preemption indication,
The preemption indication indicates an orthogonal frequency division multiplexing (OFDM) symbol and a physical resource block (PRB) of the resource to be used for ultra-reliable and low latency communication (URLLC) transmission to another terminal. The method. The method of claim 1,
The receiving of the information on the preemption-related RNTI further comprises receiving information indicating the region of the PDCCH from the base station. The method of claim 1,
The method of claim 1, wherein the information on the preemption-related RNTI is provided through higher layer signaling. The method of claim 1,
The method is
The method further comprises determining that uplink transmission scheduled in the resource indicated by the preemption indication is skipped;
For URLLC transmission to the other terminal, CSI-RS (channel state information reference signal) reception on the resource is interrupted. A method performed by a base station of a wireless communication system, comprising:
Transmitting, to the terminal, information on a dedicated pre-emption-related radio network temporary identifier (RNTI) for monitoring a pre-emption indication in a physical downlink control channel (PDCCH);
transmitting, to the terminal, the preemption indication in the PDCCH based on the preemption-related RNTI; and
Transmitting an ultra-reliable and low latency communication (URLLC) transmission to another terminal by determining that there is no downlink transmission intended for the terminal within the resource indicated by the preemption indication,
The preemption indication indicates an orthogonal frequency division multiplexing (OFDM) symbol and a physical resource block (PRB) of the resource to be used for URLLC transmission to the other terminal. 6. The method of claim 5,
The transmitting of the information on the preemption-related RNTI further comprises transmitting information indicating the region of the PDCCH to the terminal. 6. The method of claim 5,
The method of claim 1, wherein the information on the preemption-related RNTI is provided through higher layer signaling. 6. The method of claim 5,
The method is
The method further comprises determining that uplink transmission scheduled in the resource indicated by the preemption indication is skipped;
For URLLC transmission to the other terminal, CSI-RS (channel state information reference signal) transmission on the resource is interrupted. In a terminal of a wireless communication system,
a transceiver configured to transmit or receive a signal; and
at least one processor;
The at least one processor comprises:
Receiving information on a dedicated pre-emption-related radio network temporary identifier (RNTI) for monitoring a pre-emption indication in a physical downlink control channel (PDCCH) from the base station,
Receive the preemption indication in the PDCCH by monitoring the PDCCH based on the preemption-related RNTI from the base station,
It is configured to receive downlink data from the base station by determining that there is no downlink transmission intended for the terminal within the resource indicated by the preemption indication,
The preemption indication indicates an orthogonal frequency division multiplexing (OFDM) symbol and a physical resource block (PRB) of the resource to be used for ultra-reliable and low latency communication (URLLC) transmission to another terminal, the terminal. 10. The method of claim 9,
The at least one processor, the terminal is further configured to receive information indicating the region of the PDCCH from the base station. 10. The method of claim 9,
The information on the preemption-related RNTI will be provided through higher layer signaling, the terminal. 10. The method of claim 9,
The at least one processor is further configured to determine that uplink transmission scheduled in the resource indicated by the preemption indication is skipped,
CSI-RS (channel state information reference signal) reception on the resource for URLLC transmission to the other terminal is interrupted (interrupt), the terminal. In the base station,
a transceiver configured to transmit or receive a signal; and
at least one processor;
the at least one processor,
Transmits information on a dedicated pre-emption-related radio network temporary identifier (RNTI) for monitoring a pre-emption indication in a physical downlink control channel (PDCCH) to the terminal,
Transmitting the preemption indication to the terminal in the PDCCH based on the preemption-related RNTI,
It is configured to transmit an ultra-reliable and low latency communication (URLLC) transmission to another terminal by determining that there is no downlink transmission intended for the terminal within the resource indicated by the preemption indication,
The preemption indication indicates an orthogonal frequency division multiplexing (OFDM) symbol and a physical resource block (PRB) of the resource to be used for URLLC transmission to the other terminal, the base station. 14. The method of claim 13,
The at least one processor, the base station that is further configured to transmit information indicating the region of the PDCCH to the terminal. 14. The method of claim 13,
The information on the preemption-related RNTI will be provided through higher layer signaling, the base station. 14. The method of claim 13,
The at least one processor is further configured to determine that uplink transmission scheduled in the resource indicated by the preemption indication is skipped,
For the URLLC transmission to the other terminal, the CSI-RS (channel state information reference signal) transmission on the resource is interrupted, the base station.

Images