CN114930951B - Signal cancellation method - Google Patents

Abstract

A system and method for satisfying the latency and reliability requirements of URLLC signal transmissions. The system and method include receiving, by a wireless communication device, a control signal from a wireless communication node indicating whether to repeatedly transmit each of a plurality of uplink channels on an unlicensed frequency band; the plurality of uplink channels are respectively transmitted to the wireless communication node by the wireless communication device based on the control signal.

Description

Signal cancellation method

Technical Field

The present disclosure relates generally to wireless communications, and more generally to systems and methods that meet the latency and reliability requirements of signal transmission for ultra-reliable low-latency communications (URLLC).

Background

The standardization organization third generation partnership project (3 GPP) is currently specifying a new radio interface called 5G new radio (5G NR). The 5G NR system supports various services such as an ultra-reliable low-delay communication (URLLC) service. URLLC services provide support for high reliability and low latency services. In some cases, URLLC services may provide reliability of up to 99.9999% block error rate with an air interface transmission delay within 1 millisecond.

Disclosure of Invention

Embodiments disclosed herein are directed to solving one or more problems associated with the prior art and providing other features that will become readily apparent when reference is made to the following detailed description in conjunction with the accompanying drawings. According to various embodiments, example systems, methods, apparatus, and computer program products are disclosed herein. It should be understood that these embodiments are presented by way of illustration and not limitation, and that various modifications of the disclosed embodiments may be made which remain within the scope of the disclosure, as will be apparent to those of ordinary skill in the art from reading the disclosure.

In one embodiment, a method includes receiving, by a wireless communication device (e.g., UE 104 in fig. 1) from a wireless communication node (e.g., BS102 in fig. 1), a control signal indicating whether to repeatedly transmit each of a plurality of uplink channels (e.g., one or more PUSCHs) on an unlicensed frequency band. In some embodiments, the method includes transmitting, by the wireless communication device, a plurality of uplink channels to the wireless communication node, respectively, based on the control signal.

In another embodiment, a method includes receiving, by a wireless communication device from a wireless communication node, a control signal indicating a plurality of service types and a plurality of methods. In some embodiments, the method includes determining, by the wireless communication device, one of the plurality of methods corresponding to one of the plurality of service types based on the control signal. In some embodiments, the method includes transmitting, by the wireless communication device, each of the plurality of uplink channels to the wireless communication node using a respective one of the methods.

In another embodiment, a method includes transmitting, by a wireless communication node to a wireless communication device, a control signal indicating whether to repeatedly transmit each of a plurality of uplink channels on an unlicensed frequency band. In some embodiments. The method includes receiving, by the wireless communication node, the plurality of uplink channels from the wireless communication device in response to the transmission of the control signal.

In another embodiment, a method includes transmitting, by a wireless communication node, a control signal to a wireless communication device indicating a plurality of service types and a plurality of methods. In some embodiments, the control signal causes the wireless communication device to: one of the plurality of methods corresponding to one of the plurality of service types is determined based on the control signal. In some embodiments, the control signal causes the wireless communication device to transmit each of the plurality of uplink channels to the wireless communication node using a respective one of the methods. In some embodiments, the method includes receiving, by the wireless communication node, the plurality of uplink channels from the wireless communication device.

The above and other aspects and embodiments thereof are described in more detail in the accompanying drawings, description and claims.

Drawings

Various example embodiments of the present solution are described in detail below with reference to the following figures or drawings. The drawings are provided for illustrative purposes only and depict only exemplary embodiments of the present solution to facilitate the reader's understanding of the present solution. Accordingly, the drawings should not be taken as limiting the breadth, scope, or applicability of the present solution. It should be noted that for clarity and ease of illustration, the drawings are not necessarily made to scale.

Fig. 1 illustrates an example cellular communication network in which the techniques disclosed herein may be implemented, according to an embodiment of the disclosure.

Fig. 2 illustrates a block diagram of an example base station and user equipment device, according to some embodiments of the present disclosure.

Fig. 3 shows a block diagram of an example mapping of PUSCH configuration, according to an embodiment of the disclosure.

Fig. 4 shows a table of HARQ process numbers and example transmission cases of PUSCH according to an embodiment of the present disclosure.

Fig. 5 illustrates a block diagram of an example mapping of PUSCH configurations, according to some embodiments of the disclosure.

Fig. 6 illustrates a block diagram of an example mapping of PUSCH configurations, according to some embodiments of the disclosure.

Fig. 7 illustrates a block diagram of an example mapping of PUSCH configurations, according to some embodiments of the disclosure.

Fig. 8 illustrates a block diagram of an example mapping of PUSCH configurations, according to some embodiments of the disclosure.

Fig. 9 illustrates a table of an example mapping 900 of PUSCH configurations in accordance with some embodiments of the disclosure.

Fig. 10 is a flow chart illustrating a method for satisfying delay and reliability requirements of signal transmission for ultra-reliable low-delay communication (URLLC) from the perspective of a UE, according to some embodiments of the present disclosure.

Fig. 11 is a flow chart illustrating a method for satisfying the latency and reliability requirements of signal transmission for ultra-reliable low-latency communications (URLLC) from the perspective of a UE, according to some embodiments of the present disclosure.

Fig. 12 is a flow chart illustrating a method for satisfying delay and reliability requirements of signal transmission for ultra-reliable low-delay communication (URLLC) from the perspective of a BS, according to some embodiments of the present disclosure.

Fig. 13 is a flow chart illustrating a method for satisfying delay and reliability requirements of signal transmission for ultra-reliable low-delay communication (URLLC) from the perspective of a BS, according to some embodiments of the present disclosure.

Detailed Description

Various example embodiments of the present solution are described below with reference to the accompanying drawings to enable one of ordinary skill in the art to make and use the present solution. It will be apparent to those of ordinary skill in the art after reading this disclosure that various changes or modifications can be made to the examples described herein without departing from the scope of the present solution. Thus, the present solution is not limited to the example embodiments and applications described and illustrated herein. In addition, the particular order or hierarchy of steps in the methods disclosed herein is an example approach. Based on design preferences, the specific order or hierarchy of steps in the methods or processes disclosed may be rearranged while remaining within the scope of the present solution. Accordingly, those of ordinary skill in the art will understand that the methods and techniques disclosed herein present various steps or acts in an example order, and that the present solution is not limited to the particular order or hierarchy presented unless specifically stated otherwise.

The following acronyms are used throughout this disclosure:

3GPP third Generation partnership project

5G fifth generation mobile network

5G-AN 5G access network

5G gNB next generation NodeB

CBG code block group

CCA clear channel access

CE control element

CG configuration authorization

COT channel occupancy time

DCI downlink control information

DG dynamic authorization

DL downlink or downlink

EMBB enhanced moving broadband

ENBs evolved node B

ETSI European Telecommunications standards institute

LBT listen before talk/listen before hair

LTE long term evolution

MAC medium access control

MSC mobile switching center

NAS non-access stratum

NR next generation RAN

OFDM orthogonal frequency division multiplexing

OFDMA multiple access

OSI open system interconnection

PDCP packet data convergence protocol

RAN radio access network

RLC radio link control

RRC radio resource control

RV redundancy version

TB transport block

UE user equipment

UL uplink or uplink

URLLC ultra-reliable low-delay communications

