Patent Description:
To meet the demand for wireless data traffic having increased since deployment of fourth generation (<NUM>) communication systems, efforts have been made to develop an improved fifth generation (<NUM>) or pre-<NUM> communication system. Therefore, the <NUM> or pre-<NUM> communication system is also called a 'Beyond <NUM> Network' or a 'Post long term evolution (LTE) System.

In the <NUM> system, hybrid frequency shift keying (FSK) and quadrature amplitude modulation (QAM) (FQAM) and sliding window superposition coding (SWSC) as an advanced coding modulation (ACM), and filter bank multi carrier (FBMC), non-orthogonal multiple access (NOMA), and sparse code multiple access (SCMA) as an advanced access technology have been developed.

The internet, which is a human centered connectivity network where humans generate and consume information, is now evolving to the internet of things (IoT) where distributed entities, such as things, exchange and process information without human intervention. The internet of everything (IoE), which is a combination of the IoT technology and the big data processing technology through connection with a cloud server, has emerged. As technology elements, such as "sensing technology," "wired/wireless communication and network infrastructure," "service interface technology," and "Security technology" have been demanded for IoT implementation, a sensor network, a machine-to-machine (M2M) communication, machine type communication (MTC), and so forth have been recently researched. Such an IoT environment may provide intelligent internet technology services that create a new value to human life by collecting and analyzing data generated among connected things.

For example, technologies, such as a sensor network, MTC, and M2M communication may be implemented by beamforming, MIMO, and array antennas.

Compared to existing <NUM> systems, <NUM> systems are expected to support more diversified services. For example, representative services may 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 URLLC services may be referred to as a URLLC system, a system providing eMBB services may be referred to as an eMMB system, and a system providing mMTC services may be referred to as an mMTC system. The words "service" and "system" may be used interchangeably.

<NPL>; discloses UE #<NUM> (with eMBB traffic) is scheduled by the BS for transmission on the downlink shared radio channel. The former is facilitated by the BS sending a scheduling allocation (transmitted on physical layer control channel) followed by the actual transmission of the transport block. In an alternative implementation the scheduling allocation (sent on the physical control channel) for the retransmission could include information to explicitly inform the UE of the punctured part of the first transmission, such that the UE can take this into account in the HARQ soft combining process.

<CIT> discloses a thin control channel structure that can be utilized to enable multiplexing of two or more data transmission formats.

<CIT> discloses in some embodiments, the single resource allocation grant for transmission of the transport block in the first subframe and retransmission of the transport block in the second subframe is comprised in a Downlink Control Information (DCI) message that is scrambled with a Radio Network Temporary Identifier (RNTT) that indicates that preemptive retransmissions will be used for the single resource allocation grant.

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

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

Aspects of the invention are defined by the independent claims.

In a feature of the present disclosure, it is possible to provide a method and an apparatus of handling packet collisions in next generation communication system.

The following description with reference to the accompanying drawings is provided to assist in a comprehensive understanding of various embodiments of the present disclosure as defined by the claims and their equivalents. Accordingly, those of ordinary skill in the art will recognize that various changes and modifications of the various embodiments described herein can be made without departing from the scope of the present disclosure, as defined by the appended claims.

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

Meanwhile, it is known to those skilled in the art that blocks of a flowchart (or sequence diagram) and a combination of flowcharts may be represented and executed by computer program instructions. These computer program instructions may be loaded on a processor of a general purpose computer, special purpose computer or programmable data processing equipment. When the loaded program instructions are executed by the processor, they create a means for carrying out functions described in the flowchart. As the computer program instructions may be stored in a computer readable memory that is usable in a specialized computer or a programmable data processing equipment, it is also possible to create articles of manufacture that carry out functions described in the flowchart. As the computer program instructions may be loaded on a computer or a programmable data processing equipment, when executed as processes, they may carry out operations of functions described in the flowchart.

A block of a flowchart may correspond to a module, a segment or a code containing one or more executable instructions implementing one or more logical functions, or to a part thereof. In some cases, functions described by blocks may be executed in an order different from the listed order. For example, two blocks listed in sequence may be executed at the same time or executed in reverse order.

In the description, the word "unit," "module" or the like may refer to a software component or hardware component, such as an field-programmable gate array (FPGA) or application specific integrated circuits (ASIC) capable of carrying out a function or an operation. However, "unit" or the like is not limited to hardware or software. A unit or the like may be configured so as to reside in an addressable storage medium or to drive one or more processors. Units or the like may refer to software components, object-oriented software components, class components, task components, processes, functions, attributes, procedures, subroutines, program code segments, drivers, firmware, microcode, circuits, data, databases, data structures, tables, arrays or variables. A function provided by a component and unit may be a combination of smaller components and units, and may be combined with others to compose large components and units. Components and units may be configured to drive a device or one or more processors in a secure multimedia card. A component or unit may include one or more processors.

Prior to the detailed description, terms or definitions necessary to understand the present disclosure are described. However, these terms should be construed in a non-limiting way.

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

In recent years, several broadband wireless technologies have been developed to meet the growing number of broadband subscribers and to provide more and better applications and services. The second generation wireless communication system has been developed to provide voice services while ensuring the mobility of users. Third generation wireless communication system supports not only the voice service but also data service. In recent years, the fourth wireless communication system has been developed to provide high-speed data service. However, currently, the fourth generation wireless communication system suffers from lack of resources to meet the growing demand for high speed data services. Accordingly, fifth generation wireless communication system is being developed to meet the growing demand for high speed data services, support ultra-reliability and low latency applications and support massive MTC.

