WO2021098054A1 - 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
WO2021098054A1
WO2021098054A1 PCT/CN2020/075358 CN2020075358W WO2021098054A1 WO 2021098054 A1 WO2021098054 A1 WO 2021098054A1 CN 2020075358 W CN2020075358 W CN 2020075358W WO 2021098054 A1 WO2021098054 A1 WO 2021098054A1
Authority
WO
WIPO (PCT)
Prior art keywords
wireless communication
sets
signal
communication device
uplink
Prior art date
Application number
PCT/CN2020/075358
Other languages
English (en)
Inventor
Shuaihua KOU
Peng Hao
Jing Shi
Wei Gou
Xianghui HAN
Junfeng Zhang
Original Assignee
Zte Corporation
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 Corporation filed Critical Zte Corporation
Priority to PCT/CN2020/075358 priority Critical patent/WO2021098054A1/fr
Priority to CN202080096479.7A priority patent/CN115136714A/zh
Publication of WO2021098054A1 publication Critical patent/WO2021098054A1/fr

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W74/00—Wireless channel access
    • H04W74/08—Non-scheduled access, e.g. ALOHA
    • H04W74/0808—Non-scheduled access, e.g. ALOHA using carrier sensing, e.g. carrier sense multiple access [CSMA]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L27/00—Modulated-carrier systems
    • H04L27/0006—Assessment of spectral gaps suitable for allocating digitally modulated signals, e.g. for carrier allocation in cognitive radio
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/003—Arrangements for allocating sub-channels of the transmission path
    • H04L5/0044—Arrangements for allocating sub-channels of the transmission path allocation of payload
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/0091—Signaling for the administration of the divided path
    • H04L5/0094—Indication of how sub-channels of the path are allocated
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/0001—Arrangements for dividing the transmission path
    • H04L5/0003—Two-dimensional division
    • H04L5/0005—Time-frequency
    • H04L5/0007—Time-frequency the frequencies being orthogonal, e.g. OFDM(A), DMT
    • 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 signal indicating a plurality of resource block (RB) sets (e.g., LBTs assigned by BS 102 to UE 104) for transmitting a plurality of uplink channels (e.g., one or more PUSCHs) on an unlicensed band.
  • the method includes determining, by the wireless communication device, that one or more of the plurality of RB sets pass a channel access procedure (e.g., including CCA) .
  • the method includes transmitting, by the wireless communication device to the wireless communication node, a first uplink channel (e.g., PUSCH 0) of the plurality of uplink channels.
  • a method in another embodiment, includes transmitting, by a wireless communication node to a wireless communication device, a signal indicating a plurality of resource block (RB) sets for transmitting a plurality of uplink channels on an unlicensed band.
  • the signal causes the wireless communication device to: determine that one or more of the plurality of RB sets pass a channel access procedure, and transmit a first uplink channel of the plurality of uplink channels to the wireless communication node.
  • the method includes receiving, by the wireless communication node from the wireless communication device, the first uplink channel of 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 block diagram of an example mapping of PUSCH configuration, in accordance with some embodiments 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 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. 9 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 may send (e.g., transmit, deliver, etc. ) one or more PUSCHs.
  • the UE may send the PUSCHs in a CBG-based manner, where each CBG may be encoded/coded (e.g., arranged, classified, collected, etc. ) independently.
  • the UE may send one or more PUSCHs, and the UE may determine the size of the transport block according to the available resources in an LBT band.
  • the transport block may be mapped (e.g., linked, arranged, organized, etc. ) to one or more LBT bandwidths after being encoded and modulated, respectively, where the Redundancy Versions (RVs) for the transport block mapped to different LBT bandwidths may be the same or different.
  • RVs Redundancy Versions
  • the UE does not send the PUSCH on the first N symbols of the configured resources, or instead, may send a channel preemption signal on the first N symbols of the configured resources.
  • the UE may send a PUSCH after N symbols.
  • the UE may send a PUCCH after N symbols, and/or the PUCCH may carry (e.g., include, etc. ) the LBT bandwidth information on which UE transmits uplink signals and/or PUCCH is repeatedly sent on multiple LBT bandwidths.
  • the PUSCH transmission method used by the UE is configured by the network side. In some embodiments, there may be a coupling relationship between the service priority and the PUSCH transmission method. In some embodiments, when the first priority service is instructed to be sent, the UE may use “Method One” (as discussed herein) ; when the second priority service is instructed to be sent, the UE may use “Method Two” (as discussed herein) ; when the third priority service is instructed to be sent, the UE may use “Method Three” (as discussed herein) .
  • 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 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 may use DCI and /or RRC signaling to configure (e.g., arrange, schedule, adjust, initialize, etc. ) the UE to send (e.g., transmit, deliver, etc. ) uplink signal on multiple LBT bandwidths.
  • its uplink frequency domain resources may include multiple LBT bandwidths.
  • the UE may use a CBG-based transmission mode.
  • a transport block size may be determined according to the available resources configured by network side. In other words, a transport block size may be determined according to the availabe resources of the multiple LBT bandwidths.
  • the UE may independently encode and modulate each CBG.
  • the mapping rule when modulation symbols are mapped onto an uplink transmission resource, the mapping rule may be mapped in the order of frequency domain first, time domain later, and then LBT bandwidth. In some embodiments, the modulation symbols are only mapped onto the LBT bandwidth where CCA is successful. In some embodiments, the modulation symbols can be mapped to a LBT bandwidth only if the previous LBT bandwidth is fully mapped with modulation symbols. In some embodiments, the UE only transmits signals on the LBT bandwidth where CCA is successful. That is, the UE cancels (e.g. drops, punctures, etc) the modulation symbols or signals mapped onto the LBT bandwidth where CCA is failed. In other words, the modulation symbols or signals mapped onto the LBT bandwidth where CCA is failed are not transmitted. That is, only part of the CBGs of the transport block are transmitted.
  • FIG. 3 illustrates a block diagram of an example mapping 300 of a PUSCH configuration, in accordance with some embodiments of the present disclosure.
  • the PUSCH configured by the network side occupies 4 LBT bandwidths in the frequency domain (respectively, denoted as LBT bandwidths 1, 2, 3, and 4) , and the configuration signaling is RRC signaling and /or DCI.
  • the UE uses a CBG-based method for transmission.
  • the transport block for PUSCH transmission are determined according to the available resources configured by network side. In other words, the transport block for PUSCH transmission are determined according to the available resources of LBT bandwidth 1, 2, 3 and 4.
  • the PUSCH (or transport block) includes 8 CBGs (denoted as CBG 0 ⁇ 7; respectively) , and the UE independently encodes and modulates each CBG.
  • Eight CBGs are mapped to PUSCH resources in the order of first frequency domain, then time domain, and then LBT bandwidth. Among them, CBG 0 ⁇ 1 is mapped to LBT bandwidth 1, CBG 2 ⁇ 3 is mapped to LBT bandwidth 2 and CBG 4 ⁇ 5 is mapped to LBT bandwidth 3, and CBG 6 ⁇ 7 is mapped to LBT bandwidth 4.
  • CCA is successful on LBT bandwidths 2, 3, then the UE only sends signals within LBT bandwidths 2, 3. In other words, the UE only sends CBG 2 ⁇ 5.
  • CBG 0, 1, 6 and 7 are dropped.
  • FIG. 3 only shows the mapping of a select number of LBT bandwidths and a select number CBGs, the mapping may include any number of LBT bandwidths and CBGs.
  • the network side may use DCI and /or RRC signaling to configure (e.g., arrange, schedule, adjust, initialize, etc. ) the UE to send (e.g., transmit, deliver, etc. ) uplink signal on multiple LBT bandwidths.
  • UE may use the above method to transmit a PUSCH on the first PUSCH resource after CCA is successful.
  • the UE may transmit PUSCH on the next PUSCH resource.
  • transport block size are determined according to the available resources of LBT bandwidths on which UE may transmit PUSCH. That is the available resources of LBT bandwidths on which UE may transmit PUSCH are used to calculate transport block size.
  • UE may transmit one or more CBGs which constitute a complete transport block for PUSCH transmission.
  • FIG. 4 illustrates a block diagram of an example mapping 400 of PUSCH configuration, in accordance with some embodiments of the present disclosure.
  • the PUSCH configured by the network side occupies 4 LBT bandwidths in the frequency domain (respectively, denoted as LBT bandwidths 1, 2, 3, and 4) , and the configuration signaling is RRC signaling and /or DCI.
  • CCA is successful on LBT bandwidth 2 and 3 before transmitting PUSCH 0. That is, PUSCH 0 is the first PUSCH after CCA is successful.
  • UE may transmit PUSCH on LBT bandwidth 2 and 3.
  • the transport block are determined according to the available resources of LBT bandwidth 1 ⁇ 4.
  • UE only transmits sends CBG 2 ⁇ 5 for PUSCH 0.
  • CBG 0, 1, 6 and 7 are dropped for PUSCH 0.
  • the transport block are determined according to the available resources of LBT bandwidth that UE transmits PUSCH (i.e., LBT bandwidth 2 and 3) . That is, for PUSCH 1, 2 and the next PUSCH (not shown in the FIG 4) , UE transmits multiple CBGs which constitute a complete transport block. There is no CBG which is dropped. If CCA is successful on LBT bandwidth 1, 3 and 4 before transmitting PUSCH 0. UE transmits PUSCH on LBT bandwidth 3 and 4 since LBT bandwidth 3 and 4 are contiguous in frequency domain.
  • the transport block are determined according to the available resources of LBT bandwidth 1 ⁇ 4.
  • UE only transmits CBG 4 ⁇ 7 for PUSCH 0.
  • CBG 0 ⁇ 3 are dropped for PUSCH 0.
  • the transport block are determined according to the available resources of LBT bandwidth that UE transmits PUSCH (i.e., LBT bandwidth 3 and 4) .
  • FIG. 4 only shows the mapping of a select number of LBT bandwidths and a select number CBGs, the mapping may include any number of LBT bandwidths and CBGs.
  • the number of CBGs configured by the network side may be equal to the number of LBT bandwidths occupied by the PUSCH resources configured by the network side. As shown in FIG. 4, the PUSCH configured by the network side occupies 4 LBT bandwidths in the frequency domain, so the number of CBGs of a transport block is 4. CBG 0 ⁇ 3 are mapped to 4 LBT bandwidth resources, respectively. In some embodiments, the maximum number of CBGs configured by the network side may be equal to the number of LBT bandwidths occupied by the PUSCH resources configured by the network side. As shown in FIG. 4, the PUSCH configured by the network side occupies 4 LBT bandwidths in the frequency domain, so the maximum number of CBGs of a transport block is 4. CBG 0 ⁇ 3 are mapped to 4 LBT bandwidth resources, respectively.
  • the network side may use DCI and/or RRC signaling to configure the UE to transmit PUSCH, where the frequency domain resources of the PUSCH may occupy multiple LBT bandwidths.
  • the UE may determine the transport block size according to one of the resources of the LBT bandwidth. That is, the UE may calculate the transport block size of the PUSCH using the available resource size on one of the LBT bandwidths of the PUSCH.
  • the available resources refer to the resources that can be used for PUSCH transmission, such as resource elements (REs) that can be used for PUSCH transmission.
  • the UE may use the available resources of the LBT bandwidth with the smallest or largest LBT bandwidth index to calculate the PUSCH transport block size.
  • LBT bandwidth used for UE to calculate the PUSCH transport block size may be indicated by network side. The may use the available resource of the indicated bandwidth to calculate the PUSCH transport block size. In some embodiments, when the sizes of the available resources in the multiple LBT bandwidths occupied by the PUSCH are different, the UE may use the available resources of the LBT bandwidth with the smallest or largest number of available resources to calculate the PUSCH transport block size. In some embodiments, the UE may encode and/or modulate a transport block, and map the transport block to resources of one or more LBT bandwidths that CCA is successful for transmission, respectively.
  • the UE may encode and/or modulate a transport, and map the transport block to resources of one or more LBT bandwidths on which UE may transmit uplink signals, respectively.
  • the transport block when a transport block is mapped to multiple LBT bandwidth resource, the transport block is encoding and/or modulating separately for different LBT bandwidth.
  • all modulation symbols of the transport block when a transport block is mapped to multiple LBT bandwidth resources, all modulation symbols of the transport block may be mapped to each LBT bandwidth resource.
  • transport block mapped to different LBT bandwidth may use the same or different redundancy versions (RVs) .
  • the RVs may be configured by DCI or RRC signaling scheduling PUSCH transmission.
  • DCI or RRC signaling may configure the RVs used for the transport block mapped to one of the LBT bandwidths, and the RVs used for the transport block mapped to the other LBT bandwidths may be obtained from the configured RVs used for the transport block mapped to one of the LBT bandwidths.
  • the transport block may be only mapped to the LBT bandwidth that CCA is successful.
  • the UE only transmits signals on the LBT bandwidth that the CCA is successful. In other words, the UE cancels (e.g. drops, punctures, etc. ) the modulation symbols or signals on the LBT bandwidth that CCA is failed. The modulation symbols or signals mapped to the LBT bandwidths that CCA is failed are not transmitted.
  • 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 PUSCH configured by the network side occupies 4 LBT bandwidths in the frequency domain (respectively, denoted as LBT bandwidths 1, 2, 3, and 4) , and the configuration signaling may be RRC signaling and /or DCI.
  • CCA is successful only on LBT bandwidths 1, 2, and 3, and then the UE sends one or more PUSCH on LBT bandwidth 1, 2, and 3.
  • the UE may use available resources within LBT bandwidth 1 or LBT bandwidth 2 or LBT bandwidth 3 or LBT bandwidth 4 to determine the transport block size.
  • FIG. 5 only shows the mapping of a select number of LBT bandwidths and a select number of Transport Blocks (TBs) , the mapping may include any number of LBT bandwidths and TBs.
  • the network side may indicate which LBT bandwidth to be used to calculate transport block size for PUSCH.
  • the network side uses RRC signaling, or MAC CE, or DCI to instruct (e.g., notify, identify, etc. ) the UE to use the smallest or largest LBT bandwidth index of the LBT bandwidths to determine the transport block size.
  • UE may use the available resources of LBT bandwidth 1 or LBT bandwidth 4 to calculate the transport block size.
  • the protocol may determine which LBT bandwidth the UE uses. For example, the protocol predetermines the UE to use LBT bandwidth with the smallest LBT bandwidth index to determine the transport block size, that is, the UE uses the available resources on LBT bandwidth 1 to calculate the transport block size.
  • the protocol may determine that the UE uses the LBT bandwidth with the largest LBT bandwidth index to determine the transport block size.
  • the UE uses the available resources on LBT bandwidth 1 to calculate the transport block size.
  • the available resources in PUSCH resources on LBT bandwidth 1, 2, 3, 4 may be different.
  • the total number of available REs for PUSCH transmission in LBT bandwidth 1 may be N1
  • the total number of available REs for PUSCH transmission in LBT bandwidth 2 may be N2
  • the total number of available REs for PUSCH transmission in LBT bandwidth 3 may be N3
  • the total number of available REs for PUSCH transmission in LBT bandwidth 4 may be N4, where N1> N3> N4> N2.
  • the network side instructs or the protocol predetermines that the UE uses the available resources in the LBT bandwidth with the least number of available resources to determine the transport block size
  • the UE will use the available resources of the LBT bandwidth 2 to calculate the transport block size.
  • the network side instructs or the protocol predetermines that the UE uses the available resources in the LBT bandwidth with the largest number of resources to determine the transport block size
  • the UE may use the available resources in the LBT bandwidth 1 to calculate the transport block size.
  • the UE may encode and/or modulate the transport block, and map the transport block to LBT bandwidths 1, 2, 3, and 4, respectively. For example, all modulation symbols of the transport block are mapped to the available resources of LBT bandwidth 1. All modulation symbols of the transport block are mapped to the available resources of LBT bandwidth 2. All modulation symbols of the transport block are mapped to the available resources of LBT bandwidth 3. All modulation symbols of the transport block are mapped to LBT bandwidth 4.
  • a transport block mapped to different LBT bandwidths may use the same RV for encoding.
  • the network side may configure the RV for the UE, UE will use the indicated RV for encoding. For example, the network side may configure the RV of the UE as 0, and then the TB uses RV0 for encoding.
  • the transport block mapped to different LBT bandwidths may use different RVs.
  • the network side may configure the RVs used in the configured LBT bandwidths, respectively. For example, the network may configure RV0, RV1, RV2, RV 3 for the transport block mapped to LBT bandwidth 1, 2, 3, 4, respectively for encoding.
  • the RV used for transport block mapped to one LBT bandwidth may be configured by network side and the RVs for transport block mapped to the other LBT bandwidths may be determined according to the configured RV.
  • the RV sequence is 0, 3, 1, and 2.
  • the RV sequence may be configured by network side or pre-defined by protocol.
  • the network side configures the RV used for transport block mapped to LBT bandwidth 1 as 1.
  • the transport block mapped to LBT bandwidth 2, 3, 4 use RVs of 2, 0, 3 for its encoding; respectively.
  • the transport block is encoded with RV1 and mapped to LBT bandwidth 1 after modulation; the transport block is encoded with RV2 and mapped to LBT bandwidth 2 after modulation; the transport block is encoded with RV0 and mapped to LBT bandwidth 3 after modulation; the transport block is encoded with RV3 and modulated onto LBT bandwidth 4 after modulation.
  • a group of PUSCHs are configured by the network via DCI and/or RRC signaling.
  • one or more PUSCHs of the group of PUSCHs carry (e.g. transmit, include, etc. ) the same transport block.
  • the RV used for transport block carried by one PUSCH may be configured by network side and the RVs for transport block carried by the other PUSCHs may be determined according to the configured RV.
  • the transport block may be mapped to LBT bandwidth 1, and the modulation symbols may be mapped to PUSCH resources in the manner of frequency domain first and then time domain.
  • modulation symbols may be mapped to LBT bandwidth 1 in ascending order of the subcarrier index first.
  • the remaining modulation symbols are mapped to the second OFDM symbol in the same order, and the remaining OFDM symbols may be mapped by analogy until the mapping is completed.
  • this transport block may be mapped to LBT bandwidth 2 and 3 in the same manner as that mapped to LBT bandwidth 1.
  • the UE since the CCA is successful only on LBT bandwidths 1, 2, and 3, the UE only sends signals mapped to LBT bandwidths 1, 2, and 3. In some embodiments, UE cancels (drops, punctures, etc. ) the signals mapped to LBT bandwidth 4 if there have been signals mapped to LBT bandwidth 4.
  • the network side may use DCI and/or RRC signaling to configure the UE to send uplink on multiple LBT bandwidths, and the frequency domain resources include multiple LBT bandwidths.
  • the UE when CCA is successful on a part of the LBT bandwidths, the UE does not send a PUSCH (or any signals) at the beginning of the configured PUSCH resource, or sends a channel preemption signal on the part of the LBT bandwidth resources at the beginning of the configured PUSCH resource, and the UE sends one or more PUSCH from the next resource.
  • the time domain length for the beginning of the configured PUSCH resource that UE does not send a PUSCH (or any signals) or sends a channel preemption signal may be pre-defined by the protocol or configured by the network side.
  • the length may be M (M> 0) slots, M OFDM symbols, and/or M milliseconds, etc.
  • the configuration signaling may be DCI, or MAC CE, or RRC signaling.
  • the UE prior to the time-domain resources allocated for sending PUSCH, the UE is not allowed to send PUSCH or allowed to send channel preemption signal (s) for M slots/OFDM symbols/milliseconds.
  • 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 PUSCH configured by the network side using DCI and /or RRC signaling occupies K OFDM symbols in the time domain (e.g., can be a slot or multiple slots) , and occupies 4 LBT bandwidths in the frequency domain (denoted as LBT bandwidth 1, 2, 3, 4, respectively) .
  • CCA is successful on LBT bandwidths 1, 3, and 4, then the UE can only send PUSCH on LBT bandwidths 3 and 4 since LBT bandwidth 3 and 4 are contiguous in frequency domain.
  • FIG. 5 only shows the mapping of a select number of LBT bandwidths and a select number of K OFDM symbols, the mapping may include any number of LBT bandwidths and K OFDM symbols.
  • the UE does not send a PUSCH (or, any signals) or sends a channel preemption signal for the first M OFDM symbols of the PUSCH resource, where the value of M is predetermined by the protocol or configured by the network side.
  • the configuration signaling may be DCI, or MAC CE, or RRC signaling.
  • the protocol may predefine (e.g., determine) that the length of the M OFDM symbols is the same as the time for the UE to prepare the PUSCH.
  • the M value may be related to the subcarrier space and the UE capability.
  • the UE may send the PUSCH on the next PUSCH resource. In other words, the UE sends the PUSCH on the time domain resources after M symbols and the frequency domain resources of the LBT bandwidths 3 and 4.
  • the network side may use DCI and /or RRC signaling to configure the UE to send uplink signals on multiple LBT bandwidths, and its frequency domain resources may include multiple LBT bandwidths.
  • the UE when CCA is on part of the LBT bandwidth, the UE does not send a PUSCH (or any signals) at the beginning of the configured PUSCH resources, or sends a channel preemption signal at the beginning of the PUSCH resources, and sends PUCCH on the next PUSCH resources.
  • the PUCCH may carry at least the LBT bandwidth information on which UE may send PUSCH.
  • the PUCCH may repeatedly be sent on the multiple LBT bandwidths. In some embodiments, if the time domain resource of the first PUSCH is greater than the time domain resource of the PUCCH, the PUCCH may be repeatedly sent on the time domain resource of the first PUSCH. In some embodiments, PUCCH configuration may be configured by the network side. In some embodiments, the UE may send one or more PUSCH on the next resource after transmitting PUCCHs.
  • 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 UE sends a PUSCH on the LBT bandwidth 3 and the LBT bandwidth 4.
  • the first M symbols UE does not send a PUSCH (or any signals) or sends a channel preemption signal.
  • the first PUSCH after M symbols is PUSCH 1, and the number of remaining OFDM symbols is M1, then the UE sends a PUCCH on these M1 symbols and LBT bandwidths 3 and 4.
  • the PUCCH carries at least the LBT bandwidth information of the PUSCH sent by the UE. In other words, it carries at least the information of LBT bandwidths 3 and 4, and the indication method may be a bitmap or LBT bandwidth index.
  • the PUCCH is mapped on one LBT bandwidth, and is repeatedly transmitted on LBT bandwidths 3 and 4. That is, a PUCCH may be transmitted on LBT bandwidth 3 and 4, respectively.
  • the PUCCH if the time domain length of the PUCCH is less than M1, the PUCCH is repeatedly transmitted on M1 OFDM symbols until there is no more resource within PUSCH 1 for PUCCH transmission.
  • UE may send one or more PUSCH from the PUSCH resource 2 (including PUSCH 2) .
  • the PUCCH if the time domain length of the PUCCH is greater than M1, the PUCCH is sent on the next PUSCH resource, that is, the UE is sent on the PUSCH 2 resource.
  • UE may send one or more PUSCH from the PUSCH resource 3 (including PUSCH 3, and PUSCH 3 is not shown in FIG. 7) .
  • the first PUSCH after M symbols is PUSCH 2, and the number of remaining OFDM symbols is M1, then the UE sends a PUCCH on these M1 symbols and LBT bandwidths 3 and 4.
  • the time domain length of the PUCCH is less than M1, the PUCCH is repeatedly transmitted on M1 OFDM symbols.
  • UE may send one or more PUSCH from the PUSCH resource 3 (including PUSCH 3, and PUSCH 3 is not shown in FIG. 7) .
  • the time domain length of the PUCCH is greater than M1, the PUCCH is sent on the next PUSCH resource, that is, the UE sends PUCCH on the PUSCH 3 resource (not shown in FIG. 7) .
  • UE may send one or more PUSCH from the PUSCH resource 4 (including PUSCH 4, and PUSCH 4 is not shown in FIG. 7) .
  • the UE if there is only one PUSCH remaining after the M symbols, the UE does not perform any transmission. In other words, the UE does not transmit a PUCCH and does not transmit a PUSCH (or any other signals) .
  • FIG. 7 only shows the mapping of a select number of LBT bandwidths and a select number of M symbols, the mapping may include any number of LBT bandwidths and M symbols.
  • the transmission method used by the UE is configured by the network side, that is, the network side uses RRC signaling, or MAC CE, or DCI to configure the UE to use the first embodiment, the second embodiment, and/or the third embodiment for transmission.
  • the UE may transmit URLLC service using the Method Two, and the UE may transmit eMBB service using the Method One.
  • the type of service e.g. service priority, data priority, etc.
  • this coupling relationship is configured by the network side via DCI, or MAC CE, or RRC signaling.
  • the UE can obtain the transmission mode according to the service type (e.g. service priority, data priority, etc. ) for transmission configured by the network side and the coupling relationship.
  • UE can obtain the service type (e.g. service priority, data priority, etc. ) for transmission according to the transmission method configured by the network side and the coupling relationship.
  • the PUSCH transmission mode is Method Two.
  • the PUSCH transmission mode is the Method One.
  • the PUSCH transmission mode is Method One.
  • the PUSCH transmission mode is Method Two.
  • the PUSCH transmission mode is Method Three.
  • FIG. 8 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 800 may be performed by a wireless communication node, such as BS 102 in FIG. 1. In some operations, some or all operations of method 800 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 800 includes, in some embodiments, the operation 802 of receiving, by a wireless communication device from a wireless communication node, a signal indicating a plurality of resource block (RB) sets for transmitting a plurality of uplink channels on an unlicensed band.
  • the method includes, in some embodiments, the operation 804 of determining, by the wireless communication device, that one or more of the plurality of RB sets pass a channel access procedure.
  • the method includes, in some embodiments, the operation 806 of transmitting, by the wireless communication device to the wireless communication node, a first uplink channel of the plurality of uplink channels.
  • FIG. 9 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 900 may be performed by a wireless communication node, such as BS 102 in FIG. 1. In some operations, some or all operations of method 800 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 900 includes, in some embodiments, the operation 902 of transmitting, by a wireless communication node to a wireless communication device, a signal indicating a plurality of resource block (RB) sets for transmitting a plurality of uplink channels on an unlicensed band.
  • the signal causes the wireless communication device to: determine that one or more of the plurality of RB sets pass a channel access procedure, and transmit a first uplink channel of the plurality of uplink channels to the wireless communication node.
  • the method includes, in some embodiments, the operation 904 of receiving, by the wireless communication node from the wireless communication device, the first uplink channel of 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)
  • Signal Processing (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Physics & Mathematics (AREA)
  • Health & Medical Sciences (AREA)
  • General Health & Medical Sciences (AREA)
  • Spectroscopy & Molecular Physics (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

L'invention concerne un système et un procédé pour satisfaire aux exigences de retard et de fiabilité d'une transmission de signal pour des URLLC. Le système et le procédé comprennent la réception, par un dispositif de communication sans fil à partir d'un nœud de communication sans fil, d'un signal indiquant une pluralité d'ensembles de blocs de ressources (RB) pour transmettre une pluralité de canaux de liaison montante sur une bande sans licence ; la détermination, par le dispositif de communication sans fil, qu'un ou plusieurs de la pluralité d'ensembles de RB réussissent une procédure d'accès au canal ; et la transmission, par le dispositif de communication sans fil au nœud de communication sans fil, d'un premier canal de liaison montante de la pluralité de canaux de liaison montante.
PCT/CN2020/075358 2020-02-14 2020-02-14 Système et procédé de transmission de signal WO2021098054A1 (fr)

Priority Applications (2)

Application Number Priority Date Filing Date Title
PCT/CN2020/075358 WO2021098054A1 (fr) 2020-02-14 2020-02-14 Système et procédé de transmission de signal
CN202080096479.7A CN115136714A (zh) 2020-02-14 2020-02-14 一种用于信号传输的系统和方法

Applications Claiming Priority (1)

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

Publications (1)

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

Family

ID=75980361

Family Applications (1)

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

Country Status (2)

Country Link
CN (1) CN115136714A (fr)
WO (1) WO2021098054A1 (fr)

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20190037584A1 (en) * 2016-01-21 2019-01-31 Lg Electronics Inc. Uplink transmission method in wireless communication system and device therefor
CN109428626A (zh) * 2017-09-05 2019-03-05 华为技术有限公司 一种信号传输方法、相关设备及系统
WO2020032558A1 (fr) * 2018-08-09 2020-02-13 엘지전자 주식회사 Procédé et dispositif d'émission/réception de signal sans fil dans un système de communication sans fil
WO2020031819A1 (fr) * 2018-08-09 2020-02-13 ソニー株式会社 Dispositif de communication sans fil, procédé de communication sans fil et programme d'ordinateur

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20190037584A1 (en) * 2016-01-21 2019-01-31 Lg Electronics Inc. Uplink transmission method in wireless communication system and device therefor
CN109428626A (zh) * 2017-09-05 2019-03-05 华为技术有限公司 一种信号传输方法、相关设备及系统
WO2020032558A1 (fr) * 2018-08-09 2020-02-13 엘지전자 주식회사 Procédé et dispositif d'émission/réception de signal sans fil dans un système de communication sans fil
WO2020031819A1 (fr) * 2018-08-09 2020-02-13 ソニー株式会社 Dispositif de communication sans fil, procédé de communication sans fil et programme d'ordinateur

Also Published As

Publication number Publication date
CN115136714A (zh) 2022-09-30

Similar Documents

Publication Publication Date Title
CN107317662B (zh) 用于发送和接收上行数据的方法及其装置
WO2021093195A1 (fr) Système et procédé d'attribution de ressources
US20230180244A1 (en) System and method for signal transmission
US20220330321A1 (en) Signaling solution for fast beam diversity
US20220400506A1 (en) System and method for determining downlink control information
WO2021098055A1 (fr) Système et procédé de transmission de signal
US20220361206A1 (en) Signaling solution on reliability enhancement for uplink transmission
US20220360409A1 (en) System and method for sidelink configuration
US20230056864A1 (en) System and method for reference signaling design and configuration
WO2021098054A1 (fr) Système et procédé de transmission de signal
US11432282B2 (en) System and method for scheduling communication resources
US20220159734A1 (en) Systems and methods of enhanced random access procedure
US20220369307A1 (en) System and method for resource allocation
WO2021109480A1 (fr) Configurations pour des transmissions de données économisant les ressources dans un accès à un canal à spectre partagé
US20240147495A1 (en) Systems and methods for dci field size aligned in cc group
WO2024092686A1 (fr) Structures de canal pour blocs de signal de synchronisation de liaison latérale dans des opérations d'écoute avant de parler
US20220360405A1 (en) Method and device for sounding reference signal indication enhancement
US20230199798A1 (en) Method and device for signal transmission
US20220386369A1 (en) Method of data transmission in unlicensed band
US20240048346A1 (en) Systems and methods for uplink transmission scheme in multi-trp operation
US20240106619A1 (en) Systems and methods for public channels and signals
US20230067164A1 (en) Uplink packet duplication transmissions
WO2024065355A1 (fr) Systèmes et procédés d'identification de faisceaux pour transférer des liaisons
US20220369337A1 (en) System and method for signal transmission
US20230403064A1 (en) Determining times for applying beam states for uplink transmissions

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: 20889575

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: 20889575

Country of ref document: EP

Kind code of ref document: A1