Future wireless communication systems (e.g., 5G NR) support various services such as ultra-reliable low-latency communication (URLLC) services. URLLC services provide support for high reliability and low latency services. In some cases, URLLC services may provide reliability of up to 99.9999% block error rate with an air interface transmission delay within 1 millisecond.

However, URLLC services may not provide such high reliability when the network side (e.g., BS102 in fig. 1) schedules multiple PUSCHs for signal transmission. For example, if the UE only preempts a portion of the PUSCH frequency domain resources, it is difficult to determine how to signal during this time. That is, if URLLC data arrives during PUSCH transmission, and if URLLC data is scheduled again after PUSCH transmission is completed, the delay requirement of URLLC may not be satisfied. Thus, when signaling occurs on the current PUSCH, a mechanism is needed to determine how to achieve the delay requirements required for URLLC to provide high reliability.

Accordingly, the systems and methods discussed herein provide a mechanism for meeting (e.g., conforming to, etc.) the latency and reliability requirements of URLLC's signal transmissions.

In general, as discussed in more detail below, when a UE successfully performs CCA over a portion of the LBT bandwidth, the UE may send (e.g., transmit, deliver, etc.) a PUSCH.

In some embodiments, the UE may determine the repeated transmission of PUSCH according to the PDCCH transmission mechanism and/or the COT boundary. In some embodiments, the UE may determine the repeated transmission of PUSCH according to a configuration from the network. In some embodiments, the UE may determine the repeated transmission of PUSCH according to the service type of the data transmitted by the UE. In some embodiments, the HARQ process number of the repeatedly transmitted PUSCH may be the HARQ process number of the previous PUSCH. In some embodiments, the HARQ process number is changed only on the PUSCH originally transmitted.

In some embodiments, the UE may determine the MCS for PUSCH transmission according to a configuration from the network. In some embodiments, the UE may determine an MCS for PUSCH transmission according to a service type of data transmitted by the UE.

1. Mobile communication technology and environment

Fig. 1 illustrates an example wireless communication network and/or system 100 in which the techniques disclosed herein may be implemented, according to an embodiment of the disclosure. In the following discussion, the wireless communication network 100 may be any wireless network, such as a cellular network or a narrowband internet of things (NB-IoT) network, and is referred to herein as "network 100". Such an example network 100 includes a base station 102 (hereinafter referred to as "BS102", also referred to as a wireless communication node) and a user equipment device 104 (hereinafter referred to as "UE 104", also referred to as a wireless communication device), and a cluster of cells 126, 130, 132, 134, 136, 138, and 140 that cover a geographic area 101, which may communicate with each other via a communication link 110 (e.g., a wireless communication channel). In fig. 1, BS102 and UE 104 are contained within respective geographic boundaries of cell 126. Each of the other cells 130, 132, 134, 136, 138, and 140 may include at least one base station operating on its allocated bandwidth to provide adequate radio coverage to its target users.

For example, BS102 may operate on the allocated channel transmission bandwidth to provide adequate coverage to UE 104. BS102 and UE 104 may communicate via downlink radio frame 118 and uplink radio frame 124, respectively. Each radio frame 118/124 may be further divided into subframes 120/127, and the subframes 120/127 may include data symbols 122/128. In the present disclosure, BS102 and UE 104 are described herein as non-limiting examples of "communication nodes" that may generally practice the methods disclosed herein. According to various embodiments of the present solution, such communication nodes are capable of wireless and/or wired communication.

Fig. 2 illustrates a block diagram of an example wireless communication system 200 for transmitting and receiving wireless communication signals (e.g., OFDM/OFDMA signals) in accordance with some embodiments of the present solution. The system 200 may include components and elements configured to support known or conventional operational features that need not be described in detail herein. In one illustrative embodiment, as described above, system 200 may be used for communication (e.g., transmission and reception) of data symbols in a wireless communication environment such as wireless communication environment 100 of fig. 1.

The system 200 generally includes a base station 202 (hereinafter "BS 202") and a user equipment device 204 (hereinafter "UE 204"). BS202 includes BS (base station) transceiver module 210, BS antenna 212, BS processor module 214, BS memory module 216, and network communication module 218, each of which are coupled and interconnected to each other as needed via data communication bus 220. The UE 204 includes a UE (user equipment) transceiver module 230, a UE antenna 232, a UE memory module 234, and a UE processor module 236, each coupled and interconnected with each other as needed via a data communication bus 240. BS202 communicates with UE 204 via communication channel 250, which communication channel 250 may be any wireless channel or other medium suitable for data transmission as described herein.

Those of ordinary skill in the art will appreciate that the system 200 may further include any number of modules in addition to those shown in fig. 2. Those of skill in the art will appreciate that the various illustrative blocks, modules, circuits, and processing logic described in connection with the embodiments disclosed herein may be implemented as hardware, computer readable software, firmware, or any practical combination thereof. To clearly illustrate this interchangeability and compatibility of hardware, firmware, and software, various illustrative components, blocks, modules, circuits, and steps have been described above generally in terms of their functionality. Whether such functionality is implemented as hardware, firmware, or software depends upon the particular application and design constraints imposed on the overall system. Those familiar with the concepts described herein may implement such functionality in an appropriate manner for each particular application, but such implementation decisions should not be interpreted as limiting the scope of the present disclosure.

According to some embodiments, UE transceiver 230 may be referred to herein as an "uplink" transceiver 230 that includes a Radio Frequency (RF) transmitter and an RF receiver that each include circuitry coupled to an antenna 232. A duplex switch (not shown) may alternatively couple the uplink transmitter or receiver to the uplink antenna in a time division duplex manner. Similarly, BS transceiver 210 may be referred to herein as a "downlink" transceiver 210, according to some embodiments, that includes an RF transmitter and an RF receiver, each including circuitry coupled to antenna 212. The downlink duplex switch may instead couple the downlink transmitter or receiver transmissions to the downlink antenna 212 in a time division duplex manner. The operation of the two transceiver modules 210 and 230 may be coordinated in time such that the uplink receiver circuit is coupled to the uplink antenna 232 to receive transmissions over the wireless transmission link 250 while the downlink transmitter is coupled to the downlink antenna 212. Conversely, the operation of the two transceivers 210 and 230 may be coordinated in time such that the downlink receiver is coupled to the downlink antenna 212 to receive transmissions over the wireless transmission link 250 while the uplink transmitter is coupled to the uplink antenna 232. In some embodiments, there is a tight time synchronization between the duplex direction changes, with only a minimum guard time.

The UE transceiver 230 and the base station transceiver 210 are configured to communicate via a wireless data communication link 250 and cooperate with a suitably configured RF antenna arrangement 212/232 that may support a particular wireless communication protocol and modulation scheme. In some demonstrative embodiments, UE transceiver 210 and base station transceiver 210 are configured to support industry standards, such as Long Term Evolution (LTE) and emerging 5G standards. However, it should be understood that the present disclosure is not necessarily limited in application to a particular standard and associated protocol. Rather, the UE transceiver 230 and the base station transceiver 210 may be configured to support alternative or additional wireless data communication protocols, including future standards or variations thereof.