For uplink (UL) packet transmission (UE, terminal)(for example, UE1) is first allocated resources using scheduling control channel (e.g., a physical downlink common control channel (PDCCH)) in time slot (e.g., a subframe) N and the UE (UE1) transmits using the allocated resources in time slot N+P. The value of 'P' is different for different type of services/packets. For enhanced mobile broadband (eMBB) service/packet 'P' is larger than ultra-low latency (URLL)(e.g., ultra-reliable and low latency communication (URLLC)) service/packet. In order to support low latency 'P' is smaller for URLLC packet. This may result in collision between URLLC and eMBB packet transmissions from different UEs (for example, UE1 and UE3).

In another scenario a UE (for example, UE2) may be allocated semi persistently scheduled (SPS) resource. The allocated SPS resource occur periodically every SPS interval. In this case URLLC packet resources allocated to another UE (for example, UE3) using dynamic scheduling may collide with SPS resource.

Accordingly, a method of handling packet collisions is needed.

<FIG> illustrates an operation of handling collision according to an embodiment of the present disclosure.

Referring to <FIG>, in method <NUM>, if URLLC packet <NUM> scheduled in time slot (e.g., a subframe) 'X' (for example, N+<NUM> subframe) <NUM> overlaps with one or more eMBB packet(s) <NUM>, <NUM> then, gNB/BS (base station) transmits (broadcast or dedicated manner) an indication (for example, skipping indication or pre-emption indication) <NUM> to eMBB UE(s) (for example, UE1 and UE2) in time slot 'X-P' (P><NUM>)(for example, N+<NUM> subframe) <NUM> to skip UL transmission (i.e., eMBB packet(s)) in URLLC symbol(s) in time slot 'X' <NUM> OR drop UL packet transmission (i.e., eMBB packet(s)) in time slot 'X' <NUM>. The UE (i.e., UE1 and/or UE2) skips UL transmission (i.e., eMBB packet(s)) in the URLLC symbol(s) which overlaps with the UL packet transmission or the UE (i.e., UE1 and/or UE2) drops UL packet transmission (i.e., eMBB packet(s)) if it overlaps with URLLC symbol(s). In an embodiment of the present disclosure, if the number of symbols where there is collision is above a threshold then the UE (i.e., UE1 and/or UE2) skips entire packet transmission otherwise it skips only transmission in colliding symbols. The threshold can be signaled by the gNB/BS in the indication <NUM> and/or in broadcast and/or in dedicated signaling.

In an embodiment of the present disclosure, 'P' can be in unit of symbols and/or subframes and/or time slots. In an embodiment of the present disclosure, the information of 'P' can be broadcasted and/or explicitly indicated in the RRC signaling. In alternate embodiment the 'P' can be at a fixed offset from time slot 'X' <NUM> in which the UL (uplink) eMBB packet is to be transmitted. In an embodiment of the present disclosure, the gNB/BS can configure a UE to monitor indication (i.e., skipping indication or pre-emption indication) <NUM> in time slot 'X-P' <NUM> or not. This can be determined by UE capability. In an embodiment of the present disclosure, the UE monitors for the indication <NUM> from a time slot <NUM> in which the UL packet is scheduled (i.e., PDCCH scheduling packet is received) until the time slot <NUM> in which the UL packet is scheduled to be transmitted. The gNB/BS can configure a UE to monitor the indication (i.e., skipping or pre-emption indication) <NUM>. In another embodiment of the present disclosure, the UE monitors for the indication <NUM> in time interval comprising of 'X1' slots before the time slot in which the UL packet is scheduled to be transmitted. 'X1' can be signaled by the gNB/BS or can be pre-defined. The gNB/BS can configure a UE to monitor the indication (i.e., skipping or pre-emption indication) <NUM>.

In an embodiment of the present disclosure, the one or more time slots 'X' <NUM> can be explicitly indicated in the indication <NUM>. In an alternate embodiment of the present disclosure, one or more time slots 'X' <NUM> can be at a fixed offset from time slot <NUM> in which indication <NUM> is transmitted by the gNB/BS.

In an embodiment of the present disclosure, the one or more URLLC symbol(s) to be skipped in one or time slots 'X' <NUM> can be explicitly indicated in the indication <NUM> by the gNB/BS. In an alternate embodiment of the present disclosure, the one or more URLLC symbol(s) can be pre-defined. In another embodiment of the present disclosure, the one or more URLL symbol(s) can be broadcasted in system information by the gNB/BS.

