[go: up one dir, main page]

WO2021098055A1 - Système et procédé de transmission de signal - Google Patents

Système et procédé de transmission de signal Download PDF

Info

Publication number
WO2021098055A1
WO2021098055A1 PCT/CN2020/075360 CN2020075360W WO2021098055A1 WO 2021098055 A1 WO2021098055 A1 WO 2021098055A1 CN 2020075360 W CN2020075360 W CN 2020075360W WO 2021098055 A1 WO2021098055 A1 WO 2021098055A1
Authority
WO
WIPO (PCT)
Prior art keywords
wireless communication
uplink channels
subset
time
control signal
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Ceased
Application number
PCT/CN2020/075360
Other languages
English (en)
Inventor
Shuaihua KOU
Peng Hao
Jing Shi
Wei Gou
Xianghui HAN
Junfeng Zhang
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
ZTE Corp
Original Assignee
ZTE Corp
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by ZTE Corp filed Critical ZTE Corp
Priority to CN202080092797.6A priority Critical patent/CN114930951B/zh
Priority to PCT/CN2020/075360 priority patent/WO2021098055A1/fr
Publication of WO2021098055A1 publication Critical patent/WO2021098055A1/fr
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
    • H04L1/18—Automatic repetition systems, e.g. Van Duuren systems
    • H04L1/1867—Arrangements specially adapted for the transmitter end
    • H04L1/189—Transmission or retransmission of more than one copy of a message
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
    • H04L1/18—Automatic repetition systems, e.g. Van Duuren systems
    • H04L1/1822—Automatic repetition systems, e.g. Van Duuren systems involving configuration of automatic repeat request [ARQ] with parallel processes
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
    • H04L1/18—Automatic repetition systems, e.g. Van Duuren systems
    • H04L1/1867—Arrangements specially adapted for the transmitter end
    • H04L1/1896—ARQ related signaling
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/04—Wireless resource allocation
    • H04W72/044—Wireless resource allocation based on the type of the allocated resource
    • H04W72/0446—Resources in time domain, e.g. slots or frames
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/20—Control channels or signalling for resource management
    • H04W72/23—Control channels or signalling for resource management in the downlink direction of a wireless link, i.e. towards a terminal