According to various embodiments, BS202 may be, for example, an evolved node B (eNB), a serving eNB, a target eNB, a femto station, or a pico station. In some embodiments, the UE 204 may be embodied in various types of user equipment, such as mobile phones, smart phones, personal Digital Assistants (PDAs), tablet computers, laptop computers, wearable computing devices, and the like. The processor modules 214 and 236 may be implemented or realized with general purpose processors, content addressable memory, digital signal processors, application specific integrated circuits, field programmable gate arrays, any suitable programmable logic devices, discrete gate or transistor logic, discrete hardware components, or any combination thereof, that are intended to perform the functions described herein. In this manner, a processor may be implemented as a microprocessor, controller, microcontroller, state machine, or the like. A processor may also be implemented as a combination of computing devices, e.g., a combination of a digital signal processor and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a digital signal processor core, or any other such configuration.

Furthermore, the steps of a method or algorithm described in connection with the embodiments disclosed herein may be embodied directly in hardware, in firmware, in a software module executed by the processor modules 214 and 236, respectively, or in any practical combination thereof. Memory modules 216 and 234 may be implemented as RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, a hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art. In this regard, memory modules 216 and 234 may be coupled to processor modules 210 and 230, respectively, such that processor modules 210 and 230 may read information from memory modules 216 and 234 and write information to memory modules 216 and 234, respectively. Memory modules 216 and 234 may also be integrated into their respective processor modules 210 and 230. In some embodiments, memory modules 216 and 234 may each include a cache memory for storing temporary variables or other intermediate information during execution of instructions to be executed by processor modules 210 and 230, respectively. Memory modules 216 and 234 may also include non-volatile memory for storing instructions to be executed by processor modules 210 and 230, respectively.

Network communication module 218 generally represents hardware, software, firmware, processing logic, and/or other components of base station 102 that enable bi-directional communication between base station transceiver 210 and other network components and communication nodes configured to communicate with base station 202. For example, the network communication module 218 may be configured to support Internet or WiMAX services. In a typical deployment, the network communication module 218 provides an 802.3 ethernet interface without any limitation so that the base transceiver station 210 can communicate with a conventional ethernet-based computer network. In this manner, the network communication module 218 may include a physical interface for connecting to a computer network, such as a Mobile Switching Center (MSC). As used herein with respect to a specified operation or function, the term "configured to," "configured to," and variations thereof, refers to a device, component, circuit, structure, machine, signal, etc., that is physically constructed, programmed, formatted, and/or arranged to perform the specified operation or function.

The Open Systems Interconnection (OSI) model (referred to herein as the "open systems interconnection model") is a concept and logical layout that defines network communications used by systems (e.g., wireless communication devices, wireless communication nodes) that disclose interconnections and communications with other systems. The model is divided into seven sub-components or layers, each representing a set of concepts for the services provided to its upper and lower layers. The OSI model also defines a logical network and effectively describes computer packet transport by using different layer protocols. The OSI model may also be referred to as a seven layer OSI model or a seven layer model. In some embodiments, the first layer may be a physical layer. In some embodiments, the second layer may be a Medium Access Control (MAC) layer. In some embodiments, the third layer may be a Radio Link Control (RLC) layer. In some embodiments, the fourth layer may be a Packet Data Convergence Protocol (PDCP) layer. In some embodiments, the fifth layer may be a Radio Resource Control (RRC) layer. In some embodiments, the sixth layer may be a non-access stratum (NAS) layer or an Internet Protocol (IP) layer, and the seventh layer is the other layer.

2.5G Signal Transmission overview

In a wireless communication system, a system bandwidth may be divided into a plurality of frequency domain portions, each occupying a certain amount of frequency domain resources. The size of the frequency domain resources occupied by each frequency domain part may be configured by the network side or predefined by the specification. Each frequency domain portion is also referred to as a listen before talk/Listen Before Talk (LBT) bandwidth, also referred to as a RB set. A guard interval may or may not exist between two consecutive LBT bandwidths. The sender may perform a channel access procedure before sending the signal. If the UE detects that the energy (or power) of the received signal is less than the threshold for a time interval, it may be determined that the current channel is idle and the transmitter may transmit the signal. If the energy (or power) of the received signal is equal to or greater than the threshold, the current channel is considered busy and the sender cannot send the signal. This procedure is known as a channel access procedure, also known as Clear Channel Access (CCA). If a channel idle is detected, the CCA may be considered successful. If a busy channel is detected, the CCA may be deemed to have failed. Channel occupation refers to transmission on a channel by a sender after performing a corresponding channel access procedure. The channel occupation time refers to the total time that the eNB/gNB/UE and any eNB/gNB/UE occupied by the shared channel perform transmission on the channel after the eNB/gNB/UE performs the corresponding channel access procedure.

After the network side successfully performs the CCA (e.g., the network CCA is successful), a signal may be sent. The network side may also inform the UE of preempted channel (e.g., channel occupancy) information including time domain information and/or frequency domain information of the preempted channel (e.g., channel occupancy). The time domain information includes time resource information and/or end time of a preempted channel (e.g., channel occupancy) that the network side or UE may use. Here, we refer to the end time of a preempted channel (e.g., channel occupancy) that can be used by the network side or UE as a COT (channel occupancy time) boundary.

In a wireless communication system, a network side schedules a UE for uplink transmission. The network side transmits all parameters required for uplink transmission of the UE using DCI. That is, uplink transmission is scheduled by DCI. This scheduling method is also called Dynamic Grant (DG). The network transmits all parameters required for uplink transmission of the UE using RRC signaling. That is, uplink transmissions are scheduled by RRC signaling. Or the network transmits a part of parameters required for uplink transmission using RRC signaling and then transmits the remaining parameters required for uplink transmission using DCI. That is, uplink transmission is scheduled by RRC signaling and DCI. Both of these scheduling methods are referred to as Configuration Grants (CG). In the present invention, the uplink transmission scheduled by the network side includes the above-described scheduling methods.

In a wireless communication system, a network side configures time-frequency domain resources of PDCCH for a UE. Furthermore, the time domain resource is a periodic resource. The network side may transmit the PDCCH to the UE on a time-frequency domain resource of each PDCCH. The UE needs to monitor the PDCCH on the time-frequency resources of each PDCCH. Here, each time domain resource that can transmit the PDCCH is also referred to as a PDCCH scheduling occasion.

3. Exemplary embodiments: group 1

In some embodiments, the network side schedules a set of PUSCHs using DCI and/or RRC signaling indicating whether each PUSCH is repeatedly transmitted. In some embodiments, the first indication information in DCI or RRC signaling indicates whether each PUSCH is repeatedly transmitted. In some embodiments, the length of the first indication information is the maximum number of PUSCHs that the network can schedule for the UE. For example, the network side schedules a maximum of 8 PUSCHs using one DCI, and thus the first indication information length is 8. In some embodiments, the first indication information is configured by the network if present in the DCI. The configuration signaling may be MAC CE or RRC signaling. In some embodiments, the length of the first indication information is configured by the network. The configuration signaling may be MAC CE or RRC signaling.

In some embodiments, each information bit corresponds to a scheduled PUSCH. For example, the least significant bit information bits may correspond to a scheduled first PUSCH, the next information bits may correspond to a scheduled second PUSCH, and so on until all scheduled PUSCHs are indicated. As another example, the most significant bit information bits may correspond to a first scheduled PUSCH, the next information bits may correspond to a second PUSCH, and so on until all scheduled PUSCHs are indicated. If there are remaining information bits, none of these information bits are (e.g., no instruction). Thus, from the UE's perspective, the UE may ignore these remaining information bits. The information bit "1" may indicate that the corresponding PUSCH is not repeated transmission. That is, the corresponding PUSCH is initially transmitted. In other words, the corresponding PUSCH is the first transmission during PUSCH indicated by the network. The information bit "0" may indicate that the corresponding PUSCH is repeated transmission. That is, the corresponding PUSCH is not the first transmission during PUSCH indicated by the network. In other words, the corresponding PUSCH carries the same TB as the previous PUSCH.