In an embodiment of the present disclosure, the indication <NUM> can be signaled in broadcast or dedicated manner. In a case of dedicated signaling, the indication <NUM> can be addressed to UE's cell-radio network temporary identifier(C-RNTI). For example, if the scheduled resource for the UE1 and the scheduled resource for the UE3 only overlaps and the scheduled resource for the UE2 and the scheduled resource for the UE3 does not overlaps, the indication <NUM> can be addressed to UE1's C-RNTI. Depending on whether collision is with one or multiple UEs, appropriate signaling method can be used by the gNB/BS. In a case of broadcast signaling, the indication <NUM> can be addressed to broadcast radio network temporary identifier (RNTI). Alternately, in a case of broadcast signaling, the indication <NUM> can be addressed to a new RNTI (e.g., skip-RNTI). The UEs which have been scheduled UL packet (and/or UL packet (e.g., eMBB) which has low priority compared to other packets (e.g., URLLC)) may only monitor indication <NUM> addressed to skip-RNTI. In an embodiment of the present disclosure, the indication <NUM> can be an radio resource control (RRC) message or medium access control (MAC) control element (CE) included in DL MAC packet data unit (PDU) or downlink control information (DCI) in PDCCH or group common DCI in PDCCH. In an embodiment of the present disclosure, the group common DCI for the skipping indication can be transmitted separately from group common DCI for slot format indication. In an embodiment of the present disclosure, the control resource set (CORESET) information for monitoring the group common DCI for the skipping indication can be signaled in system information or in RRC signaling. In an embodiment of the present disclosure, the monitoring interval for monitoring the group common DCI for the skipping indication can be signaled in system information or in RRC signaling. In an embodiment of the present disclosure, the indication <NUM> can also be signaled using broadcast channel (BCH).

Referring to <FIG>, an example of handling collision using method <NUM> is illustrated. As illustrated in <FIG>, the gNB schedules UE1 and UE2 in subframe N+<NUM><NUM> (for example, uplink eMBB packet transmission, <NUM>, <NUM>) by transmitting scheduling control information (i.e., PDCCH) <NUM> in subframe N <NUM>. Later there is an urgent need to schedule UE3 (for example, URLLC service). The UE3 is scheduled in same subframe N+<NUM><NUM> by transmitting scheduling control information (i.e., PDCCH) <NUM> in subframe N+<NUM><NUM>. In this case, the gNB/BS knows that it has already scheduled the UE1 and the UE2 in subframe N+<NUM><NUM>. To avoid collision, the URLLC service is prioritized over the eMBB service. The gNB/BS sends an indication <NUM> before the subframe N+<NUM><NUM> indicating the UE1 and the UE2 to skip transmission (of the uplink eMBB packet) in the URLLC symbols <NUM> in the SF (subframe) N+<NUM><NUM>. Alternately, the gNB/BS sends an indication <NUM> before subframe N+<NUM><NUM> indicating the UE1 and the UE2 to drop the UL packet transmission in the SF N+<NUM><NUM>.

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

Referring to <FIG>, at operation <NUM>, a gNB/BS <NUM> determines scheduling a UE1 <NUM> for uplink eMBB packet transmission, and determines packet scheduling information for the UE1 <NUM>. At operation <NUM>, the UE1 <NUM> is first scheduled an eMBB packet in subframe (SF) X by scheduling control information transmitted by the gNB/BS <NUM> in subframe N1. At operation <NUM>, the UE1 <NUM> prepares uplink eMBB packet for transmission.

At operation <NUM>, the gNB/BS <NUM> determines scheduling a UE3 <NUM> for URLLC packet transmission, and determines packet scheduling information for the UE3 <NUM>. At operation <NUM>, the UE3 <NUM> is scheduled a URLLC packet in SF X by scheduling control information transmitted by the gNB/BS <NUM> in subframe N2, where N2>N1.

At operation <NUM>, the gNB/BS <NUM> determines whether to transmit, to the UE1 <NUM>, the skipping indication <NUM> or not. At operation <NUM>, the skipping indication <NUM> is sent, from the gNB/BS <NUM> to the UE1 <NUM>, in subframe N3 where N3>N2, if there is collision between eMBB packet scheduled to UE1 <NUM> and the URLLC packet scheduled to the UE3 <NUM>.

If the skipping indication <NUM> is received by UE1 <NUM>, then, at operation <NUM>, the UE1 <NUM> determines whether the skipping indication <NUM> corresponds to its UL packet transmission. If the UE1 <NUM> is applicable to its UL packet transmission, then the UE1 <NUM> skips UL transmission in URLLC symbol(s) or drop the UL packet transmission, at operation <NUM>. The skipping indication <NUM> is applicable to UE1 <NUM> it is addressed to it and/or its UL packet transmission collides with the URLLC symbol(s).

Referring to <FIG>, it is same as <FIG> except that skipping indication <NUM> is sent in subframe N3 where N3 equals N2.

At operation <NUM>, the gNB/BS <NUM> determines scheduling the UE1 <NUM> for uplink eMBB packet transmission, and determines packet scheduling information for the UE1 <NUM>. At operation <NUM>, the UE1 <NUM> is first scheduled an eMBB packet in SF X by scheduling control information transmitted by the gNB/BS <NUM> in subframe N1. At operation <NUM>, the UE1 <NUM> prepares uplink eMBB packet for transmission.

At operation <NUM>, the gNB/BS <NUM> determines scheduling the UE3 <NUM> for URLLC packet transmission, and determines packet scheduling information for the UE3 <NUM>. The gNB/BS <NUM> determines whether to transmit, to the UE1 <NUM>, the skipping indication <NUM> or not.

At operation <NUM>, the UE3 <NUM> is scheduled a URLLC packet in SF X by scheduling control information transmitted by the gNB/BS <NUM> in subframe N2, where N2>N1. At operation <NUM>, the skipping indication <NUM> is sent, from the gNB/BS <NUM> to the UE1 <NUM>, in subframe N3 where N3 = N2, if there is collision between eMBB packet scheduled to UE1 <NUM> and the URLLC packet scheduled to the UE3 <NUM>.