Definitions

  • the disclosure relates generally to wireless communications and, more particularly, to systems and methods for meeting the delay and reliability requirements for signal transmission for Ultra-Reliable Low Latency Communication (URLLC) .
  • URLLC Ultra-Reliable Low Latency Communication
  • a 5G NR system supports various services, such as the Ultra-Reliable Low-Latency Communication (URLLC) service.
  • the URLLC service provides support for high reliability and low latency services. In some instances, the URLLC service may provide reliability as high as a 99.9999%block error rate with its air interface transmission delay within 1 millisecond.
  • example embodiments disclosed herein are directed to solving the issues relating to one or more of the problems presented in the prior art, as well as providing additional features that will become readily apparent by reference to the following detailed description when taken in conjunction with the accompany drawings.
  • example systems, methods, devices and computer program products are disclosed herein. It is understood, however, that these embodiments are presented by way of example and are not limiting, and it will be apparent to those of ordinary skill in the art who read the present disclosure that various modifications to the disclosed embodiments can be made while remaining within the scope of this disclosure.
  • a method includes receiving, by a wireless communication device (e.g., UE 104 in FIG. 1) from a wireless communication node (e.g., BS 102 in FIG. 1) , a control signal indicating whether to repetitively transmit each of a plurality of uplink channels (e.g., one or more PUSCHs) on an unlicensed band.
  • the method includes respectively transmitting, by the wireless communication device to the wireless communication node, the plurality of uplink channels based on the control signal.
  • a method in another embodiments, 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 approaches. In some embodiments, the method includes determining, by the wireless communication device according to the control signal, one of the plurality of approaches corresponding to one of the plurality of service types. In some embodiments, the method includes transmitting, by the wireless communication device to the wireless communication node, each of the plurality of uplink channels using a respective one of the approaches.
  • a method include transmitting, by a wireless communication node to a wireless communication device, a control signal indicating whether to repetitively transmit each of a plurality of uplink channels on an unlicensed band.
  • a method include receiving, by the wireless communication node from the wireless communication device and responsive to transmitting the control signal, the plurality of uplink channels.
  • a method in another embodiment, includes transmitting, by a wireless communication node to a wireless communication device, a control signal indicating a plurality of service types and a plurality of approaches.
  • the control signal causes the wireless communication device to: determine, according to the control signal, one of the plurality of approaches corresponding to one of the plurality of service types.
  • 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 approaches.
  • the method includes receiving, by the wireless communication node from the wireless communication device, the plurality of uplink channels.
  • FIG. 1 illustrates an example cellular communication network in which techniques disclosed herein may be implemented, in accordance with an embodiment of the present disclosure.
  • FIG. 2 illustrates block diagrams of an example base station and a user equipment device, in accordance with some embodiments of the present disclosure.
  • FIG. 3 illustrates a block diagram of an example mapping of a PUSCH configuration, in accordance with some embodiments of the present disclosure.
  • FIG. 4 illustrates a table of example sending situations and HARQ process numbers for a PUSCH, in accordance with an embodiment of the present disclosure.
  • FIG. 5 illustrates a block diagram of an example mapping of a PUSCH configuration, in accordance with some embodiments of the present disclosure.
  • FIG. 6 illustrates a block diagram of an example mapping of a PUSCH configuration, in accordance with some embodiments of the present disclosure.
  • FIG. 7 illustrates a block diagram of an example mapping of a PUSCH configuration, in accordance with some embodiments of the present disclosure.
  • FIG. 8 illustrates a block diagram of an example mapping of a PUSCH configuration, in accordance with some embodiments of the present disclosure.
  • FIG. 9 illustrates a table of an example mapping 900 of a PUSCH configuration, in accordance with some embodiments of the present disclosure.
  • FIG. 10 is a flow diagram depicting a method for meeting the delay and reliability requirements for signal transmission for Ultra-Reliable Low Latency Communication (URLLC) from the perspective of a UE, in accordance with some embodiments of the present disclosure.
  • URLLC Ultra-Reliable Low Latency Communication
  • FIG. 11 is a flow diagram depicting a method for meeting the delay and reliability requirements for signal transmission for Ultra-Reliable Low Latency Communication (URLLC) from the perspective of a UE, in accordance with some embodiments of the present disclosure.
  • URLLC Ultra-Reliable Low Latency Communication
  • FIG. 12 is a flow diagram depicting a method for meeting the delay and reliability requirements for signal transmission for Ultra-Reliable Low Latency Communication (URLLC) from the perspective of a BS, in accordance with some embodiments of the present disclosure.
  • URLLC Ultra-Reliable Low Latency Communication
  • FIG. 13 is a flow diagram depicting a method for meeting the delay and reliability requirements for signal transmission for Ultra-Reliable Low Latency Communication (URLLC) from the perspective of a BS, in accordance with some embodiments of the present disclosure.
  • URLLC Ultra-Reliable Low Latency Communication
  • the future wireless communication system (e.g., 5G NR) supports various services, such as the Ultra-Reliable Low-Latency Communication (URLLC) service.
  • the URLLC service provides support for high reliability and low latency services.
  • the URLLC service may provide reliability as high as a 99.9999%block error rate with its air interface transmission delay within 1 millisecond.
  • the URLLC service may be incapable of providing such a high reliability rate in instances when the network side (e.g., BS 102 in FIG. 1) schedules multiple PUSCHs for signal transmission. For example, if the UE only preempts a part of the frequency domain resources of the PUSCH frequency domain resources, then it may be difficult to determine how to perform the signal transmission during this time. That is, if the URLLC data arrives in the middle of PUSCH transmission and if the URLLC data is scheduled again after the PUSCH transmission ends, then the delay requirements for URLLC may not be met. Thus, a mechanism is needed for determining how to achieve the delay requirements necessary for URLLC to provide high reliability when the signal transmission occurs on the current PUSCH.
  • the systems and methods discussed herein provide a mechanism for meeting (e.g., satisfying, etc. ) the delay and reliability requirements for signal transmission for URLLC.
  • the UE when the UE performs CCA successfully on part of the LBT bandwidth, the UE may send (e.g., transmit, deliver, etc. ) a PUSCH.
  • the UE may determine repeated transmission of PUSCH according to PDCCH transmission mechanism and/or a COT boundary. In some embodiments, the UE may determine repetitive transmission of PUSCH according to the configuration from the network. In some embodiments, the UE may determine repetitive transmission of PUSCH according to the service type of data that UE transmits. In some embodiments, the HARQ process number of the repeatedly sent PUSCH may be the HARQ process number of the previous PUSCH. In some embodiments, the HARQ process number changes only on initially transmitted PUSCH.
  • the UE may determine the MCS for PUSCH transmission according to the configuration from the network. In some embodiments, the UE may determine the MCS for PUSCH transmission according to the service type of data that UE transmits.
  • FIG. 1 illustrates an example wireless communication network, and/or system, 100 in which techniques disclosed herein may be implemented, in accordance with an embodiment of the present disclosure.
  • 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 herein referred to as “network 100.
  • NB-IoT narrowband Internet of things
  • Such an example network 100 includes a base station 102 (hereinafter “BS 102” ; also referred to as wireless communication node) and a user equipment device 104 (hereinafter “UE 104” ; also referred to as wireless communication device) that can communicate with each other via a communication link 110 (e.g., a wireless communication channel) , and a cluster of cells 126, 130, 132, 134, 136, 138 and 140 overlaying a geographical area 101.
  • the BS 102 and UE 104 are contained within a respective geographic boundary of cell 126.
  • Each of the other cells 130, 132, 134, 136, 138 and 140 may include at least one base station operating at its allocated bandwidth to provide adequate radio coverage to its intended users.
  • the BS 102 may operate at an allocated channel transmission bandwidth to provide adequate coverage to the UE 104.
  • the BS 102 and the UE 104 may communicate via a downlink radio frame 118, and an uplink radio frame 124 respectively.
  • Each radio frame 118/124 may be further divided into sub-frames 120/127 which may include data symbols 122/128.
  • the BS 102 and UE 104 are described herein as non-limiting examples of “communication nodes, ” generally, which can practice the methods disclosed herein. Such communication nodes may be capable of wireless and/or wired communications, in accordance with various embodiments of the present solution.
  • 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 operating features that need not be described in detail herein.
  • system 200 can be used to communicate (e.g., transmit and receive) data symbols in a wireless communication environment such as the wireless communication environment 100 of Figure 1, as described above.
  • the System 200 generally includes a base station 202 (hereinafter “BS 202” ) and a user equipment device 204 (hereinafter “UE 204” ) .
  • the BS 202 includes a BS (base station) transceiver module 210, a BS antenna 212, a BS processor module 214, a BS memory module 216, and a network communication module 218, each module being coupled and interconnected with one another as necessary via a 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 module being coupled and interconnected with one another as necessary via a data communication bus 240.
  • the BS 202 communicates with the UE 204 via a communication channel 250, which can be any wireless channel or other medium suitable for transmission of data as described herein.
  • system 200 may further include any number of modules other than the modules shown in Figure 2.
  • modules other than the modules shown in Figure 2.
  • Those skilled in the art will understand that the various illustrative blocks, modules, circuits, and processing logic described in connection with the embodiments disclosed herein may be implemented in 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 are described generally in terms of their functionality. Whether such functionality is implemented as hardware, firmware, or software can depend upon the particular application and design constraints imposed on the overall system. Those familiar with the concepts described herein may implement such functionality in a suitable manner for each particular application, but such implementation decisions should not be interpreted as limiting the scope of the present disclosure
  • the UE transceiver 230 may be referred to herein as an "uplink" transceiver 230 that includes a radio frequency (RF) transmitter and a RF receiver each comprising circuitry that is coupled to the antenna 232.
  • a duplex switch (not shown) may alternatively couple the uplink transmitter or receiver to the uplink antenna in time duplex fashion.
  • the BS transceiver 210 may be referred to herein as a "downlink" transceiver 210 that includes a RF transmitter and a RF receiver each comprising circuity that is coupled to the antenna 212.
  • a downlink duplex switch may alternatively couple the downlink transmitter or receiver to the downlink antenna 212 in time duplex fashion.
  • the operations of the two transceiver modules 210 and 230 may be coordinated in time such that the uplink receiver circuitry is coupled to the uplink antenna 232 for reception of transmissions over the wireless transmission link 250 at the same time that the downlink transmitter is coupled to the downlink antenna 212. Conversely, the operations of the two transceivers 210 and 230 may be coordinated in time such that the downlink receiver is coupled to the downlink antenna 212 for reception of transmissions over the wireless transmission link 250 at the same time that the uplink transmitter is coupled to the uplink antenna 232. In some embodiments, there is close time synchronization with a minimal guard time between changes in duplex direction.
  • the UE transceiver 230 and the base station transceiver 210 are configured to communicate via the wireless data communication link 250, and cooperate with a suitably configured RF antenna arrangement 212/232 that can support a particular wireless communication protocol and modulation scheme.
  • the UE transceiver 210 and the base station transceiver 210 are configured to support industry standards such as the Long Term Evolution (LTE) and emerging 5G standards, and the like. It is understood, however, that the present disclosure is not necessarily limited in application to a particular standard and associated protocols. Rather, the UE transceiver 230 and the base station transceiver 210 may be configured to support alternate, or additional, wireless data communication protocols, including future standards or variations thereof.
  • LTE Long Term Evolution
  • 5G 5G
  • the BS 202 may be an evolved node B (eNB) , a serving eNB, a target eNB, a femto station, or a pico station, for example.
  • eNB evolved node B
  • the UE 204 may be embodied in various types of user devices such as a mobile phone, a smart phone, a personal digital assistant (PDA) , tablet, laptop computer, wearable computing device, etc.
  • PDA personal digital assistant
  • the processor modules 214 and 236 may be implemented, or realized, with a general purpose processor, a content addressable memory, a digital signal processor, an application specific integrated circuit, a field programmable gate array, any suitable programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof, designed to perform the functions described herein.
  • a processor may be realized as a microprocessor, a controller, a microcontroller, a 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.
  • 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 processor modules 214 and 236, respectively, or in any practical combination thereof.
  • the memory modules 216 and 234 may be realized 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.
  • memory modules 216 and 234 may be coupled to the processor modules 210 and 230, respectively, such that the processors modules 210 and 230 can read information from, and write information to, memory modules 216 and 234, respectively.
  • the memory modules 216 and 234 may also be integrated into their respective processor modules 210 and 230.
  • the 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 each include non-volatile memory for storing instructions to be executed by the processor modules 210 and 230, respectively.
  • the network communication module 218 generally represents the hardware, software, firmware, processing logic, and/or other components of the base station 202 that enable bi-directional communication between base station transceiver 210 and other network components and communication nodes configured to communication with the base station 202.
  • network communication module 218 may be configured to support internet or WiMAX traffic.
  • network communication module 218 provides an 802.3 Ethernet interface such that base station transceiver 210 can communicate with a conventional Ethernet based computer network.
  • the network communication module 218 may include a physical interface for connection to the computer network (e.g., Mobile Switching Center (MSC) ) .
  • MSC Mobile Switching Center
  • the Open Systems Interconnection (OSI) Model (referred to herein as, “open system interconnection model” ) is a conceptual and logical layout that defines network communication used by systems (e.g., wireless communication device, wireless communication node) open to interconnection and communication with other systems.
  • the model is broken into seven subcomponents, or layers, each of which represents a conceptual collection of services provided to the layers above and below it.
  • the OSI Model also defines a logical network and effectively describes computer packet transfer by using different layer protocols.
  • the OSI Model may also be referred to as the seven-layer OSI Model or the seven-layer model.
  • a first layer may be a physical layer.
  • a second layer may be a Medium Access Control (MAC) layer.
  • MAC Medium Access Control
  • a third layer may be a Radio Link Control (RLC) layer.
  • a fourth layer may be a Packet Data Convergence Protocol (PDCP) layer.
  • PDCP Packet Data Convergence Protocol
  • a fifth layer may be a Radio Resource Control (RRC) layer.
  • a sixth layer may be a Non Access Stratum (NAS) layer or an Internet Protocol (IP) layer, and the seventh layer being the other layer.
  • NAS Non Access Stratum
  • IP Internet Protocol
  • the system bandwidth may be divided into multiple frequency domain parts, and each frequency domain part occupies a certain number of frequency domain resources.
  • the size of the frequency domain resource occupied by each frequency domain part may be configured by the network side or pre-defined by specification.
  • Each of the frequency domain parts is also called Listen Before Talk/Listen Before Send (LBT) bandwidth, also called RB set.
  • LBT Listen Before Talk/Listen Before Send
  • a guard interval may or may not exist between two consecutive LBT bandwidths.
  • the sender may perform a channel access procedure before sending a signal. If the UE detects that the energy (or power) of the received signal is less than a threshold within a time interval, it may determine that the current channel is considered to be idle and the sender can send a signal.
  • a channel access process is also called Clean Channel Access (CCA) . If the channel is sensed to be idle, CCA may be considered successful. If the channel is sensed to be busy, CCA may be considered failed.
  • a channel occupancy refers to transmission (s) on channel (s) by a sender after performing the corresponding channel access procedure.
  • a Channel Occupancy Time refers to the total time for which eNB/gNB/UE and any eNB/gNB/UE (s) sharing the channel occupancy perform transmission (s) on a channel after an eNB/gNB/UE performs the corresponding channel access procedures.
  • the signal can be sent.
  • the network side may also notify the UE of the 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 the time resource information and/or the end time of the preempted channel (e.g. channel occupancy) that the network side or the UE can use.
  • the network side schedules the UE for uplink transmission.
  • the network side use DCI to send all necessary parameters for uplink transmission for UE. That is, the uplink transmission is scheduled by DCI.
  • This scheduling method is also called dynamic grant (DG) .
  • the network uses RRC signaling to send all necessary parameters for uplink transmission for UE. That is, the uplink transmission is scheduled by RRC signaling.
  • the network uses RRC signaling to send part of the necessary parameters for uplink transmission, and then uses DCI to send the remaining necessary parameters for uplink transmission. That is, the uplink transmission is scheduled by RRC signaling and DCI.
  • Both of the scheduling methods are called configured grant (CG) .
  • the uplink transmission scheduled by the network side includes these mentioned scheduling modes.
  • the network side configures time-frequency domain resources of the PDCCH for UE. Further, the time-domain resources are periodic resources. The network side may send the PDCCH to the UE on the time-frequency domain resources of each PDCCH. The UE needs to monitor the PDCCH on the time-frequency resources of each PDCCH.
  • each time-domain resource that may send a PDCCH is also called a PDCCH scheduling occasion.
  • the network side uses DCI and/or RRC signaling to schedule a group of PUSCH, and DCI and/or RRC signaling indicates whether to repetitively transmit each of the PUSCH.
  • a first indication information in the DCI or RRC signaling indicates whether to repetitively transmit each of the PUSCH.
  • 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 can schedule a maximum of 8 PUSCHs using one DCI, so the first indication information length is 8.
  • whether the first indication information exists in the DCI is configured by network.
  • the configuration signaling may be MAC CE or RRC signaling.
  • the length of the first indication information is configured by network.
  • the configuration signaling may be MAC CE or RRC signaling.
  • each information bit corresponds to a scheduled PUSCH.
  • the least significant bit information bit may correspond to the first PUSCH that is scheduled
  • the next information bit may correspond to the second PUSCH that is scheduled, and so on until all scheduled PUSCHs are indicated.
  • the most significant bit information bit may correspond to the first scheduled PUSCH
  • the next information bit may correspond to the second PUSCH, and so on until all scheduled PUSCHs are indicated. If there are remaining information bits, these information bits are nothing (e.g., no instructions) . Thus, from the perspective of the UE, the UE may ignore these remaining information bits.
  • the information bit '1' may indicate that the corresponding PUSCH is not a repetitive transmission.
  • the corresponding PUSCH is initially transmitted.
  • the corresponding PUSCH is a first transmission during the PUSCHs indicated by the network.
  • the information bit '0' may indicate that the corresponding PUSCH is a repetitive transmission. That is, the corresponding PUSCH is not a first transmission during the PUSCHs indicated by the network. In other words, the corresponding PUSCH carries a same TB with the PUSCH before it.
  • the information bit '0' may indicate that the corresponding PUSCH is not a repetitive transmission.
  • the information bit '1' may indicate that the corresponding PUSCH is a repetitive transmission.
  • each repeatedly transmitted PUSCH may have the same HARQ process number as the first PUSCH that was not repeatedly transmitted (e.g. the first PUSCH that was initially transmitted) .
  • a repetitively transmitted PUSCH has the same HARQ process number as the PUSCH before it.
  • the HARQ process number of the first scheduled PUSCH may be indicated in the DCI, and the HARQ process number of each PUSCH that is not repetitive transmission may be the HARQ process number of the PUSCH that is not repetitive transmission plus one.
  • the UE or BS may perform a modulo operation on the calculated HARQ process number, and then use the number after the modulo operation as the HARQ process number for the PUSCH.
  • the modulo operation finds the remainder after division of one number by a second number.
  • the second number is the maximum number of the HARQ processes that UE may be used.
  • the maximum number of the HARQ process that UE may be used may be configured by the network via DCI, or MAC CE, or RRC signaling or defined by the protocol.
  • the HARQ process number for the PUSCH is 0.
  • FIG. 3 illustrates a block diagram of an example mapping 300 of a PUSCH configuration, in accordance with some embodiments of the present disclosure.
  • DCI schedules 8 PUSCHs (e.g., denoted as PUSCH 0 ⁇ 7 respectively) , and DCI indicates that the first HARQ process number is 14.
  • the maximum number of HARQ process that UE can be used configured by the network side is 16.
  • the length of the indication information in the DCI is 8.
  • the indication information bit is '11010011' .
  • the most significant bit of the indication field corresponds to the first PUSCH scheduled, and the information bit '1' indicates that the corresponding PUSCH is not a repetitive transmission, and the information bit '0' indicates that the corresponding PUSCH is a repetitive transmission, then the most significant bit '1' indicates PUSCH 0 is not repetitive transmission, and the HARQ process is 14.
  • the next information bit corresponds to the second PUSCH, i.e. PUSCH 1.
  • the information bit '1' indicates that PUSCH 1 is not repetitive transmission, and the HARQ process is 15.
  • the next information bit corresponds to the third PUSCH (e.g., PUSCH 2)
  • the information bit '0' indicates that the PUSCH 2 is a repetitive transmission, which is repeatedly transmitted the same transport block of the PUSCH 1
  • the HARQ process number of PUSCH 2 is also 15.
  • PUSCH 2 and PUSCH 1 carries the same transport block. The rest can be done in the same manner.
  • FIG. 4 illustrates a table 400 of example sending scheme and HARQ process numbers for the scheduled PUSCHs. If ‘send repeatedly’ is yes, the corresponding PUSCH is a repetitive transmission. For example, PUSCH 2 is a repetitive transmission. If ‘send repeatedly’ is no, the corresponding PUSCH is not a repetitive transmission. For example, the PUSCH 0 is not a repetitive transmission. ‘Repeated PUSCH’ represents 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.
  • 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 block.
  • PUSCH 3, PUSCH 4 and PUSCH 5 have the same HARQ process number.
  • the process number of PUSCH 3 is obtained by 16 modulo 16.
  • a group of PUSCHs is scheduled by using DCI and/or RRC signaling.
  • the PUSCHs in the group of PUSCHs that are sent before the first time interval before the next PDCCH scheduling occasion are sent in a repetitive transmission manner. That is, a same transport block is repetitively transmitted in different PUSCHs. In other words, a same transport block is transmitted more than once in different PUSCHs.
  • the PUSCH in the group of PUSCHs that are sent after the first time interval before the next PDCCH scheduling occasion are transmitted using a single transmission method. That is, a transport block is transmitted only once.
  • the PUSCHs in the group of PUSCHs that are sent before the second time interval before the COT boundary is transmitted using a single transmission method. In some embodiments, the PUSCHs in the group of the PUSCHs that are sent after the second time interval before the COT boundary are transmitted in a repetitive transmission manner. In some embodiments, the first time interval duration and the second time interval duration are configured by the network side or pre-defined by the protocol.
  • the PUSCH when a conflict occurs between the two methods (e.g., PUSCH is located after the first time interval before the next PDCCH scheduling occasion and after the second time interval before the COT boundary, or PUSCH is located before the first time interval before the next PDCCH scheduling occasion and before the second time interval before the COT boundary) , then the PUSCH is transmitted in a repetitive transmission manner.
  • the first number is the maximum number that a transport block can be transmitted repetitively (including the first transmission) .
  • the first number of repeated PUSCH transmissions or the first number of the repetitive transmission for a 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 a PUSCH configuration, in accordance with some embodiments of the present disclosure.
  • the network side schedules 8 PUSCHs (denoted as PUSCH 0 ⁇ 7 respectively) .
  • the first time interval is 3 slots.
  • the PUSCH 0 ⁇ 4 are located before 3 slots before the next PDCCH scheduling occasions, then PUSCH 0 ⁇ 4 is sent in a repetitive transmission manner.
  • the PUSCH 5 ⁇ 7 are located within 3 slots before the next PDCCH scheduling occasion, the PUSCH 5 ⁇ 7 are sent in a single transmission manner.
  • FIG. 6 illustrates a block diagram of an example mapping 600 of a PUSCH configuration, in accordance with some embodiments of the present disclosure.
  • the network side schedules 8 PUSCHs (denoted as PUSCH 0 ⁇ 7 respectively) .
  • the second time interval is 3 slots.
  • PUSCH 0 ⁇ 5 are located before 3 slots before the COT boundary, then PUSCH 0 ⁇ 5 is sent in a single transmission manner;
  • PUSCH 6 ⁇ 7 are located within 3 slots before the COT boundary, then PUSCH 6 ⁇ 7 are transmitted in a repetitive transmission manner.
  • FIG. 7 illustrates a block diagram of an example mapping 700 of a PUSCH configuration, in accordance with some embodiments of the present disclosure.
  • the network side schedules 8 PUSCHs (denoted as PUSCH 0 ⁇ 7, respectively) .
  • the first time interval configured is 4 slots, and the second time interval is 3 slots.
  • PUSCH 0 ⁇ 3 are located before 4 slots before the next PDCCH scheduling occasion and before 4 slots before the COT boundary.
  • PUSCH 0 ⁇ 3 are transmitted in a repetitive transmission manner.
  • the PUSCH 4 ⁇ 5 are located after 4 slots before the next PDCCH scheduling occasion and before the 3 slots before the COT boundary.
  • PUSCH 4 ⁇ 5 are transmitted in a single transmission manner.
  • the PUSCH 6 ⁇ 7 are located after 4 slots before the next PDCCH scheduling occasion and after 3 slots before the COT boundary.
  • PUSCH 6 ⁇ 7 are transmitted in a repetitively transmission manner.
  • a group of PUSCHs is scheduled by using DCI and/or RRC signaling.
  • the PUSCHs in the group of PUSCHs that are sent after the first time interval before the next PDCCH scheduling occasion are sent in a repetitive transmission manner. That is, a same transport block is repetitively transmitted in different PUSCHs. In other words, a same transport block is transmitted more than once in different PUSCHs.
  • the PUSCH in the group of PUSCHs that are sent before the first time interval before the next PDCCH scheduling occasion are transmitted using a single transmission method. That is, a transport block is transmitted only once.
  • the PUSCHs in the group of PUSCHs that are sent after the second time interval before the COT boundary is transmitted using a single transmission method. In some embodiments, the PUSCHs in the group of the PUSCHs that are sent before the second time interval before the COT boundary are transmitted in a repetitive transmission manner. In some embodiments, the first time interval duration and the second time interval duration are configured by the network side or pre-defined by the protocol.
  • the PUSCH when a conflict occurs between the two methods (e.g., PUSCH is located after the first time interval before the next PDCCH scheduling occasion and after the second time interval before the COT boundary, or PUSCH is located before the first time interval before the next PDCCH scheduling occasion and before the second time interval before the COT boundary) , then the PUSCH is transmitted in a single transmission manner.
  • the first number is the maximum number that a transport block can be transmitted repetitively (including the first transmission) .
  • the first number of repeated PUSCH transmissions or the first number of the repetitive transmission for a transport block is configured by the network side or specified by the protocol.
  • a transport block is repeatedly transmitted starting from the first PUSCH until the number of repetitive transmission is equal to the first number or there is no more PUSCH resource.
  • another transport block is repetitively transmitted starting from the next PUSCH resource.
  • the next PUSCH after a PUSCH transmitted in a repetitive transmission manner with the number of repetitive transmission less than the first number is transmitted in a single transmission manner, the next PUSCH is a first transmission for a transport block during the scheduled PUSCHs.
  • the next PUSCHs is an repetitive transmission to carry the transport block that is carried by the PUSCH before it until the number of repetitive number is equal to the first number or there is no more PUSCH resource.
  • the first number is the maximum number that a transport block can be transmitted repetitively (including the first transmission) .
  • PUSCH 0 ⁇ 3 are transmitted in a repetitive transmission manner.
  • PUSCH 4 ⁇ 5 are transmitted in a single transmission manner.
  • PUSCH 6 ⁇ 7 are transmitted in a repetitive transmission manner.
  • the first number of repetitive transmissions is two (including the first transmission)
  • PUSCH 0 and 1 transmit the same TB
  • PUSCH 2 and 3 transmit the same TB
  • PUSCH 4 transmits one TB
  • PUSCH 5 transmits one TB
  • PUSCH 6 and 7 transmit the same TB.
  • PUSCH 0 ⁇ 2 transmits the same TB.
  • PUSCH 3 transmits a TB.
  • PUSCH 4 and 5 are transmitted in a single transmission manner and TB carried in PUSCH 3 is transmitted only once, which is less than 3, PUSCH 4 and PUSCH 5 transmitted the same TB with PUSCH 3.
  • PUSCH 4 transmits a TB.
  • PUSCH 5 transmits a TB.
  • PUSCH 6 and PUSCH 7 transmit the same TB.
  • TB carried by PUSCH 6 and PUSCH 7 is transmitted only two times since there is no more PUSCH resource.
  • the PUSCHs transmitting the same TB has the same HARQ process number
  • the HARQ process number is the HARQ process number of the PUSCH transmitting the TB for the first time.
  • the service type e.g. service priority, data priority, etc
  • the relationship between the service type (e.g. service priority, data priority, etc) that uplink signal may carry and transmission approach or the relationship between priority for uplink transmission and transmission approach is configured by the network side or defined by protocol.
  • the configuration signaling may be DCI, or MAC CE, or RRC signaling.
  • UE transmits data (or service) using corresponding transmission approach according to the relationship between the priority for uplink transmission and transmission approach.
  • the network side configures a group of uplink transmissions for UE.
  • a first priority is configured for the group of uplink transmissions.
  • the group of uplink transmission carry the data (or service) with a first priority.
  • the UE transmits data (or service) with the second priority on the group of PUSCH using corresponding transmission approach according to the relationship between the priority for uplink transmission and transmission approach.
  • UE before transmitting the data (or service) with the second priority, UE transmits a first indication signaling to indicate that the UE has data (or, service) with the second priority to be transmitted, or indicate that the UE will transmit data (or service) with the second priority on the next PUSCH resource.
  • the first indication signaling may be a physical layer signaling, such as Uplink Control Information (UCI) , or a MAC layer signaling, such as MAC CE or a Buffer Status Report (BSR) .
  • UCI Uplink Control Information
  • BSR Buffer Status Report
  • the priority of data may be the priority of the logical channel. There is a relationship between the priority of the logical channel of the data and the transmission approach. In some embodiments, UE transmits data (or service) using corresponding transmission approach according to the relationship between the priority of the logical channel of data for uplink transmission and transmission approach.
  • the relationship may be to transmit data (or service) with the first priority in a single transmission manner and to transmit data (or service) with the second priority in a repetitive manner with second number of transmission times.
  • the second number may be configured by the network side via DCI, or MAC CE, or RRC signaling or pre-defined by protocol.
  • data (or service) with the first priority may be eMBB data (service) .
  • data (or service) with the second priority may be URLLC data (service) .
  • the network side configures a group of PUSCHs for UE.
  • the group of PUSCHs is configured for transmitting data (service) with the first priority.
  • one or more PUSCHs in the group of the PUSCHs transmit (e.g. carry) data (service) with the first priority in a single transmission manner.
  • one or more PUSCHs in the group the PUSCHs transmit (e.g. carry) data (service) with the second priority in a repetitive transmission manner.
  • FIG. 8 illustrates a block diagram of an example mapping 800 of a PUSCH configuration, in accordance with some embodiments of the present disclosure.
  • eMBB data is transmitted only once and URLLC data is repetitively transmitted two times.
  • the network side schedules a group of PUSCH transmissions (denoted as PUSCH 0 ⁇ 7 respectively) for UE.
  • the group of PUSCH is configured for transmitting eMBB data.
  • eMBB data is transmitted on PUSCH 0 ⁇ 2 in a single transmission manner.
  • UE has URLLC data for transmission during PUSCH 2.
  • an UCI may be multiplexing to PUSCH 3 or a BSR may be transmitted in PUSCH 3 to indicate that UE has URLLC data for transmission or URLLC data is transmitted on the next PUSCH resource.
  • URLLC data is transmitted starting from PUSCH 4 (including PUSCH 4) in a repetitive transmission manner.
  • PUSCH 4 and PUSCH 5 carry the same TB for URLLC data.
  • PUSCH 6 and PUSCH 7 carry the same TB for URLLC data.
  • URLLC data is transmitted starting from PUSCH 3 (including PUSCH 3) in a repetitive transmission manner.
  • PUSCH 3 and PUSCH 4 carry the same TB for URLLC data.
  • PUSCH 5 and PUSCH 6 carry the same TB for URLLC data.
  • PUSCH 7 carries a TB for URLLC data.
  • URLLC data is transmitted starting from PUSCH 0 (including PUSCH 0) in a repetitive transmission manner.
  • 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 TB for URLLC data.
  • PUSCH 6 and PUSCH 7 carry the same TB for URLLC data.
  • the relationship may be to transmit data (or service) with the first priority using a first MCS, to transmit data (or service) with the second priority using a second MCS, and so on.
  • the first MCS, the second MCS (and other MCS) are configured by the network side via DCI, or MAC CE, or RRC signaling.
  • the network side configures a group of PUSCHs for UE.
  • the group of PUSCHs is configured for transmitting data (service) with the first priority.
  • one or more PUSCHs in the group of the PUSCHs transmit data (service) with the first priority using the first MCS.
  • when UE has data (service) with the second priority for transmission one or more PUSCHs in the group the PUSCHs transmit data (service) with the second priority using the second MCS.
  • the network side schedules a group of PUSCH transmissions (denoted as PUSCH 0 ⁇ 7 respectively) for UE.
  • the group of PUSCH is configured for transmitting eMBB data.
  • eMBB data are transmitted on PUSCH 0 ⁇ 2 by using MCS 1.
  • UE has URLLC data for transmission during PUSCH 2.
  • an UCI may be multiplexing to PUSCH 3 or a BSR may be transmitted in PUSCH 3 to indicate that UE has URLLC data for transmission or URLLC data are transmitted on the next PUSCH resource.
  • URLLC data are transmitted starting from PUSCH 4 (including PUSCH 4) by using MCS 2. In other words, URLLC data are transmitted on PUSCH 4 ⁇ 7 by using MCS2, respectively.
  • URLLC data are transmitted starting from PUSCH 3 (including PUSCH 3) by using MCS 2. In other words, URLLC data are transmitted on PUSCH 3 ⁇ 7 by using MCS2, respectively.
  • URLLC data are transmitted starting from PUSCH 0 (including PUSCH 0) by using MCS 2. In other words, URLLC data are transmitted on PUSCH 0 ⁇ 7 by using MCS 2, respectively.
  • the relationship may be to transmit data (or service) with the first priority in a single transmission manner and by using a first MCS, to transmit data (or service) with the second priority in a repetitive transmission manner with a second transmission times and by using the a second MCS, and so on.
  • the first MCS, the second MCS (and other MCS) are configured by the network side via DCI, or MAC CE, or RRC signaling.
  • the second number may be configured by the network side via DCI, or MAC CE, or RRC signaling or pre-defined by protocol.
  • the network side configures a group of PUSCHs for UE.
  • the group of PUSCHs is configured for transmitting data (service) with the first priority.
  • one or more PUSCHs in the group of the PUSCHs transmit data (service) with the first priority by using the first MCS only once.
  • one or more PUSCHs in the group the PUSCHs transmit data (service) with the second priority in a repetitive transmission manner and by using the second MCS.
  • the network side schedules a group of PUSCH transmissions (denoted as PUSCH 0 ⁇ 7 respectively) for UE.
  • the group of PUSCH is configured for transmitting eMBB data.
  • eMBB data are transmitted on PUSCH 0 ⁇ 2 by using MCS 1 only one times.
  • PUSCH 0, PUSCH 1, PUSCH 2 carries one TB for eMBB data, respectively.
  • UE has URLLC data for transmission during PUSCH 2.
  • an UCI may be multiplexing to PUSCH 3 or a BSR may be transmitted in PUSCH 3 to indicate that UE has URLLC data for transmission or URLLC data are transmitted on the next PUSCH resource.
  • URLLC data are transmitted starting from PUSCH 4 (including PUSCH 4) repetitively 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.
  • URLLC data are transmitted starting from PUSCH 3 (including PUSCH 3) repetitively by using MCS 2.
  • PUSCH 3 and PUSCH 4 carrying the same TB for URLLC data are transmitted by using MCS 2.
  • PUSCH 5 and PUSCH 6 carrying the same TB for URLLC data are transmitted by using MCS 2.
  • PUSCH 7 carrying the one TB for URLLC data is transmitted by using MCS 2 and this TB is transmitted only once.
  • URLLC data are transmitted starting from PUSCH 0 (including PUSCH 0) repetitively by using MCS 2.
  • 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.
  • network may configure one or more configurations for uplink signals transmission for UE. UE may use one of the configurations to transmit uplink signals. In some embodiments, network may configure one or more configurations for PUSCH transmission for UE. UE may use one of the configurations to transmit the PUSCH. In some embodiments, network may configure a Time Domain Resource Allocation (TDRA) configuration for PUSCH for UE.
  • the TDRA configuration may include one or more time resource configuration for uplink signal transmission.
  • a time resource configuration may include at least a start and a length of the resource in the time domain. In some embodiments, a time resource configuration may be indicated by Start and length indicator value (SLIV) .
  • UE may use one of the time resource configuration for PUSCH transmission.
  • the configuration for uplink signals for UE may be configured by DCI, or MAC CE, or RRC signaling.
  • the time domain resource for PUSCH across the slot boundary according the start and the length of the time domain resource should start from the indicated starting symbol and end to the slot boundary.
  • the nominal repetition for the PUSCH may be divided into two actual repetition.
  • the PUSCH may be divided into two PUSCHs.
  • FIG. 9 illustrates a table of an example mapping 900 of a PUSCH configuration, in accordance with some embodiments of the present disclosure.
  • a TDRA index indicates a TDRA configuration.
  • TDRA configuration 0 includes 5 configurations of the time domain resource for PUSCH. For the 5 configuration of the time domain resource, the start symbols are symbol 0, 1, 2, 3, 5, respectively. The length of 5 configurations of the time domain resource are all 14 OFDM symbols.
  • TDRA configuration 0 is configured for transmitting PUSCH.
  • UE can use each of the 5 configuration of the time domain for transmitting PUSCH. In other words, UE can transmit PUSCH starting from any symbol of symbol 0 ⁇ 4. In some embodiments, UE detect that channel is idle before symbol 0.
  • UE can transmit PUSCH on the time domain resource that the length is 14 OFDM symbols and starts from symbol 0. In some embodiments, UE detect that channel is idle before symbol 2. UE can transmit PUSCH on the time domain resource that the length is 14 OFDM symbols and starts from symbol 2.
  • network may configure more than one configured grant resource for UE.
  • multiple dynamic grant resource for PUSCH is configured by the same method for configuring multiple configured grant resource.
  • a dynamic resource configuration may include more than one frequency domain resource configurations.
  • multiple dynamic resource may have the same time domain resource while have the different frequency time resource.
  • UE may choose any one of the multiple dynamic resource to transmit uplink signals if the time domain resource of the multiple dynamic resource are the same as the time domain resource scheduled by network.
  • multiple dynamic resource may have the same the frequency domain resource.
  • the offset of the time domain resource for two adjacent dynamic resource is D.
  • the value of D is configured by the network via DCI, or MAC CE, or RRC signaling.
  • network configures more than PUSCHs (e.g. K PUSCHs) for UE. If UE detects that the channel is idle, it may transmit only one PUSCH or transmit K1 PUSCH repetitively and release the remaining channel. In other words, after transmitting only one PUSCH or transmitting K1 PUSCH repetitively, UE may not transmit anything no longer (K-1 PUSCHs or K-K1 PUSCHs may be not transmitted) .
  • network configures more than PUSCHs for UE. If UE detects that the channel is idle, UE may transmit uplink signal on the configured resource.
  • UE transmit uplink signals by using method 1.
  • UE only transmits one PUSCH or transmits K1 PUSCH and release the remaining channel.
  • network may indicates which method UE uses for transmitting uplink signals via DCI, or MAC CE, or RRC signaling.
  • transmission occasion can be increased for dynamic PUSCH.
  • the probability and the reliability of the dynamic PUSCH can be increased.
  • the flexibility of scheduling can be increased.
  • an uplink signal (e.g. PUCCH, PUSCH, SRS, PRACH, etc. ) of a first cell is overlapped with a PRACH of a second cell at least in time domain or in frequency domain, only the PRACH of the second cell is transmitted. In other words, the uplink signal is not transmitted (e.g., dropped) .
  • a uplink signal e.g. PUCCH, PUSCH, SRS, PRACH, etc.
  • a uplink signal of a first cell or part of a uplink signal of a first cell locates within a slot of a second cell in which a PRACH of the second cell may be transmit, only the PRACH of the second cell is transmitted.
  • the uplink signal is not transmitted (e.g. dropped) .
  • a PRACH of a second cell or part of a PRACH of a second cell locates within a slot of a first cell in which a uplink signal (e.g. PUCCH, PUSCH, SRS, PRACH, etc. ) of first cell is transmitted, only the PRACH of the second cell is transmitted.
  • the uplink signal is not transmitted (e.g. dropped) .
  • a gap between the first or last symbol of an uplink signal e.g., PUCCH, PUSCH, SRS, PRACH, etc.
  • the uplink signal is not transmitted (e.g. dropped) .
  • the first cell may be the source cell or source Master Cell Group (MCG) during handover.
  • the second cell may be the target cell or target MCG.
  • the value of Z is pre-defined by protocol or configured by network via DCI, or MAC CE, or RRC signaling.
  • the value of Z may be determined according to the uplink subcarrier space.
  • the value of Z may be determined according to the largest or largest subcarrier space for the uplink bandwidth part of source cell (source MCG) and target cell (target MCG) .
  • FIG. 10 is a flow diagram depicting a method for meeting the delay and reliability requirements for signal transmission for Ultra-Reliable Low Latency Communication (URLLC) from the perspective of a UE, in accordance with 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 operations of method 1000 may be performed by a wireless communication node, such as BS 102 in FIG. 1. In some operations, some or all operations of method 1000 may be performed by a wireless communication device, such as UE 104 in FIG. 1. Each operation may be re-ordered, added, removed, or repeated.
  • URLLC Ultra-Reliable Low Latency Communication
  • the method 1000 includes, in some embodiments, the operation 1002 of receiving, by a wireless communication device from a wireless communication node, a control signal indicating whether to repetitively transmit each of a plurality of uplink channels on an unlicensed band.
  • the method includes, in some embodiments, the operation 1004 of respectively transmitting, by the wireless communication device to the wireless communication node, the plurality of uplink channels based on the control signal.
  • FIG. 11 is a flow diagram depicting a method for meeting the delay and reliability requirements for signal transmission for Ultra-Reliable Low Latency Communication (URLLC) from the perspective of a UE, in accordance with 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 operations of method 1100 may be performed by a wireless communication node, such as BS 102 in FIG. 1. In some operations, some or all operations of method 1100 may be performed by a wireless communication device, such as UE 104 in FIG. 1. Each operation may be re-ordered, added, removed, or repeated.
  • URLLC Ultra-Reliable Low Latency Communication
  • the method 1100 includes, in some embodiments, the 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 approaches.
  • the method includes, in some embodiments, the operation 1104 of determining, by the wireless communication device according to the control signal, one of the plurality of approaches corresponding to one of the plurality of service types.
  • the method includes, in some embodiments, the operation 1106 of transmitting, by the wireless communication device to the wireless communication node, each of the plurality of uplink channels using a respective one of the approaches.
  • FIG. 12 is a flow diagram depicting a method for meeting the delay and reliability requirements for signal transmission for Ultra-Reliable Low Latency Communication (URLLC) from the perspective of a BS, in accordance with 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 operations of method 1200 may be performed by a wireless communication node, such as BS 102 in FIG. 1. In some operations, some or all operations of method 1200 may be performed by a wireless communication device, such as UE 104 in FIG. 1. Each operation may be re-ordered, added, removed, or repeated.
  • URLLC Ultra-Reliable Low Latency Communication
  • the method 1200 includes, in some embodiments, the operation 1202 of transmitting, by a wireless communication node to a wireless communication device, a control signal indicating whether to repetitively transmit each of a plurality of uplink channels on an unlicensed band.
  • the method includes, in some embodiments, the operation 1204 of receiving, by the wireless communication node from the wireless communication device and responsive to transmitting the control signal, the plurality of uplink channels.
  • FIG. 13 is a flow diagram depicting a method for meeting the delay and reliability requirements for signal transmission for Ultra-Reliable Low Latency Communication (URLLC) from the perspective of a BS, in accordance with 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 operations of method 1300 may be performed by a wireless communication node, such as BS 102 in FIG. 1. In some operations, some or all operations of method 1300 may be performed by a wireless communication device, such as UE 104 in FIG. 1. Each operation may be re-ordered, added, removed, or repeated.
  • URLLC Ultra-Reliable Low Latency Communication
  • the method 1300 includes, in some embodiments, the 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 approaches, wherein the control signal causes the wireless communication device to: determine, according to the control signal, one of the plurality of approaches corresponding to one of the plurality of service types, and transmit each of the plurality of uplink channels to the wireless communication node using a respective one of the approaches.
  • the method includes, in some embodiments, the operation 1304 of receiving, by the wireless communication node from the wireless communication device, the plurality of uplink channels.
  • any reference to an element herein using a designation such as “first, “ “second, “ and so forth does not generally limit the quantity or order of those elements. Rather, these designations can be used herein as a convenient means of distinguishing between two or more elements or instances of an element. Thus, a reference to first and second elements does not mean that only two elements can be employed, or that the first element must precede the second element in some manner.
  • any of the various illustrative logical blocks, modules, processors, means, circuits, methods and functions described in connection with the aspects disclosed herein can be implemented by electronic hardware (e.g., a digital implementation, an analog implementation, or a combination of the two) , firmware, various forms of program (e.g., a computer program product) or design code incorporating instructions (which can be referred to herein, for convenience, as "software” or a "software module) , or any combination of these techniques.
  • firmware e.g., a digital implementation, an analog implementation, or a combination of the two
  • firmware various forms of program
  • design code incorporating instructions which can be referred to herein, for convenience, as "software” or a "software module”
  • IC integrated circuit
  • DSP digital signal processor
  • ASIC application specific integrated circuit
  • FPGA field programmable gate array
  • the logical blocks, modules, and circuits can further include antennas and/or transceivers to communicate with various components within the network or within the device.
  • a general purpose processor can be a microprocessor, but in the alternative, the processor can be any conventional processor, controller, or state machine.
  • a processor can 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.
  • Computer-readable media includes both computer storage media and communication media including any medium that can be enabled to transfer a computer program or code from one place to another.
  • a storage media can be any available media that can be accessed by a computer.
  • such computer-readable media can include 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.
  • module refers to software, firmware, hardware, and any combination of these elements for performing the associated functions described herein. Additionally, for purpose of discussion, the various modules are described as discrete modules; however, as would be apparent to one of ordinary skill in the art, two or more modules may be combined to form a single module that performs the associated functions according embodiments of the present solution.
  • memory or other storage may be employed in embodiments of the present solution.
  • memory or other storage may be employed in embodiments of the present solution.
  • any suitable distribution of functionality between different functional units, processing logic elements or domains may be used without detracting from the present solution.
  • functionality illustrated to be performed by separate processing logic elements, or controllers may be performed by the same processing logic element, or controller.
  • references to specific functional units are only references to a suitable means for providing the described functionality, rather than indicative of a strict logical or physical structure or organization.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