In some embodiments, an information bit of "0" may indicate that the corresponding PUSCH is not a repeated transmission. The information bit "1" may indicate that the corresponding PUSCH is repeated transmission. In some embodiments, each repeatedly transmitted PUSCH may have the same HARQ process number as the first PUSCH without repeated transmission (e.g., the first PUSCH transmitted initially). In some embodiments, the repeatedly transmitted PUSCH has the same HARQ process number as its previous PUSCH. In some embodiments, the HARQ process number of the first scheduled PUSCH may be indicated in the DCI, and the HARQ process number of each non-repeatedly transmitted PUSCH may be increased by 1. In some embodiments, when the calculated HARQ process number of the PUSCH is greater than or equal to the maximum HARQ process number that can be used by the UE, the UE or the BS may modulo the calculated HARQ process number and then use the modulo number as the HARQ process number of the PUSCH. In some embodiments, the modulo operation finds the remainder of one number divided by the second number. The second number is the maximum HARQ process number that can be used by the UE. In some embodiments, the maximum HARQ process number that can be used by the UE may be configured by the network via DCI, or MAC CE, or RRC signaling or defined by the protocol. In some embodiments, when the calculated HARQ process number of PUSCH is greater than or equal to the maximum HARQ process number that can be used by the UE, the HARQ process number of PUSCH is 0.

Fig. 3 illustrates a block diagram of an example mapping 300 of PUSCH configurations, according to some embodiments of the disclosure. As shown, the DCI schedules 8 PUSCHs (e.g., PUSCH 0-7, respectively), which indicates a first HARQ process number of 14. The maximum HARQ process number that can be used by the UE, configured by the network side, is 16. The length of the information indicated in the DCI is 8. The indication information bit is "11010011". In some embodiments, if the most significant bit of the indication field corresponds to the first scheduled PUSCH and the information bit "1" indicates that the corresponding PUSCH is not repeated transmission, the information bit "0" indicates that the corresponding PUSCH is repeated transmission, the most significant bit "1" indicates that PUSCH 0 is not repeated transmission and the HARQ process is 14. In some embodiments, the next information bit corresponds to the second PUSCH, PUSCH 1. In some embodiments, an information bit of "1" indicates that PUSCH 1 is not a repeated transmission and HARQ process is 15. In some embodiments, the next information bit corresponds to a third PUSCH (e.g., PUSCH 2), and an information bit of "0" indicates that PUSCH 2 is a repeated transmission, the same transport block as PUSCH 1 is repeated transmission, and the HARQ process number of PUSCH 2 is also 15. In other words, PUSCH 2 and PUSCH 1 carry the same transport block. The remainder may be done in the same way.

Fig. 4 shows a table 400 of example transmission schemes and HARQ process numbers for a scheduled PUSCH. If "repeat transmission" is yes, the corresponding PUSCH is repeat transmission. For example, PUSCH 2 is repeated transmission. If "repeat transmission" is no, the corresponding PUSCH is not repeat transmission. For example, PUSCH 0 is not a repeated transmission. "repeated PUSCH" means the first transmission of the corresponding PUSCH. For example, the first transmission of PUSCH 2 is PUSCH 1. The first transmission of PUSCH 4 and 5 is PUSCH 3. In other words, PUSCH 2 and PUSCH 1 carry the same transport block. PUSCH 2 and PUSCH 1 have the same HARQ process number. PUSCH 3, 4 and 5 carry the same transport blocks. PUSCH 3, PUSCH 4 and PUSCH 5 have the same HARQ process number. In some embodiments, the process number of PUSCH 3 is obtained by modulo 16 to 16.

4. Exemplary embodiments: group 2

In some embodiments, a set of PUSCHs is scheduled using DCI and/or RRC signaling. In some embodiments, PUSCHs in the PUSCH group transmitted before the first time interval before the next PDCCH scheduling occasion are transmitted in a repeated transmission. That is, the same transport block is repeatedly transmitted in different PUSCH. In other words, the same transport block is transmitted more than once in different PUSCHs. In some embodiments, PUSCHs in a PUSCH group transmitted after a first time interval before a next PDCCH scheduling occasion are transmitted using a single transmission method. I.e. one transport block is sent only once. In some embodiments, PUSCHs in the PUSCH group transmitted before the second time interval before the COT boundary are transmitted using a single transmission method. In some embodiments, PUSCHs in the PUSCH group transmitted after the second time interval before the COT boundary are transmitted in a repeated transmission. In some embodiments, the first time interval duration and the second time interval duration are configured by the network side or predefined by the protocol. In some embodiments, when two methods collide (e.g., PUSCH is after a first time interval before the next PDCCH scheduling occasion and after a second time interval before the COT boundary, or PUSCH is before a first time interval before the next PDCCH scheduling occasion and before a second time interval before the COT boundary), then PUSCH is transmitted in a repeated transmission. In some embodiments, the first number is the maximum number of times a transport block can be repeatedly transmitted (including the first transmission). In some embodiments, the first number of repeated PUSCH transmissions or the first number of repeated transmissions of the transport block is configured by the network side or specified by the protocol.

Fig. 5 illustrates a block diagram of an example mapping 500 of PUSCH configurations, according to some embodiments of the disclosure. As shown, the network side schedules 8 PUSCHs (respectively PUSCH 0 to 7). The first time interval is 3 slots. PUSCH 0 to 4 is located 3 slots before the next PDCCH scheduling occasion, and PUSCH 0 to 4 is transmitted in a repeated transmission manner. PUSCH 5 to 7 is located within 3 slots before the next PDCCH scheduling occasion, and PUSCH 5 to 7 is transmitted in a single transmission.

Fig. 6 illustrates a block diagram of an example mapping 600 of PUSCH configurations, according to some embodiments of the disclosure. As shown, the network side schedules 8 PUSCHs (respectively PUSCH 0 to 7). The second time interval is 3 time slots. The PUSCH 0-5 is positioned 3 time slots before the COT boundary, and the PUSCH 0-5 is sent in a single sending mode; the PUSCHs 6 to 7 are located within 3 slots before the COT boundary, and the PUSCHs 6 to 7 are transmitted in a repeated transmission manner.

Fig. 7 illustrates a block diagram of an example mapping 700 of PUSCH configurations, according to some embodiments of the disclosure. As shown in fig. 4, 8 PUSCHs (respectively, PUSCH 0 to 7) are scheduled on the network side. The first time interval is configured to be 4 time slots, and the second time interval is configured to be 3 time slots. PUSCH 0-3 is located 4 slots before the next PDCCH scheduling occasion and 4 slots before the COT boundary. The PUSCHs 0 to 3 are transmitted in a repeated transmission manner. PUSCH 4-5 is located 4 slots after the next PDCCH scheduling occasion and 3 slots before the COT boundary. The PUSCHs 4 to 5 are transmitted as a single transmission. PUSCH 6-7 is located 4 slots after the next PDCCH scheduling occasion and 3 slots after the COT boundary. The PUSCHs 6 to 7 are transmitted in a repeated transmission manner.