If the skipping indication <NUM> is received by UE1 <NUM>, then, at operation <NUM>, the UE1 <NUM> determines whether skipping indication <NUM> corresponds to its UL packet transmission. If the UE1 <NUM> is applicable to its UL packet transmission, then the UE1 <NUM> skips UL transmission in the URLLC symbol(s) or drop the UL packet transmission, at operation <NUM>. The skipping indication <NUM> is applicable to UE1 <NUM> it is addressed to it and/or its UL packet transmission collides with URLLC symbol(s).

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

Referring to <FIG>, a UE (for example, the UE1) <NUM> may be allocated SPS resource <NUM>, <NUM>. The allocated SPS resource <NUM>, <NUM> occur periodically every SPS interval <NUM>. There is an urgent need to schedule the UE3 <NUM> (for example, URLLC service). Accordingly, the UE3 <NUM> is scheduled in same subframe N+<NUM><NUM> by transmitting scheduling control information (i.e., PDCCH) <NUM> in subframe N+<NUM><NUM>. The URLLC packet resources <NUM> allocated to another UE (for example, the UE3) <NUM> using dynamic scheduling may collide with SPS resource <NUM>.

In this case, if URLLC packet <NUM> scheduled in time slot (e.g., a subframe) 'X' (for example, N+<NUM> subframe) <NUM> overlaps with one or more SPS resource <NUM> then, the gNB/BS <NUM> transmits (broadcast or dedicated manner) an indication (for example, skipping indication) <NUM> to the UE1 <NUM> in time slot 'X-P' (P><NUM>)(for example, N+<NUM> subframe) <NUM> to skip UL transmission in URLLC symbol(s) in time slot 'X' <NUM> OR drop UL packet transmission in time slot 'X' <NUM>. The UE1 <NUM> skips UL transmission in the URLLC symbol(s) which overlaps with its the UL packet transmission or the UE1 <NUM> drops UL packet transmission if it overlaps with URLLC symbol(s). The indication <NUM> is almost same as described above examples.

Referring to <FIG>, at operation <NUM>, the UE1 <NUM> is first scheduled SPS resource activation by the gNB/BS <NUM>. In an embodiment of the present disclosure, the UE1 <NUM> is scheduled the SPS resource activation in SF X by scheduling control information transmitted by the gNB/BS <NUM> in subframe N1. At operation <NUM>, the UE1 <NUM> prepares and transmits uplink packet in SPS resources scheduled by the gNB/BS <NUM>. The UE1 <NUM> monitors for skipping indication <NUM>. The skipping indication <NUM> may be only in designated subframes before the SPS subframe.

At operation <NUM>, the gNB/BS <NUM> determines scheduling the UE3 <NUM> for URLLC packet transmission, and determines packet scheduling information for the UE3 <NUM>. At operation <NUM>, the UE3 <NUM> is scheduled a URLLC packet in SF X by scheduling control information transmitted by the gNB/BS <NUM> in subframe N2. In an embodiment of the present disclosure, the N2 is greater than the N1.

At operation <NUM>, the gNB/BS <NUM> determines whether to transmit, to the UE1 <NUM>, the skipping indication <NUM> or not. In an embodiment of the present disclosure, the gNB/BS <NUM> determines scheduling the UE3 <NUM> for URLLC packet transmission, and determines whether to transmit the skipping indication <NUM> to the UE1 <NUM> at the same time.

At operation <NUM>, the skipping indication <NUM> is sent, from the gNB/BS <NUM> to the UE1 <NUM>, in subframe N3, if there is collision between the SPS resources scheduled to UE1 <NUM> and the URLLC packet scheduled to the UE3 <NUM>. In an embodiment of the present disclosure, the N3 is greater or equal to the N2. For example, the gNB/BS <NUM> transmits the scheduling information of the URLLC packet to the UE3, and transmits the skipping indication <NUM> at the same time.

If the skipping indication <NUM> is received by UE1 <NUM>, then, at operation <NUM>, the UE1 <NUM> determines whether skipping indication <NUM> corresponds to its UL packet transmission. If the UE1 <NUM> is applicable to its UL packet transmission, then the UE1 <NUM> skips UL transmission in URLLC symbol(s) or drop the UL packet transmission, at operation <NUM>. The skipping indication <NUM> is applicable to UE1 <NUM> it is addressed to it and/or its UL packet transmission collides with URLLC symbol(s).

In an embodiment whether the UE has to apply skipping/dropping rule for a scheduled UL packet can be signaled by the gNB/BS <NUM>. Only if this is signaled then only the UE skip/drop based on the skipping indication <NUM>, <NUM>.

In an embodiment of the present disclosure, the skipping indication <NUM>, <NUM> can be named as URLLC usage indication or overlapping indication. The gNB/BS <NUM> transmits (broadcast or dedicated manner) an indication that UL URLLC symbol(s) in time slot 'X' are used. The UE skips the UL transmission in the URLLC symbol(s) which overlaps with its UL packet transmission or the UE drops UL packet transmission if it overlaps with the URLLC symbol(s). In an embodiment of the present disclosure, the one or more time slots 'X' can be explicitly indicated in the indication <NUM>, <NUM>. In an alternate embodiment of the present disclosure, one or more time slots 'X' can be at a fixed offset from time slot in which the indication <NUM>, <NUM> is transmitted by the gNB/BS <NUM>. In an embodiment of the present disclosure, the one or more URLLC symbol(s) used in one or more time slots 'X' can be explicitly indicated in the indication <NUM>, <NUM> by the gNB/BS <NUM>. In an alternate embodiment of the present disclosure, the one or more URLLC symbol(s) can be pre-defined. In another embodiment of the present disclosure, the one or more URLLC symbol(s) can be broadcasted in system information by the gNB/BS <NUM>.