Système et procédé permettant de satisfaire aux exigences de délai et de fiabilité relatives à la transmission de signal pour URLLC. Le système et le procédé consistent à recevoir, par un dispositif de communication sans fil depuis un nœud de communication sans fil, un signal de commande indiquant si chacun d'une pluralité de canaux de liaison montante sur une bande sans licence doit être transmis de manière répétée ; et à transmettre respectivement, par le dispositif de communication sans fil au nœud de communication sans fil, la pluralité de canaux de liaison montante sur la base du signal de commande.
PCT/CN2020/075360 2020-02-14 2020-02-14 Système et procédé de transmission de signal Ceased WO2021098055A1 (fr)

Priority Applications (2)

Application Number Priority Date Filing Date Title
CN202080092797.6A CN114930951B (zh) 2020-02-14 2020-02-14 信号取消的方法
PCT/CN2020/075360 WO2021098055A1 (fr) 2020-02-14 2020-02-14 Système et procédé de transmission de signal

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2020/075360 WO2021098055A1 (fr) 2020-02-14 2020-02-14 Système et procédé de transmission de signal

Publications (1)

Publication Number Publication Date
WO2021098055A1 true WO2021098055A1 (fr) 2021-05-27

Family

ID=75980337

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2020/075360 Ceased WO2021098055A1 (fr) 2020-02-14 2020-02-14 Système et procédé de transmission de signal