In some embodiments, a set of PUSCHs is scheduled using DCI and/or RRC signaling. In some embodiments, PUSCHs in a PUSCH group transmitted after a first time interval before a next PDCCH scheduling occasion are transmitted in a repeated transmission. That is, the same transport block is repeatedly transmitted in different PUSCH. In other words, the same transport block is transmitted more than once in different PUSCHs. In some embodiments, PUSCHs in the PUSCH group transmitted before the first time interval before the next PDCCH scheduling occasion are transmitted using a transmission method. I.e. one transport block is sent only once. In some embodiments, PUSCHs in the PUSCH group transmitted after the second time interval before the COT boundary are transmitted using a single transmission method. In some embodiments, PUSCHs in the PUSCH group transmitted before the second time interval before the COT boundary are transmitted in a repeated transmission. In some embodiments, the first time interval duration and the second time interval duration are configured by the network side or predefined by the protocol. In some embodiments, when two methods collide (e.g., PUSCH is after a first time interval before the next PDCCH scheduling occasion and after a second time interval before the COT boundary, or PUSCH is before a first time interval before the next PDCCH scheduling occasion and before a second time interval before the COT boundary), then PUSCH is transmitted in a single transmission. In some embodiments, the first number is the maximum number of times a transport block can be repeatedly transmitted (including the first transmission). In some embodiments, the first number of repeated PUSCH transmissions or the first number of repeated transmissions of the transport block is configured by the network side or specified by the protocol.

In some embodiments, for PUSCH transmitted in a repeated transmission, the transport block is repeated from the first PUSCH until the number of repeated transmissions is equal to the first number of times or there are no more PUSCH resources. In some embodiments, after a transport block is repeatedly transmitted a first number of times, another transport block is repeatedly transmitted starting from the next PUSCH resource. In some embodiments, if a next PUSCH after a PUSCH transmitted in a repeated transmission (the number of repeated transmissions is less than the first number of times) is transmitted in a single transmission, the next PUSCH is the first transmission of a transport block during the scheduled PUSCH. In some embodiments, if the next PUSCH after the PUSCH transmitted in a repeated transmission (the number of repeated transmissions is less than the first number of times) is transmitted in a single transmission, the next PUSCH is a repeated transmission for carrying transport blocks carried by its previous PUSCH until the number of repetitions is equal to the first number of times or no more resources. In some embodiments, the first number is the maximum number of times a transport block can be repeatedly transmitted (including the first transmission).

Still referring to fig. 7, puschs 0 to 3 are transmitted in a repeated transmission manner. The PUSCHs 4 to 5 are transmitted as a single transmission. The PUSCHs 6 to 7 are transmitted in a repeated transmission manner. In some embodiments, if the first number of repeated transmissions is 2 (including the first transmission), PUSCH 0 and 1 transmit the same TB; PUSCH 2 and 3 send the same TB; PUSCH4 sends a TB; PUSCH 5 sends a TB; PUSCH 6 and 7 transmit the same TB. In some embodiments, if the first number of repeated transmissions is 3 (including the first/initial transmission), PUSCH 0-2 transmits the same TB. PUSCH 3 transmits one TB. In some embodiments, PUSCH4 and PUSCH 5 transmit the same TBs as PUSCH 3, since PUSCH4 and 5 are transmitted in a single transmission, and the TBs carried in PUSCH 3 are transmitted only once, less than 3. In some embodiments, PUSCH4 transmits one TB. PUSCH 5 transmits one TB. In some embodiments, PUSCH 6 and PUSCH 7 transmit the same TB. As there are no more PUSCH resources, TBs carried by PUSCH 6 and PUSCH 7 are only sent twice.

In some embodiments, the PUSCH transmitting the same TB has the same HARQ process number, and the HARQ process number is the HARQ process number of the PUSCH transmitting the TB for the first time.

5. Exemplary embodiments: group 3

In some embodiments, there is a relationship between the type of service (e.g., service priority, data priority, etc.) that the uplink signal may carry and the method of transmission. In some embodiments, there is a relationship between uplink transmission priority and transmission method. In some embodiments, the relationship between the type of service (e.g., service priority, data priority, etc.) that the uplink signal may carry and the method of transmission or the relationship between the priority of uplink transmission and the method of transmission is configured by the network side or defined by the protocol. The configuration signaling may be DCI, MAC CE, or RRC signaling. In some embodiments, the UE transmits data (or service) using a corresponding transmission method according to a relationship between a priority of uplink transmission and the transmission method. In some embodiments, the network side configures a set of uplink transmissions for the UE. In some embodiments, a first priority is configured for an uplink transmission group. In other words, the set of uplink transmissions carries data (or services) having a first priority. In some embodiments, when the UE is to transmit data (or service) having the second priority, the UE transmits the data (or service) having the second priority on the PUSCH group using a corresponding transmission method according to a relationship between the priority of uplink transmission and the transmission method. In some embodiments, prior to transmitting data (or services) having a second priority, the UE transmits first indication signaling to indicate that the UE is to transmit data (or services) having a second priority, or to indicate that the UE is to transmit data (or services) having a second priority on the next PUSCH resource. In some embodiments, the first indication signaling may be physical layer signaling, such as Uplink Control Information (UCI), or MAC layer signaling, such as MAC CE or Buffer Status Report (BSR).

In some embodiments, the priority of the data (or service) may be the priority of the logical channel. There is a certain relationship between the priority of the data logical channel and the transmission method. In some embodiments, the UE transmits data (or service) using a corresponding transmission method according to a relationship between a priority of a logical channel of data for uplink transmission and the transmission method.

In some embodiments, this relationship may be to transmit data (or services) having a first priority in a single transmission method and to transmit data (or services) having a second priority in a repeated transmission manner (having a second number of transmissions). The second number of times may be configured by the network side via DCI, or MAC CE, or RRC signaling or predefined by the protocol. In some embodiments, the data (or service) having the first priority may be eMBB data (service). In some embodiments, the data (or service) having the second priority may be URLLC data (service). In some embodiments, the network side configures a set of PUSCHs for the UE. In some embodiments, the set of PUSCHs is configured to transmit data (services) having a first priority. In some embodiments, one or more PUSCHs in the set of PUSCHs transmit (e.g., carry) data (services) having a first priority in a single transmission. In some embodiments, when the UE is to transmit data (service) having the second priority, one or more PUSCHs in the group of PUSCHs transmit (e.g., carry) the data (service) having the second priority in a repeated transmission.

Fig. 8 illustrates a block diagram of an example mapping 800 of PUSCH configurations, according to some embodiments of the disclosure. As shown, eMBB data is sent only once, while URLLC data is sent repeatedly twice. The network side schedules a set of PUSCH transmissions (respectively PUSCH 0-7) for the UE. In some embodiments, the set of PUSCHs is configured to transmit eMBB data. eMBB data is transmitted in a single transmission on PUSCH 0 to 2. The UE has URLLC data to be transmitted during PUSCH 2. In some embodiments, UCI may be multiplexed to PUSCH 3 or a BSR may be transmitted in PUSCH 3 to indicate that the UE has URLLC data to transmit or URLLC data on the next PUSCH resource. In some embodiments, URLLC data is transmitted starting with PUSCH 4 (including PUSCH 4) in a repeated transmission. PUSCH 4 and PUSCH 5 carry the same TBs for URLLC data. PUSCH 6 and PUSCH 7 carry the same TB for URLLC data. In some embodiments, URLLC data is transmitted starting with PUSCH 3 (including PUSCH 3) in a repeated transmission. PUSCH 3 and PUSCH 4 carry the same TBs for URLLC data. PUSCH 5 and PUSCH 6 carry the same TB for URLLC data. PUSCH 7 carries one TB for URLLC data.