Referring to <FIG>, in method <NUM>, the UE (for example, UE1 and/or UE2) skips transmission in the one or more URLLC symbols(s) <NUM> in time slot X (for example, N+<NUM> subframe) <NUM>, if time slot X <NUM> is a URLLC time slot or is a time slot having URLLC symbols, and UL packet <NUM>, <NUM> is scheduled to the UE (UE1 and/or UE2) in time slot X <NUM> and resources allocated for the UL packet <NUM>, <NUM> overlaps with URLLC resources <NUM>. In an embodiment of the present disclosure, the one or more URLLC time slots <NUM> are signaled by the gNB/BS in broadcast signaling. In an embodiment of the present disclosure, the one or more URLLC symbols <NUM> in the URLLC time slots <NUM> can be pre-defined in system. Alternately, the one or more URLLC symbols <NUM> in URLLC time slots <NUM> can also be signaled by the gNB/BS in broadcast signaling. Frequency resources in URLLC symbols <NUM> can also be signaled if the symbol is partially used for URLLC.

Referring to <FIG>, an example of handling collision using method <NUM> is illustrated. As illustrated in <FIG>, the gNB/BS schedules the UE1 and the UE2 in subframe N+<NUM><NUM> (for example, uplink eMBB packet transmission, <NUM>, <NUM>) by transmitting scheduling control information (i.e., PDCCH) <NUM> in subframe N <NUM>. There is an urgent need to schedule UE3 (for example, URLLC service). Accordingly, the UE3 is scheduled in same subframe N+<NUM><NUM> by transmitting scheduling control information (i.e., PDCCH) <NUM> in subframe N+<NUM><NUM>. Alternately, the UE3 may autonomously use the URLLC resource <NUM> in subframe N+<NUM><NUM>. To avoid collision, the URLLC service is prioritized over the eMBB service. The UE1 and/or the UE2 skip transmission in URLLC symbols <NUM> in the SF N+<NUM><NUM>, if it is URLLC subframe and the resources allocated for its UL packet <NUM>, <NUM> in SF N+<NUM><NUM> overlaps with the URLLC resources <NUM>. Alternately, the UE1 and the UE2 drops the UL packet transmission in SF N+<NUM><NUM> if SF N+<NUM><NUM> is a URLLC subframe and the resources allocated for its UL packet <NUM>, <NUM> in SF N+<NUM><NUM> overlaps with the URLLC resources <NUM>.

Referring to <FIG>, at operation <NUM>, URLLC configuration information (for example, subframes, OFDM symbols, physical resource blocks (PRBs) or sub carriers, and the like) is broadcasted by the gNB/BS <NUM>. At operation <NUM>, the gNB/BS <NUM> determines scheduling the UE1 <NUM> for uplink eMBB packet transmission, and determines packet scheduling information for the UE1 <NUM>. At operation <NUM>, the UE1 <NUM> is first scheduled an eMBB packet in SF X <NUM> by scheduling control information transmitted by the gNB/BS <NUM>. At operation <NUM>, the UE1 <NUM> prepare packet for transmission.

At operation <NUM>, the UE1 <NUM> determines whether the SF X is URLLC subframe or not.

At operation <NUM>, the UE1 <NUM> skip transmission in URLLC symbols <NUM> in SF X <NUM>, if it (the scheduled subframe of the UE1 <NUM>) is URLLC subframe and the resources allocated for its UL packet in SF X <NUM> overlaps with the URLLC resources <NUM> in that subframe <NUM>. Alternately, the UE1 <NUM> drops the UL packet transmission in SF X <NUM> if it is URLLC subframe and the resources allocated for its UL packet in SF X <NUM> overlaps with the URLLC resources <NUM> in that subframe <NUM>.

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

Referring to <FIG>, at operation <NUM>, URLLC configuration information (for example, subframes, OFDM symbols, PRBs or sub carriers, and the like) is broadcasted by the gNB/BS <NUM>. At operation <NUM>, the UE1 <NUM> is first scheduled SPS resource activation by the gNB/BS <NUM>. In an embodiment of the present disclosure, the UE1 <NUM> is scheduled the SPS resource activation in SF X. At operation <NUM>, the UE1 <NUM> prepares and transmits uplink packet in SPS resources scheduled by the gNB/BS <NUM>.

At operation <NUM>, the UE1 <NUM> skip transmission in URLLC symbols in SF X, if it (the scheduled SPS subframe X of the UE1 <NUM>) is URLLC subframe and the SPS resources allocated for its UL packet in SF X overlaps with the URLLC resources in that subframe. Alternately, the UE1 <NUM> drops the UL packet transmission in SF X if it is URLLC subframe and the resources allocated for its UL packet in SF X overlaps with the URLLC resources in that subframe.

In an embodiment of the present disclosure whether the UE has to apply the skipping/dropping rule for a scheduled UL packet can be signaled by the gNB/BS. Only if this is signaled then only the UE skip/drop if the resources allocated for its UL packet in the SF X overlaps with the URLLC resources in that subframe.