Country Status (2)

Country Link
CN (1) CN114930951B (fr)
WO (1) WO2021098055A1 (fr)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2024021115A1 (fr) * 2022-07-29 2024-02-01 Zte Corporation Procédé, dispositif et produit-programme d'ordinateur destinés à la communication sans fil

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20180368117A1 (en) * 2017-06-15 2018-12-20 Sharp Laboratories Of America, Inc. Procedure, base station and user equipment for uplink transmission without grant
WO2019032748A1 (fr) * 2017-08-10 2019-02-14 Sharp Laboratories Of America, Inc. Procédures, station de base et équipements utilisateurs pour une transmission en liaison montante sans autorisation

Family Cites Families (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP3627954B1 (fr) * 2013-11-19 2022-08-31 LG Electronics Inc. Procédé pour effectuer une procédure d'accès aléatoire
JP2019054314A (ja) * 2016-02-02 2019-04-04 シャープ株式会社 端末装置および方法
US11490434B2 (en) * 2018-06-25 2022-11-01 Qualcomm Incorporated Dual connectivity transmission techniques

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20180368117A1 (en) * 2017-06-15 2018-12-20 Sharp Laboratories Of America, Inc. Procedure, base station and user equipment for uplink transmission without grant
WO2019032748A1 (fr) * 2017-08-10 2019-02-14 Sharp Laboratories Of America, Inc. Procédures, station de base et équipements utilisateurs pour une transmission en liaison montante sans autorisation

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
ERICSSON: ""PUSCH Enhancement for NR URLLC"", 3GPP TSG RAN WG1 MEETING #98BIS， R1-1910547， CHONGQING， CHINA， OCT 14TH-20TH， 2019, 7 October 2019 (2019-10-07), XP051789348 *
ERICSSON: ""PUSCH Enhancement for NR URLLC"", 3GPP TSG RAN WG1 MEETING #99， R1-1911947， RENO， USA， NOVEMBER 18TH-22ND， 2019, 9 November 2019 (2019-11-09), XP051823128 *

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2024021115A1 (fr) * 2022-07-29 2024-02-01 Zte Corporation Procédé, dispositif et produit-programme d'ordinateur destinés à la communication sans fil

Also Published As

Publication number Publication date
CN114930951B (zh) 2024-08-23
CN114930951A (zh) 2022-08-19

Similar Documents

Publication Publication Date Title
US20220272557A1 (en) Systems and methods for determining information indicative of cancelation
US12389377B2 (en) Partial sensing method and device for device-to-device communication in wireless communication system
US20220369307A1 (en) System and method for resource allocation
US12395967B2 (en) System and method for sidelink configuration
CN115004602A (zh) 用于确定下行链路控制信息的系统和方法
US12185378B2 (en) Systems and methods of enhanced random access procedure using information element containing configured parameters
CN115039359A (zh) 用于资源分配的系统和方法
US12336001B2 (en) Method of data transmission in unlicensed band
US12328739B2 (en) Signaling solution for fast beam diversity
US20230180244A1 (en) System and method for signal transmission
US12369182B2 (en) System and method for reference signaling design and configuration
US20220360409A1 (en) System and method for sidelink configuration
US11432282B2 (en) System and method for scheduling communication resources
WO2021098055A1 (fr) Système et procédé de transmission de signal
CN115136714B (zh) 一种用于信号传输的系统和方法
KR102899488B1 (ko) 고속 빔 다이버시티를 위한 시그널링 해결책
CN115211191B (zh) 用于侧行链路配置的系统和方法
WO2024156145A1 (fr) Systèmes et procédés pour effectuer un partage de temps d'occupation de canal (cot) de liaison latérale sur une porteuse sans licence
KR102902232B1 (ko) 사이드링크 구성을 위한 시스템 및 방법
JP2025023181A (ja) Ｐｕｓｃｈのサブキャリア間隔とｐｒａｃｈのサブキャリア間隔との組み合わせのためのシステムおよび方法

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 20890434

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 20890434

Country of ref document: EP

Kind code of ref document: A1

32PN Ep: public notification in the ep bulletin as address of the adressee cannot be established

Free format text: NOTING OF LOSS OF RIGHTS PURSUANT TO RULE 112(1) EPC (EPO FORM 1205A DATED 21/02/2023)

122 Ep: pct application non-entry in european phase

Ref document number: 20890434

Country of ref document: EP

Kind code of ref document: A1