In some embodiments, if the UE has URLLC data to transmit before PUSCH 0, URLLC data is transmitted starting with PUSCH 0 (including PUSCH 0) in a repeated transmission. PUSCH 0 and PUSCH 1 carry the same TB for URLLC data. PUSCH 2 and PUSCH 3 carry the same TB for URLLC data. PUSCH 4 and PUSCH 5 carry the same TBs for URLLC data. PUSCH 6 and PUSCH 7 carry the same TB for URLLC data.

6. Exemplary embodiments: group 4

In some embodiments, this relationship may be to transmit data (or services) having a first priority using a first MCS, to transmit data (or services) having a second priority using a second MCS, and so on. In some embodiments, the first MCS, the second MCS (and other MCSs) are configured by the network side via DCI, or MAC CE, or RRC signaling. In some embodiments, the network side configures a set of PUSCHs for the UE. In some embodiments, the set of PUSCHs is configured to transmit data (services) having a first priority. In some embodiments, one or more PUSCHs in the set of PUSCHs transmit data (services) having a first priority using a first MCS. In some embodiments, when the UE is to transmit data (service) with a second priority, one or more PUSCHs in the group of PUSCHs transmit data (service) with the second priority using the second MCS.

Still referring to fig. 8, in some embodiments, the configuration uses MCS1 to transmit eMBB the service and MCS2 to transmit URLLC the service. In some embodiments, the network side schedules a set of PUSCH transmissions (PUSCH 0-7, respectively) for the UE. In some embodiments, the set of PUSCHs is configured to transmit eMBB data. In some embodiments, eMBB data is transmitted on PUSCH 0-2 using MCS 1. The UE has URLLC data to be transmitted during PUSCH 2. In some embodiments, UCI may be multiplexed to PUSCH 3 or to send BSR in PUSCH 3 to indicate that the UE has URLLC data to send or to send URLLC data on the next PUSCH resource. In some embodiments, URLLC data is transmitted starting from PUSCH 4 (including PUSCH 4) by using MCS 2. In other words, URLLC data are transmitted on the PUSCHs 4 to 7, respectively, by using MCS 2. In some embodiments, URLLC data is transmitted starting from PUSCH 3 (including PUSCH 3) by using MCS 2. In other words, URLLC data are transmitted on PUSCH 3 to 7, respectively, by using MCS 2.

In some embodiments, if the UE has URLLC data to transmit before PUSCH 0, URLLC data is transmitted starting from PUSCH 0 (including PUSCH 0) by using MCS 2. In other words, URLLC data are transmitted on PUSCH 0 to 7, respectively, by using MCS 2.

7. Exemplary embodiments: group 5

In some embodiments, this relationship may be to transmit data (or services) with a first priority in a single transmission, and to transmit data (or services) with a second priority in a repeated transmission (with a second number of transmissions) by using a first MCS, and so on. In some embodiments, the first MCS, the second MCS (and other MCSs) are configured by the network side via DCI, or MAC CE, or RRC signaling. The second number of times may be configured by the network side via DCI, or MAC CE, or RRC signaling or predefined by the protocol. In some embodiments, the network side configures a set of PUSCHs for the UE. In some embodiments, the set of PUSCHs is configured to transmit data (services) having a first priority. In some embodiments, one or more PUSCHs in the set of PUSCHs transmit data (services) having the first priority only once using the first MCS. In some embodiments, when the UE is to transmit data (service) having a second priority, one or more PUSCHs in the group of PUSCHs transmit the data (service) having the second priority in a repeated transmission manner using the second MCS.

Still referring to fig. 8, in some embodiments, the configuration uses MCS1 to transmit eMBB data only once and MCS2 to transmit URLLC services twice. The network side schedules a set of PUSCH transmissions (respectively PUSCH 0-7) for the UE. In some embodiments, the set of PUSCHs is configured to transmit eMBB data. In some embodiments, eMBB data is transmitted once on PUSCH 0-2 by using MCS1 only. In other words, PUSCH 0, PUSCH 1, PUSCH 2 each carry one TB for eMBB data. The UE has URLLC data to be transmitted during PUSCH 2. In some embodiments, UCI may be multiplexed to PUSCH 3 or a BSR may be sent in PUSCH 3 to indicate that the UE is to send URLLC data or URLLC data on the next PUSCH resource. In some embodiments, URLLC data is repeatedly transmitted starting from PUSCH 4 (including PUSCH 4) by using MCS2. In other words, PUSCH 4 and PUSCH 5 carrying the same TB for URLLC data are transmitted by using MCS2. PUSCH 6 and PUSCH 7 carrying the same TB for URLLC data are transmitted by using MCS2. In some embodiments, URLLC data is repeatedly transmitted starting from PUSCH 3 (including PUSCH 3) by using MCS2. In other words, PUSCH 3 and PUSCH 4 carrying the same TB for URLLC data are transmitted by using MCS2. By using MCS2. PUSCH 5 and PUSCH 6 carrying the same TB for URLLC data are transmitted. By using MCS2, PUSCH 7 carrying one TB for URLLC data is transmitted and the TB is transmitted only once.

In some embodiments, if the UE has URLLC to transmit before PUSCH 0, URLLC data is repeatedly transmitted starting from PUSCH 0 (including PUSCH 0) through MCS 2. In other words, PUSCH 0 and PUSCH 1 carrying the same TB for URLLC data are transmitted by using MCS 2. PUSCH 2 and PUSCH 3 carrying the same TB for URLLC data are transmitted by using MCS 2. PUSCH 4 and PUSCH 5 carrying the same TB for URLLC data are transmitted by using MCS 2. PUSCH 6 and PUSCH 7 carrying the same TB for URLLC data are transmitted by using MCS 2.

In some embodiments, the network may configure the UE with one or more configurations for uplink signaling. The UE may use one of the configurations to transmit uplink signals. In some embodiments, the network may configure the UE with one or more configurations for PUSCH transmission. The UE may transmit PUSCH using one of the configurations. In some embodiments, the network may configure a Time Domain Resource Allocation (TDRA) configuration for the UE for PUSCH. TDRA configurations may include one or more time resource configurations for uplink signaling. In some embodiments, the time resource configuration may include at least a start and a length of the resource in the time domain. In some embodiments, the time resource configuration may be indicated by a Start and Length Indication Value (SLIV). The UE may transmit PUSCH using one of the time resource configurations. In some embodiments, the uplink signal configuration of the UE may be configured via DCI, or MAC CE, or RRC signaling. In some embodiments, if the time domain resource of PUSCH crosses a slot boundary according to the start and length of the time domain resource, the time domain resource should start from the indicated start symbol and end at the slot boundary. In some embodiments, if the time domain resources of the PUSCH cross slot boundaries according to the start and length of the time domain resources, the nominal repetition of the PUSCH may be split into two actual repetitions. In some embodiments, a PUSCH may be split into two PUSCHs if the time domain resources of the PUSCH cross slot boundaries according to the start and length of the time domain resources.