Referring to <FIG>, in method <NUM>, the UE (for example, UE1 and/or UE2) skips transmission in the one or more URLLC symbols(s) <NUM> in time slot X (for example, N+<NUM> subframe) <NUM>, if UL packet <NUM>, <NUM> is scheduled to the UE (UE1 and/or UE2) in the time slot X <NUM> and scheduling information <NUM> indicates to skip the one or more URLLC symbols <NUM>. In an embodiment of the present disclosure, the URLLC symbols <NUM> to be skipped are indicated in scheduling information.

Referring to <FIG>, an example of handling collision using the proposed method is illustrated. As illustrated in <FIG>, the gNBBS schedules the UE1 and the UE2 in subframe N+<NUM><NUM> (for example, uplink eMBB packet transmission, <NUM>, <NUM>) by transmitting scheduling control information (i.e., PDCCH) <NUM> in subframe N <NUM>. There is an urgent need to schedule UE3 (for example, URLLC service). Accordingly, the UE3 is scheduled in same subframe N+<NUM><NUM> by transmitting scheduling control information (i.e., PDCCH) <NUM> in subframe N+<NUM><NUM>. Alternately, the UE3 may autonomously use the URLLC resource <NUM> in subframe N+<NUM><NUM>. To avoid collision, the URLLC service is prioritized over the eMBB service. The UE1 and/or the UE2 skip transmission in URLLC symbols <NUM> in SF N+<NUM><NUM>, if these are indicated in the scheduling information <NUM> transmitted in the subframe N <NUM>. This method may lead to wastage if the URLLC symbols <NUM> are not used for URLLC service of the UE3. However there is reduced signaling overhead of broadcasting the URLLC configuration and the skipping indication.

The above methods have been explained for handling collision between the URLLC and eMBB across UEs. In a case of collision between the URLLC and eMBB transmission within same UE, the UE knows both the URLLC and eMBB transmission resources, so the UE can skip transmission of either the URLLC packet or the eMBB packet in colliding resources. In an embodiment of the present disclosure, the UE skips transmission of URLL packet or the eMBB packet only in symbols where there is collision. In an embodiment of the present disclosure, the UE can skip transmission of complete URLL packet or EMBB packet in a case of collision. In an embodiment of the present disclosure, the URLLC is prioritized and the eMBB transmission is skipped. In another embodiment of the present disclosure, whether to prioritize the eMBB or the URLLC can be indicated by network.

In the methods (method1 to method <NUM>) explained above, whether to skip only symbols or entire packet when there is collision can decide based on number of symbols where there is collision. If the number of symbols where there is collision is above a threshold then the UE skips entire packet transmission. Otherwise the UE skips only transmission in colliding symbols. Threshold can be signaled by the gNB/BS in broadcast or dedicated signaling to the UE.

<FIG> illustrates an operation of handling collision in downlink according to an embodiment of the present disclosure.

Referring to <FIG>, in method <NUM>, resources for URLLC <NUM> are reserved and indicated to the UE in broadcast or dedicated signaling. The gNB/BS sends indication <NUM>, <NUM> indicating whether reserved resources in the corresponding time slot (e.g., a subframe, transmission time interval (TTI), and the like) are used or not (i.e., whether URLLC traffic is scheduled or not). In an embodiment of the present disclosure, the indication <NUM>, <NUM> can be there in grant or in DCI. In an embodiment of the present disclosure, the indication <NUM>, <NUM> can be for a group of UEs, e.g., eMBB UEs. In an embodiment of the present disclosure, the gNB/BS can inform the UE to monitor the indication <NUM>, <NUM> or not by RRC signaling. In an embodiment of the present disclosure, the indication <NUM>, <NUM> can be transmitted in a dedicated channel, or a normal PDCCH at pre-defined location. In an embodiment of the present disclosure, special RNTI can be reserved for masking PDCCH for this indication <NUM>, <NUM>. This method is illustrated in <FIG>. The gNB/BS schedules the UE (for example, downlink eMBB packet transmission, <NUM>) by transmitting scheduling control information (i.e., PDCCH) <NUM>. If the UE DL packet resources (for example, eMBB resources) <NUM> collide with the URLLC resources <NUM> and URLLC reserved resources are in use, then the gNB/BS transmits the indication <NUM> indicting the URLLC resources <NUM> are used. After, during the decoding the UE does not consider the information in colliding resources <NUM>. In an embodiment of the present disclosure, if the UE DL packet resources <NUM> collide with the URLLC resources <NUM> and URLLC reserved resources are not in use, the gNB/BS transmits the indication <NUM> indicting the URLLC resources <NUM> are not used. In an embodiment of the present disclosure, the indication is only transmitted when the URLLC reserved resources are used.

Referring to <FIG>, in method <NUM>, resources for URLLC <NUM> are dynamically scheduled. The gNB/BS sends indication <NUM> indicating that certain resources (OFDM symbols and/or PRBs) are used for URLLC in the subframe. The URLLC resources <NUM> can be pre-defined or indicated in indication <NUM> or broadcasted. In an embodiment of the present disclosure, for URLLC resource usage indication <NUM>, the UE may read PDCCH region for URLLC. The gNB/BS schedules the UE (for example, downlink eMBB packet transmission, <NUM>) by transmitting scheduling control information (i.e., PDCCH) <NUM>. If the UE DL packet resources (for example, eMBB resources) <NUM> collides with the URLLC resources <NUM>, then the gNB/BS transmits the indication <NUM> indicting the URLLC resources <NUM> are used. After, during the decoding the UE does not consider the information in colliding resources <NUM>. This method is illustrated in <FIG>.

The above methods have been explained for handling collision between the URLLC and cMBB transmissions across UEs. In a case of collision between the URLLC and eMBB transmission within same UE, the UE knows both the URLLC and eMBB reception resources, so the UE can skip received information of either the URLLC packet or eMBB packet in colliding resources during decoding. In an embodiment of the present disclosure, the URLLC is prioritized and the eMBB information is skipped. In another embodiment of the present disclosure, whether to prioritize the eMBB or the URLLC can be indicated by network.

The purpose of the indication is to inform some UEs (e.g., one or more UEs with eMBB service) that a certain amount of resources in a time slot are pre-empted and not used in the actual transmission, for example, if the resources are assigned to a UE for URLLC service. If there is conflict between the pre-empted resources and assigned resources for eMBB data scheduling in the DCI, the UE may assume that the pre-empted resources are punctured or rate-matched from the assigned resources. The pre-emptied resources may include the resources in both time domain and frequency domain. For time domain resources, the indication can be the OFDM symbols in a time slot with pre-defined duration, for example, a <NUM>-symbol or <NUM>-symbol slot targeted to the eMBB service based on system configuration. For example, a symbol bitmap can be used to indicate which symbol(s) needs to be pre-emptied. For the frequency domain resources, it can be by default the full bandwidth in the system bandwidth or a configured bandwidth part. Or, the indication can be based on the resource block (RB) groups. There can be multiple RB groups in the full bandwidth based on a pre-defined rule. For example, a size of RB group (for example, M RBs) can be pre-defined or configured by the higher layer signaling. If the full bandwidth is expressed by N RBs, there are ceil (N/M) RB groups. It can be indicated which RB groups needs to be pre-emptied. The UE can obtain that how many bits are used to indicate the pre-emption information of the RB groups in the frequency domain. Alternatively, a bitmap size of indication can be pre-defined or configured by the higher layer signaling, for example, X bits, the size of RB group can be derived based on the total number of RBs and pre-defined/indicated bitmap size, for example, M=ceil (N/X).

<FIG> illustrates an indication method according to an embodiment of the present disclosure.

Referring to <FIG>, the pre-emption indication can be for a group of UEs, for example, one or multiple eMBB UEs. The gNB/BS can inform a UE to monitor the pre-emption indication or not by RRC signaling. The pre-emption indication can be transmitted in a dedicated channel, or a normal PDCCH at pre-defined location. The indication can be addressed by a certain RNTI assigned by the gNB/BS. For example, it can be addressed by a skip-RNTI with a pre-defined or configured value.

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

The pre-emption indication transmitted in a time slot m, can be applied for the current time slot or the previous time slot, for example, m-P (P>=<NUM>). The information of P can be pre-defined as a fixed offset, or can be configured by the higher layer signaling. The exact value can be indicated from a set of pre-defined values, for example, {<NUM>, <NUM>, <NUM>, <NUM>?}. On the other hand, if the UE is scheduled in the n-th time slot, the UE assumes that there can be a pre-emption indication in the time slot n+P. If the UE fails to decode a downlink data transmission, it can decode one more time after receiving the pre-emption indication, for example, by puncturing the indicated pre-emptied resources from the assigned resources. The value P can be explicitly indicated to a UE by dedicated signaling. The gNB/BS can configure different values of P to different UEs. This can be determined by UE capability. If the UE reports its capability related to the PDCCH blind decoding and physical downlink shared channel (PDSCH) processing, the gNB/BS can determine a proper P value considering UE's processing capability. In <FIG>, the examples of P=<NUM> and P=<NUM> are shown to illustrate that a pre-emption indication can be for the current time slot (i.e., P=<NUM>), or can be for the previous time slot (i.e., P=<NUM>).

Referring to <FIG>, at operation <NUM>, the gNB/BS <NUM> determines scheduling the UE1 <NUM> for downlink eMBB packet transmission, and determines packet scheduling information for the UE1 <NUM>. At operation <NUM>, the UE1 <NUM> is first scheduled an eMBB packet in subframe N1 by scheduling control information transmitted by the gNB/BS <NUM> in subframe N1.

And, at operation <NUM>, the gNB/BS <NUM> determines scheduling the UE3 <NUM> for downlink URLLC packet transmission, and determines packet scheduling information for the UE3 <NUM>. At operation <NUM>, the UE3 <NUM> is scheduled a URLLC packet in SF N1 by scheduling control information transmitted by the gNB/BS <NUM> in subframe N1.

At operation <NUM>, the gNB/BS <NUM> determines whether to transmit, to the UE1 <NUM>, the pre-emption indication or not. At operation <NUM>, the pre-emption indication s sent, from the gNB/BS <NUM> to the UE1 <NUM>, in subframe N2 where N2 is greater or equal to N1, if there is collision between eMBB packet scheduled to UE1 <NUM> and the URLLC packet scheduled to the UE3 <NUM>.

If the pre-emption indication is received by UE1 <NUM>, then, at operation <NUM>, the UE1 <NUM> determines whether the pre-emption indication <NUM> corresponds to its DL packet transmission or not. If the pre-emption indication <NUM> corresponds to its DL packet transmission, then the UE1 <NUM> punctures pre-emptied resources during DL packet transmission in subframe N1 and decode again at operation <NUM>.