Fig. 9 illustrates a table of an example mapping 900 of PUSCH configurations in accordance with some embodiments of the disclosure. As shown in fig. 9, TDRA index indicates TDRA configuration. TDRA configuration 0 includes 5 configurations of time domain resources of PUSCH. For 5 configurations of time domain resources, the starting symbols are symbols 0, 1,2,3, 5, respectively. The length of the 5 configurations of the time domain resource is 14 OFDM symbols. TDRA configuration 0 is configured to transmit PUSCH. The UE may transmit PUSCH using each of the 5 configurations of the time domain. In other words, the UE may transmit PUSCH starting from any of symbols 0 to 4. In some embodiments, the UE detects that the channel is idle before symbol 0. The UE may transmit PUSCH on a time domain resource of length 14 OFDM symbols and starting from symbol 0. In some embodiments, the UE detects that the channel is idle before symbol 2. The UE may transmit PUSCH on a time domain resource of length 14 OFDM symbols and starting from symbol 2.

In some embodiments, the network may configure more than one configuration grant resource for the UE. In some embodiments, the plurality of dynamic grant resources of PUSCH are configured by the same method used to configure the plurality of configuration grant resources. In some embodiments, the dynamic resource configuration may include more than one frequency domain resource configuration. In some embodiments, multiple dynamic resources may have the same time domain resource and different frequency time resources. In some embodiments, if the time domain resources of the plurality of dynamic resources are the same as the time domain resources of the network schedule, the UE may select any one of the plurality of dynamic resources to transmit the uplink signal. In some embodiments, multiple dynamic resources may have the same frequency domain resources. The time domain resource offset of two adjacent dynamic resources is D. In some embodiments, the value of D is configured by the network via DCI, or MAC CE, or RRC signaling.

In some embodiments, (also referred to herein as "method 1"), the network configures multiple PUSCHs (e.g., K PUSCHs) for the UE. If the UE detects that the channel is idle, only one PUSCH is transmitted or the K1PUSCH is repeatedly transmitted and the rest of the channels are released. In other words, after transmitting only one PUSCH or repeatedly transmitting K1PUSCH, the UE may not transmit anything (not transmit K-1PUSCH or K-K1 PUSCH). In some embodiments, (also referred to herein as "method 2"), the network configures the UE with multiple PUSCHs. If the UE detects that the channel is idle, the UE may send an uplink signal on the configured resources. In some embodiments, for aperiodic URLLC services, when URLLC services are sparse, the UE uses method 1 to transmit uplink signals. In other words, the UE transmits only one PUSCH or transmits K1PUSCH and releases the remaining channels. In some embodiments, the network may instruct the UE which method to use to transmit the uplink signal via DCI, or MAC CE, or RRC signaling. According to the embodiment, the transmission opportunity of the dynamic PUSCH can be increased. Accordingly, the probability and reliability of dynamic PUSCH can be increased. Flexibility of scheduling can be increased.

In some embodiments, only the PRACH of the second cell is transmitted when the uplink signal (e.g., PUCCH, PUSCH, SRS, PRACH, etc.) of the first cell overlaps with the PRACH of the second cell, at least in the time or frequency domain. In other words, no uplink signal is sent (e.g., dropped). In some embodiments, only the PRACH of the second cell is transmitted when the uplink signal of the first cell (e.g., PUCCH, PUSCH, SRS, PRACH, etc.) or a portion of the uplink signal of the first cell is within a time slot in which the PRACH of the second cell may be transmitted. In other words, no uplink signal is sent (e.g., dropped). In some embodiments, the PRACH of the second cell is only transmitted when the PRACH of the second cell or a portion of the PRACH of the second cell is within a time slot of the first cell where the uplink signal (e.g., PUCCH, PUSCH, SRS, PRACH, etc.) of the first cell may be transmitted. In other words, no uplink signal is sent (e.g., dropped). In some embodiments, the PRACH of the second cell is only transmitted when the first or last symbol of the uplink signal (e.g., PUCCH, PUSCH, SRS, PRACH, etc.) of the first cell is separated from the last or first symbol of the PRACH of the second cell by less than Z symbols. In other words, no uplink signal is sent (e.g., dropped). In some embodiments, the first cell may be a source cell or a source Master Cell Group (MCG) during handover. In some embodiments, the second cell may be a target cell or a target MCG. In some embodiments, the value of Z is predefined by the protocol or configured by the network via DCI, or MAC CE, or RRC signaling. In some embodiments, the value of Z may be determined from the uplink subcarrier spacing. In some embodiments, the value of Z may be determined from the maximum or maximum subcarrier spacing of the uplink bandwidth portions of the source cell (source MCG) and the target cell (TARGET MCG).

8. Methods for implementing exemplary embodiments of groups 1-5

Fig. 10 is a flow chart illustrating a method for satisfying delay and reliability requirements of signal transmission for ultra-reliable low-delay communication (URLLC) from the perspective of a UE, according to some embodiments of the present disclosure. Additional, fewer, or different operations may be performed in the method, depending on the particular embodiment. In some embodiments, some or all of the operations of method 1000 may be performed by a wireless communication node, such as BS102 in fig. 1. In some operations, some or all of the operations of method 1000 may be performed by a wireless communication device, such as UE 104 in fig. 1. Each operation may be reordered, added, deleted, or repeated.

As shown, in some embodiments, method 1000 includes an operation 1002 of receiving, by a wireless communication device from a wireless communication node, a control signal indicating whether to repeatedly transmit each of a plurality of uplink channels on an unlicensed frequency band. In some embodiments, the method includes an operation 1004 of transmitting, by the wireless communication device, a plurality of uplink channels to the wireless communication node, respectively, based on the control signal.

Fig. 11 is a flow chart illustrating a method for satisfying the latency and reliability requirements of signal transmission for ultra-reliable low-latency communications (URLLC) from the perspective of a UE, according to some embodiments of the present disclosure. Additional, fewer, or different operations may be performed in the method, depending on the particular embodiment. In some embodiments, some or all of the operations of method 1100 may be performed by a wireless communication node, such as BS102 in fig. 1. In some operations, some or all of the operations of method 1100 may be performed by a wireless communication device, such as UE 104 in fig. 1. Each operation may be reordered, added, deleted, or repeated.

As shown, in some embodiments, method 1100 includes an operation 1102 of receiving, by a wireless communication device from a wireless communication node, a control signal indicating a plurality of service types and a plurality of methods. In some embodiments, the method includes an operation 1104 of determining, by the wireless communication device, one of a plurality of methods corresponding to one of the plurality of service types based on the control signal. In some embodiments, the method includes an operation 1106 of transmitting, by the wireless communication device, each of the plurality of uplink channels to the wireless communication node using a respective one of a plurality of methods.

Fig. 12 is a flow chart illustrating a method for satisfying delay and reliability requirements of signal transmission for ultra-reliable low-delay communication (URLLC) from the perspective of a BS, according to some embodiments of the present disclosure. Additional, fewer, or different operations may be performed in the method, depending on the particular embodiment. In some embodiments, some or all of the operations of method 1200 may be performed by a wireless communication node, such as BS102 in fig. 1. In some operations, some or all of the operations of method 1200 may be performed by a wireless communication device, such as UE 104 in fig. 1. Each operation may be reordered, added, deleted, or repeated.