<FIG> illustrates an operation of handling collision between CSI-RS and URLLC according to an embodiment of the present disclosure.

Referring to <FIG>, to support low latency fast data scheduling is needed. As a result there can be collision between CSI-RS and URLLC transmission. 'P' is delay between CSI-RS trigger <NUM> and transmission of CSI-RS <NUM>. 'Q' is delay between URLL trigger <NUM> and transmission of URLLC packet <NUM>. In this case, the CSI-RS transmission is dropped and the URLLC packet is transmitted. The URLLC packet transmission is more urgent then the CSI-RS transmission. In an embodiment of the present disclosure, the CSI-RS transmission and the CSI-RS reporting can be re-triggered by the gNB/BS.

In a case of collision, the URLLC packet is transmitted instead of the CSI-RS, so the UE measuring the CSI-RS will have incorrect measurement and the CSI reporting will be not correct. When the CSI-RS is periodically transmitted and there is no measurement restriction, the UE can send the CSI report based on measurement of any CSI-RS transmission. Accordingly, the CSI report should be based on measurement of latest N CSI-RS transmissions. In an embodiment of the present disclosure, N can be one. Based on this gNB/BS will know whether the CSI report is correct or not as it know which the CSI-RS was collided. In an embodiment of the present disclosure, whether to apply the restriction or not can be signaled. It can also be implicit i.e., the UE applies if the URLLC is configured.

<FIG> is a block diagram of a user equipment according to an embodiment of the present disclosure.

Referring to <FIG>, the UE may include a transceiver <NUM> and a controller <NUM> to control the overall operation thereof.

The transceiver <NUM> may transmit and receive signals to and from other network entities.

The controller <NUM> may control the UE to perform a function according to one of the embodiments described before. For example, the controller <NUM> may receive, from a base station, scheduling information for a first uplink packet transmission in a first time slot, determine whether the first uplink packet transmission in the first time slot is restricted based on information corresponding to a second uplink packet transmission in the first time slot of another terminal, and if the first uplink packet transmission in the first time slot is restricted, skip the first uplink packet transmission in a first time slot.

Although the controller <NUM> and the transceiver <NUM> are shown as separate entities, they may be realized as a single entity like a single chip. The controller <NUM> and the transceiver <NUM> may be electrically connected to each other.

The controller <NUM> may be a circuit, an application-specific circuit, or at least one processor. The UE operations may be implemented using a memory unit storing corresponding program codes. Specifically, the UE may be equipped with a memory unit to store program codes implementing desired operations, and the controller <NUM> may read and execute the program codes stored in the memory unit.

<FIG> is a block diagram of a base station according to an embodiment of the present disclosure.

Referring to <FIG>, the base station may include a transceiver <NUM> and a controller <NUM> to control the overall operation thereof.

The controller <NUM> may control the base station to perform a function according to one of the embodiments described before. For example, the controller <NUM> may transmit, to a first terminal, first scheduling information for a first uplink packet transmission in a first time slot, transmit, to a second terminal, second scheduling information for a second uplink packet transmission in the first time slot, determine whether the first uplink packet transmission in the first time slot is restricted based on the second scheduling information, and if the first uplink packet transmission in the first time slot is restricted, receive, from the second terminal, the second uplink packet transmission in the first time slot.

The controller <NUM> may be a circuit, an application-specific circuit, or at least one processor. The base station operations may be implemented using a memory unit storing corresponding program codes. Specifically, the base station may be equipped with a memory unit to store program codes implementing desired operations, and the controller <NUM> may read and execute the program codes stored in the memory unit.

It should be understood that schemes or methods and devices or components shown in <FIG> are not intended to limit the scope of the present disclosure. It will also be apparent to those skilled in the art that the present disclosure may be practiced with only some of the aspects including components, entities, and operations described in <FIG>.

BS operations and UE operations described herein may be implemented using memory units storing corresponding program codes. Specifically, the BS or the UE may be equipped with a memory unit to store program codes implementing desired operations. To perform a desired operation, the controller of the BS or the UE may read and execute the program codes stored in the memory unit by using at least one processor or a central processing unit (CPU).

Various components and modules of the entity, base station or user equipment described in the specification may be implemented by use of hardware (such as complementary metal oxide semiconductor (CMOS) logic circuits), software, firmware (such as software stored in machine readable media), or a combination thereof. For example, various electrical structures and schemes may be realized by use of electric circuits, such as transistors, logic gates, and ASIC.

Claim 1:
A method performed by a terminal in a wireless communication system, the method comprising:
receiving, via radio resource control, RRC, signaling from a base station, information on monitoring of a pre-emption indication based on a pre-emption related radio network temporary identifier, RNTI, assigned by the base station and dedicated for the monitoring of the pre-emption indication in a physical downlink control channel, PDCCH;
receiving (<NUM>), from the base station, the pre-emption indication in the PDCCH by monitoring the PDCCH based on the pre-emption related RNTI, wherein the pre-emption indication indicates an orthogonal frequency division multiplexing, OFDM, symbol and a physical resource block, PRB, of a resource to be used for an ultra-reliable and low latency communication, URLLC, transmission to another terminal; and
receiving, from the base station, downlink data,
wherein the resource indicated by the pre-emption indication are not used for receiving the downlink data.