As shown, in some embodiments, the method 1200 includes an operation 1202 of transmitting, by the wireless communication node to the wireless communication device, a control signal indicating whether to repeatedly transmit each of the plurality of uplink channels on the unlicensed frequency band. In some embodiments, the method includes an operation 1204 of receiving, by the wireless communication node, a plurality of uplink channels from the wireless communication device in response to the transmission of the control signal.

Fig. 13 is a flow chart illustrating a method for satisfying delay and reliability requirements of signal transmission for ultra-reliable low-delay communication (URLLC) from the perspective of a BS, according to some embodiments of the present disclosure. Additional, fewer, or different operations may be performed in the method, depending on the particular embodiment. In some embodiments, some or all of the operations of method 1300 may be performed by a wireless communication node, such as BS102 in fig. 1. In some operations, some or all of the operations of method 1300 may be performed by a wireless communication device, such as UE 104 in fig. 1. Each operation may be reordered, added, deleted, or repeated.

As shown, in some embodiments, the method 1300 includes an operation 1302 of transmitting, by a wireless communication node to a wireless communication device, a control signal indicating a plurality of service types and a plurality of methods, wherein the control signal causes the wireless communication device to: one of a plurality of methods corresponding to one of the plurality of service types is determined based on the control signal, and each of the plurality of uplink channels is transmitted to the wireless communication node using a respective one of the plurality of methods. In some embodiments, the method includes an operation 1304 of receiving, by the wireless communication node, a plurality of uplink channels from the wireless communication device.

While various embodiments of the present solution have been described above, it should be understood that they have been presented by way of example only, and not limitation. Likewise, various diagrams may depict example architectures or configurations provided to enable one of ordinary skill in the art to understand the example features and functionality of the present solution. However, those skilled in the art will appreciate that the present solution is not limited to the example architecture or configuration shown, but may be implemented using a variety of alternative architectures and configurations. In addition, one of ordinary skill in the art will understand that one or more features of one embodiment can be combined with one or more features of another embodiment described herein. Thus, the breadth and scope of the present disclosure should not be limited by any of the above-described illustrative embodiments.

It should also be appreciated that any reference herein to an element using designations such as "first," "second," etc. generally does not limit the number or order of such elements. Rather, these designations may be used herein as a convenient means of distinguishing between two or more elements or between multiple instances of an element. Thus, reference to first and second elements does not mean that only two elements can be employed, nor that the first element must somehow precede the second element.

Furthermore, those of ordinary skill in the art would understand that information and signals may be represented using any of a variety of different technologies and techniques. For example, data, instructions, commands, information, signals, bits, and symbols, for example, referenced throughout the above description may be represented by voltages, currents, electromagnetic waves, magnetic fields or particles, optical fields or particles, or any combination thereof.

Those of ordinary skill would further appreciate that any of the various illustrative logical blocks, modules, processors, devices, circuits, methods, and functions described in connection with the aspects disclosed herein may be implemented as electronic hardware (e.g., a digital implementation, an analog implementation, or a combination of both), firmware, various forms of program (e.g., a computer program product) or design code containing instructions (referred to herein as "software" or "a software module" for convenience), or any combination of these techniques. To clearly illustrate this interchangeability of hardware, firmware, and software, various illustrative components, blocks, modules, circuits, and steps have been described above generally in terms of their functionality. Whether such functionality is implemented as hardware, firmware, or software, or a combination of such techniques depends upon the particular application and design constraints imposed on the overall system. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present disclosure.

Moreover, those of ordinary skill in the art will appreciate that the various illustrative logical blocks, modules, devices, components, and circuits described herein may be implemented within or performed by an Integrated Circuit (IC) comprising a general purpose processor, a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), a Field Programmable Gate Array (FPGA), or other programmable logic device, or any combination thereof. The logic, modules, and circuitry may further include an antenna and/or transceiver to communicate with various components within the network or within the device. A general purpose processor may be a microprocessor, but in the alternative, the processor may be any conventional processor, controller, or state machine. A processor may also be implemented as a combination of computing devices, e.g., a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a DSP core, or any other suitable configuration to perform the functions described herein.

If implemented in software, the functions may be stored on a computer-readable medium as one or more instructions or code. Thus, the steps of a method or algorithm disclosed herein may be implemented as software stored on a computer readable medium. Computer-readable media includes both computer storage media and communication media including any medium that enables transmission of a computer program or code from one place to another. A storage media may be any available media that can be accessed by a computer. By way of example, and not limitation, such computer-readable media can comprise RAM, ROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other medium that can be used to store desired program code in the form of instructions or data structures and that can be accessed by a computer.

As used herein, the term "module" refers to software, firmware, hardware, and any combination of these elements for performing the related functions described herein. In addition, for purposes of discussion, the various modules are described as discrete modules. However, it will be apparent to one of ordinary skill in the art that two or more modules may be combined to form a single module that performs the relevant functions in accordance with embodiments of the present solution.

Additionally, in embodiments of the present solution, memory or other storage devices and communication components may be employed. It will be appreciated that for clarity, the above description has described embodiments of the present solution with reference to different functional units and processors. However, it will be apparent that any suitable distribution of functionality between different functional units, processing logic elements or domains may be used without detracting from the present solution. For example, functions illustrated as being performed by separate processing logic elements or controllers may be performed by the same processing logic elements or controllers. Thus, references to specific functional units are only references to suitable means for providing the described functionality rather than indicative of a strict logical or physical structure or organization.

Various modifications to the embodiments described in this disclosure will be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other embodiments without departing from the scope of this disclosure. Thus, the present disclosure is not intended to be limited to the embodiments shown herein but is to be accorded the widest scope consistent with the novel features and principles disclosed herein as set forth in the following claims.

Claims (10)

1. A method of signal cancellation, comprising:

Determining that at least a portion of a PRACH (physical random ACCESS CHANNEL) signal of a second cell is located within the first cell time slot in which an uplink signal of a first cell may be transmitted, or that a first or last symbol of the uplink signal of the first cell is separated from a last or first symbol of the PRACH signal of the second cell by less than Z symbols;

The uplink signal of the first cell is not transmitted.

2. The method of claim 1, wherein the uplink signal comprises a Physical Uplink Control Channel (PUCCH), a Physical Uplink Shared Channel (PUSCH), or a Sounding Reference Signal (SRS).

3. The method of claim 1, the value of Z being determined according to a subcarrier spacing of the uplink signal.

4. The method of claim 1, the first cell is a source primary cell group.

5. The method of claim 1, the second cell is a target primary cell group.

6. A method of signal cancellation, comprising:

Determining that at least a portion of a PRACH (physical random ACCESS CHANNEL) signal of a second cell is located within the first cell time slot in which an uplink signal of a first cell may be transmitted, or that a first or last symbol of the uplink signal of the first cell is separated from a last or first symbol of the PRACH signal of the second cell by less than Z symbols;

the uplink signal of the first cell is not received.

7. The method of claim 6, wherein the uplink signal comprises a Physical Uplink Control Channel (PUCCH), a Physical Uplink Shared Channel (PUSCH), or a Sounding Reference Signal (SRS).

8. The method of claim 6, the value of Z is determined according to a subcarrier spacing of the uplink signal.

9. The method of claim 6, the first cell is a source primary cell group.

10. The method of claim 6, the second cell is a target primary cell group.