WO2023179618A1 - 传输方法、装置、终端及存储介质 - Google Patents

传输方法、装置、终端及存储介质 Download PDF

Info

Publication number
WO2023179618A1
WO2023179618A1 PCT/CN2023/082843 CN2023082843W WO2023179618A1 WO 2023179618 A1 WO2023179618 A1 WO 2023179618A1 CN 2023082843 W CN2023082843 W CN 2023082843W WO 2023179618 A1 WO2023179618 A1 WO 2023179618A1
Authority
WO
WIPO (PCT)
Prior art keywords
uplink transmission
target uplink
target
symbol
time slot
Prior art date
Application number
PCT/CN2023/082843
Other languages
English (en)
French (fr)
Inventor
王理惠
潘学明
Original Assignee
维沃移动通信有限公司
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 维沃移动通信有限公司 filed Critical 维沃移动通信有限公司
Publication of WO2023179618A1 publication Critical patent/WO2023179618A1/zh

Links

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00Arrangements affording multiple use of the transmission path
    • H04L5/14Two-way operation using the same type of signal, i.e. duplex
    • H04L5/16Half-duplex systems; Simplex/duplex switching; Transmission of break signals non-automatically inverting the direction of transmission
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W72/00Local resource management
    • H04W72/04Wireless resource allocation
    • H04W72/044Wireless resource allocation based on the type of the allocated resource
    • H04W72/0446Resources in time domain, e.g. slots or frames
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W72/00Local resource management
    • H04W72/50Allocation or scheduling criteria for wireless resources
    • H04W72/51Allocation or scheduling criteria for wireless resources based on terminal or device properties
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W8/00Network data management
    • H04W8/22Processing or transfer of terminal data, e.g. status or physical capabilities
    • H04W8/24Transfer of terminal data

Definitions

  • This application belongs to the field of communication technology, and specifically relates to a transmission method, device, terminal and storage medium.
  • terminals need to reduce complexity in terms of the number of receiving antennas, transmitting antennas, supported bandwidth, and the time and ability of the terminal to process data and signals.
  • this type of terminal is called a low-capability terminal (Redcued Capability User Equipment, RedCap UE).
  • the terminal when a terminal does not have full-duplex capability, the terminal cannot perform uplink transmission and downlink reception at the same time, and a certain switching time is required between the terminal's uplink transmission and downlink reception or between downlink reception and uplink transmission. .
  • uplink transmission and downlink reception resources conflict or when the switching time between the terminal's uplink transmission and downlink reception is less than the terminal's switching capability or the time specified by the protocol, the terminal gives up uplink transmission, resulting in poor uplink coverage.
  • Embodiments of the present application provide a transmission method, device, terminal and storage medium, which can solve the problem of poor uplink coverage.
  • the first aspect provides a transmission method, which includes:
  • the terminal reports first capability information to the network side device; the first capability information is used to indicate that the terminal does not expect the network side device to enable or configure available time slot counts for the terminal;
  • the terminal performs at least one of the following:
  • the terminal has half-duplex capability or does not have full-duplex capability.
  • the second aspect provides a transmission method, which includes:
  • the network side device receives the first capability information reported by the terminal; the first capability information is used to indicate that the terminal does not expect the network side device to enable or configure available time slot counting for the terminal; the network side device is The terminal does not enable or configure available time slot counting;
  • the network-side device performs at least one of the following:
  • the terminal has half-duplex capability or does not have full-duplex capability.
  • a transmission device which device includes:
  • the first transmission module is configured to report first capability information to the network side device; the first capability information is used to indicate that the terminal does not expect the network side device to enable or configure the available time slot count for the terminal;
  • the terminal has half-duplex capability or does not have full-duplex capability.
  • a transmission device which device includes:
  • the second transmission module is used to receive the first capability information reported by the terminal; the first capability information is used to indicate that the terminal does not expect the network side device to enable or configure the available time slot count for the terminal; the processing module , used to disable or configure available time slot counting for the terminal;
  • the second transmission module is configured to perform at least one of the following when the target condition is met:
  • the terminal has half-duplex capability or does not have full-duplex capability.
  • a terminal in a fifth aspect, includes a processor and a memory.
  • the memory stores programs or instructions that can be run on the processor.
  • the program or instructions are executed by the processor, the following implementations are implemented: The steps of the method described in one aspect.
  • a terminal including a processor and a communication interface; wherein:
  • the communication interface is used to report first capability information to the network side device; the first capability information is used to indicate that the terminal does not expect the network side device to enable or configure available time slot counts for the terminal;
  • the processor is configured to perform at least one of the following when the target condition is met:
  • the terminal has half-duplex capability or does not have full-duplex capability.
  • a network side device in a seventh aspect, includes a processor and a memory.
  • the memory stores programs or instructions that can be run on the processor.
  • the program or instructions are implemented when executed by the processor. The steps of the method as described in the second aspect.
  • a network side device including a processor and a communication interface; wherein:
  • the communication interface is used to receive the first capability information reported by the terminal; the first capability information is used to indicate that the terminal does not expect the network side device to enable or configure available time slot counts for the terminal; the processing The device is used to disable or configure available time slot counting for the terminal;
  • the processor is configured to perform at least one of the following when the target condition is met:
  • the terminal has half-duplex capability or does not have full-duplex capability.
  • a transmission system including: a terminal and a network side device.
  • the terminal can be used to perform the steps of the method described in the first aspect
  • the network side device can be used to perform the steps of the method described in the second aspect. steps of the method.
  • a readable storage medium In a tenth aspect, a readable storage medium is provided. Programs or instructions are stored on the readable storage medium. When the programs or instructions are executed by a processor, the steps of the method described in the first aspect are implemented, or the steps of the method are implemented as described in the first aspect. The steps of the method described in the second aspect.
  • a chip in an eleventh aspect, includes a processor and a communication interface.
  • the communication interface is coupled to the processor.
  • the processor is used to run programs or instructions to implement the method described in the first aspect. Method, or steps for implementing a method as described in the second aspect.
  • a computer program/program product is provided, the computer program/program product is stored in a storage medium, and the computer program/program product is executed by at least one processor to implement the method as described in the first aspect steps, or steps to implement the method described in the second aspect.
  • the terminal when the terminal reports the first capability information to the network side device, the terminal does not expect the network side device to enable or configure the available time slot count for the terminal; or has half-duplex capability or does not have full-duplex capability.
  • the terminal with duplex capability performs at least one of the following: determines that the target time slot in which the terminal's target uplink transmission is located is an unavailable time slot for the target uplink transmission, or determines that the target time slot is not included in the target uplink transmission.
  • the transmission method provided by the embodiment of the present application can realize unified processing when there is resource overlap between the target uplink transmission and downlink reception or the switching time between the target uplink transmission and downlink reception is insufficient, simplifying the behavior and complexity of the terminal, and by determining The target time slot where the terminal's target uplink transmission is located is an unavailable time slot for the target uplink transmission, or the target time slot is determined not to be included in the number of transmissions of the target uplink transmission, and then the target uplink transmission is transmitted in the next available time slot. This can improve uplink coverage.
  • Figure 1 is a schematic diagram of a wireless communication system applicable to the embodiment of the present application.
  • FIG. 2 is one of the flow diagrams of the transmission method provided by the embodiment of the present application.
  • FIG. 3 is the second schematic flowchart of the transmission method provided by the embodiment of the present application.
  • Figure 4 is one of the structural schematic diagrams of the transmission device provided by the embodiment of the present application.
  • Figure 5 is the second structural schematic diagram of the transmission device provided by the embodiment of the present application.
  • Figure 6 is a schematic structural diagram of a communication device provided by an embodiment of the present application.
  • Figure 7 is a schematic structural diagram of a terminal provided by an embodiment of the present application.
  • Figure 8 is a schematic structural diagram of a network-side device provided by an embodiment of the present application.
  • first, second, etc. in the description and claims of this application are used to distinguish similar objects and are not used to describe a specific order or sequence. It is to be understood that the terms so used are interchangeable under appropriate circumstances so that the embodiments of the present application can be practiced in sequences other than those illustrated or described herein, and that "first" and “second” are distinguished objects It is usually one type, and the number of objects is not limited.
  • the first object can be one or multiple.
  • “and/or” in the description and claims indicates at least one of the connected objects, and the character “/" generally indicates that the related objects are in an "or” relationship.
  • LTE Long Term Evolution
  • LTE-Advanced, LTE-A Long Term Evolution
  • LTE-A Long Term Evolution
  • CDMA Code Division Multiple Access
  • TDMA Time Division Multiple Access
  • FDMA Frequency Division Multiple Access
  • OFDMA Orthogonal Frequency Division Multiple Access
  • SC-FDMA Single-carrier Frequency Division Multiple Access
  • NR New Radio
  • FIG 1 is a schematic diagram of a wireless communication system applicable to the embodiment of the present application.
  • the wireless communication system shown in Figure 1 includes a terminal 11 and a network side device 12.
  • the terminal 11 can be a mobile phone, a tablet computer (Tablet Personal Computer), a laptop computer (Laptop Computer), or a notebook computer, a personal digital assistant (Personal Digital Assistant, PDA), a handheld computer, a netbook, or a super mobile personal computer.
  • Tablet Personal Computer Tablet Personal Computer
  • laptop computer laptop computer
  • PDA Personal Digital Assistant
  • PDA Personal Digital Assistant
  • UMPC ultra-mobile personal computer
  • UMPC mobile Internet device
  • Mobile Internet Device MID
  • augmented reality augmented reality, AR
  • VR virtual reality
  • robots wearable devices
  • VUE vehicle-mounted equipment
  • PUE pedestrian terminal
  • smart home home equipment with wireless communication functions, such as refrigerators, TVs, washing machines or furniture, etc.
  • game consoles personal computers (personal computers, PC), teller machines or self-service Terminal devices
  • wearable devices include: smart watches, smart bracelets, smart headphones, smart glasses, smart jewelry (smart bracelets, smart bracelets, smart rings, smart necklaces, smart anklets, smart anklets, etc.), Smart wristbands, smart clothing, etc. It should be noted that the embodiment of the present application does not limit the specific type of the terminal 11.
  • the network side device 12 may include an access network device or a core network device, where the access network device may also be called a radio access network device, a radio access network (Radio Access Network, RAN), a radio access network function or a wireless device. access network unit. Access network equipment may include base stations, WLAN access points or WiFi nodes, etc.
  • the base stations may be called Node B, Evolved Node B (eNB), Access Point, Base Transceiver Station (BTS), Radio Base Station , radio transceiver, Basic Service Set (BSS), Extended Service Set (ESS), Home B-Node, Home Evolved B-Node, Transmitting Receiving Point (TRP) or the above
  • eNB Evolved Node B
  • BTS Base Transceiver Station
  • ESS Extended Service Set
  • Home B-Node Home Evolved B-Node
  • TRP Transmitting Receiving Point
  • Core network equipment may include but is not limited to at least one of the following: core network nodes, core network functions, mobility management entities (Mobility Management Entity (MME), Access and Mobility Management Function (AMF), Session Management Function (SMF), User Plane Function (UPF), Policy Control Function , PCF), Policy and Charging Rules Function (PCRF), Edge Application Server Discovery Function (EASDF), Unified Data Management (UDM), Unified Data Warehousing (Unified Data Repository, UDR), Home Subscriber Server (HSS), Centralized network configuration (CNC), Network Repository Function (NRF), Network Exposure Function, NEF), local NEF (LocalNEF, or L-NEF), binding support function (Binding Support Function, BSF), application function (Application Function, AF), location management function (LMF), enhanced service mobile positioning Center (Enhanced Serving Mobile Location Centre, E-SMLC), network data analytics function (NWDAF), etc.
  • MME Mobility Management Entity
  • AMF Access and Mobility Management Function
  • SMF Session Management
  • FIG 2 is one of the flow diagrams of the transmission method provided by the embodiment of the present application. As shown in Figure 2, the method includes:
  • Step 201 The terminal reports first capability information to the network side device; the first capability information is used to indicate that the terminal does not expect the network side device to enable or configure available time slot counts for the terminal;
  • the terminal performs at least one of the following:
  • the terminal has half-duplex capability or does not have full-duplex capability.
  • the terminal includes a low-capability terminal (RedCap UE), such as RedCap half-duplex (Half Duplex-frequency-division duplex, HD-FDD) UE.
  • RedCap UE low-capability terminal
  • Network-side devices include but are not limited to the types of network-side devices 12 listed above, and this application is not limited thereto.
  • the first capability information is used to indicate that the terminal does not expect the network side device to enable or configure the available time slot count for the terminal.
  • the first capability information may include at least one of the following: 1) having half-duplex capability; 2) not having full-duplex capability.
  • the terminal reports the first capability information to the network side device, the terminal does not expect the network side device to enable available slot counting (AvailableSlotCounting) for the terminal.
  • the network side device receives the first capability information reported by the terminal, and the network side device does not enable or configure available time slot counting for the terminal.
  • Terminals with half-duplex capability or terminals without full-duplex capability do not support a mechanism in which the number of uplink repeated transmissions (such as PUSCH repetition Type A or PUCCH) is based on the available slot count.
  • the terminal reports to the network side device that the terminal is a half-duplex terminal, assuming that the terminal reports: RedCap UE with Half-duplex FDD operation type A (operation type A), the terminal does not expect the network
  • the side device configures or enables available time slot counting.
  • the target conditions in the embodiment of this application may include at least one of the following:
  • the network side device enables or configures available time slot counting for the terminal's uplink transmission.
  • the network side device disables or does not configure available time slot counting for the terminal's uplink transmission.
  • the switching time between the target uplink transmission and the downlink reception may include at least one of the following: a) the time interval between the last symbol of the target uplink transmission and the first symbol of the downlink reception; b ) The time interval between the last symbol received in the downlink and the first symbol transmitted in the target uplink.
  • uplink and downlink switching time overlap when there is no resource overlap between target uplink transmission and downlink reception, and the switching time between target uplink transmission and downlink reception is less than the target time, it can also be referred to as: uplink and downlink switching time overlap.
  • the downlink transmission is Synchronization Signal/PBCH block (SSB) as an example.
  • SSB and uplink transmission (such as PUSCH) do not overlap, but the switching time between uplink transmission and downlink reception is less than the first time, or the switching time between downlink reception and uplink transmission is less than the second time.
  • the value of the target time may include the first time or the second time.
  • the number of transmissions is greater than 1, or the number of transmissions is equal to 1;
  • the target uplink transmission is an uplink transmission configured semi-statically by Radio Resource Control (RRC); or the target uplink transmission is a dynamically scheduled uplink transmission.
  • RRC Radio Resource Control
  • the uplink transmission of the RRC semi-static configuration may include at least one of the following:
  • PUSCH Type 1 (CG PUSCH Type 1) of RRC semi-statically configured grant scheduling (configured grant);
  • Physical Random Access Channel Physical Random Access Channel, PRACH
  • the dynamically scheduled uplink transmission may include at least one of the following:
  • uplink grant includes: DCI format 0_0, DCI format 0_1 or DCI format 0_2, etc.
  • TC-RNTI Temporary Cell Radio Network Temporary Identifier
  • Dynamically scheduled PRACH for example, dynamically scheduled PRACH is the transmission of PRACH scheduled by PDCCH order.
  • SRS Dynamically scheduled Sounding Reference Signal
  • the downlink reception may include at least one of the following:
  • Type0 Common Search Space Type0 CSS, Type0A CSS, Type1 CSS and Type2 CSS;
  • the SSB may include at least one of the following:
  • SSB configured by the position of the synchronized broadcast block in the set (ssb-PositionsInBurst);
  • SSB configured by non-cell defining SSB (nonCellDefiningSSB) related signaling
  • SSB configured by dedicated downlink partial bandwidth (BWP-DownlinkDedicated) signaling
  • the terminal determines that the target time slot in which the terminal's target uplink transmission is located is an unavailable time slot for the target uplink transmission, or determines that the target time slot is not included in the number of transmissions of the target uplink transmission. Under this condition, the terminal transmits the target uplink transmission in the next available time slot. line uplink transmission.
  • the terminal when the terminal reports the first capability information to the network side device, the terminal does not expect the network side device to enable or configure the available time slot count for the terminal; or has half-duplex capability or When the target conditions are met, the terminal without full-duplex capability performs at least one of the following: determines that the target time slot in which the terminal's target uplink transmission is located is an unavailable time slot for the target uplink transmission, or determines that the target time slot is not included in the calculation Among the number of transmissions of the target uplink transmission; resource overlap between the target uplink transmission and downlink reception is not expected, or the switching time between the target uplink transmission and downlink reception is not expected to be less than the target time; the target uplink transmission is abandoned; and downlink reception is performed.
  • the transmission method provided by the embodiment of the present application can realize unified processing when there is resource overlap between the target uplink transmission and downlink reception or the switching time between the target uplink transmission and downlink reception is insufficient, simplifying the behavior and complexity of the terminal, and by determining The target time slot where the terminal's target uplink transmission is located is an unavailable time slot for the target uplink transmission, or the target time slot is determined not to be included in the number of transmissions of the target uplink transmission, and then the target uplink transmission is transmitted in the next available time slot. This can improve uplink coverage.
  • the terminal behavior performed by the terminal based on different target conditions may correspond to at least one of the following situations:
  • the terminal behavior may include the following At least one way:
  • Tc represents the basic time unit (Basic time unit);
  • NRX-TX represents the switching time between downlink reception and uplink transmission;
  • NTX-RX represents the switching time between uplink transmission and downlink reception.
  • SSB Synchronous Broadcast Signal Block
  • the terminal behavior may include at least one of the following ways:
  • SSB Synchronous Broadcast Signal Block
  • the terminal behavior may include at least one of the following methods:
  • Method 3-1 For the repeated transmission of PUSCH configured and authorized by the half-duplex terminal or the PUCCH transmitted by the semi-static configuration or the repeated transmission of other PRACH not triggered by the PDCCH order:
  • the terminal behavior may include at least one of the following methods:
  • Method 4-1 For half-duplex terminals, PUSCH repeated transmission scheduled by uplink DCI format, or PUCCH transmission scheduled by DCI, or PRACH triggered by PDCCH order:
  • the space between the last symbols of symbols is less than/less than NRX-TX*Tc, and/or HD-FDD UE does not expect the interval between the last symbol of a PUSCH or PUCCH or PRACH repeated transmission and the first symbol of a Synchronous Broadcast Signal Block (SSB) transmission symbol to be smaller/less than NTX-RX*Tc.
  • the interval between the last symbol of the symbol is smaller/less than NRX-TX*Tc, and/or the HD-FDD UE does not expect a PUSCH or PUCCH or PRACH repeated transmission of the last symbol and the Synchronous Broadcast Signal Block (SSB) transmission symbol
  • the spacing between the first symbols is smaller/less than NTX-RX*Tc.
  • Method 4-3 For half-duplex terminals, PUSCH repeated transmission scheduled by uplink DCI format, or PUCCH transmission scheduled by DCI, or PRACH triggered by PDCCH order:
  • the interval between the last symbol of the symbol is smaller/less than NRX-TX*Tc, and/or the HD-FDD UE does not expect a PUSCH or PUCCH or PRACH repeated transmission of the last symbol and the Synchronous Broadcast Signal Block (SSB) transmission symbol
  • the spacing between the first symbols is smaller/less than NTX-RX*Tc.
  • the terminal behavior may include at least one of the following methods:
  • Method 5-1 for PUSCH repeated transmission of configuration authorization of half-duplex terminal, or PUCCH of semi-static configuration transmission, or repeated transmission of other PRACH not triggered by PDCCH order:
  • the HD-FDD UE determines that the PUSCH or The time slot in which PUCCH or PRACH is located is an unavailable time slot, or the time slot is not included in the K time slots for PUSCH, PUCCH or PRACH transmission. HD-FDD UE will postpone the repeated transmission of PUSCH, PUCCH or PRACH to the next available time. gap.
  • the HD-FDD UE does not transmit the PUSCH Or PUCCH or PRACH, that is, the HD-FDD UE determines that the time slot in which the PUSCH or PUCCH or PRACH is located is an available time slot, or the time slot is included in the In K time slots of PUSCH or PUCCH or PRACH transmission.
  • the HD-FDD UE does not transmit the PUSCH, PUCCH or PRACH, that is, the HD-FDD UE determines that the time slot where the PUSCH, PUCCH or PRACH is located is an available time slot, or the time slot is included in the PUSCH or PRACH. In K time slots of PUCCH or PRACH transmission.
  • the terminal behavior may include at least one of the following methods:
  • Method 6-1 For half-duplex terminals, PUSCH repeated transmission scheduled by uplink DCI format, or PUCCH transmission scheduled by DCI, or PRACH triggered by PDCCH order:
  • the HD-FDD UE does not expect that the interval between the first symbol of a PUSCH or PUCCH or PRACH repeated transmission and the last symbol of the Synchronous Broadcast Signal Block (SSB) transmission symbol is less than/less than For NRX-TX*Tc, and/or HD-FDD UEs do not expect the interval between the last symbol of a PUSCH or PUCCH or PRACH repeat transmission and the first symbol of a Synchronous Broadcast Signal Block (SSB) transmission symbol to be less/less on NTX-RX*Tc.
  • SSB Synchronous Broadcast Signal Block
  • the interval between the last symbol of the symbol is smaller/less than NRX-TX*Tc, and/or the HD-FDD UE does not expect a PUSCH or PUCCH or PRACH repeated transmission of the last symbol and the Synchronous Broadcast Signal Block (SSB) transmission symbol
  • the spacing between the first symbols is smaller/less than NTX-RX*Tc.
  • Method 6-2 For half-duplex terminals, PUSCH repeated transmission scheduled by uplink DCI format, or PUCCH transmission scheduled by DCI, or PRACH triggered by PDCCH order:
  • the HD-FDD UE does not expect that the interval between the first symbol of a PUSCH or PUCCH or PRACH repeated transmission and the last symbol of the Synchronous Broadcast Signal Block (SSB) transmission symbol is less than/less than For NRX-TX*Tc, and/or HD-FDD the UE does not expect the interval between the last symbol of a PUSCH or PUCCH or PRACH repeat transmission and the first symbol of a Synchronous Broadcast Signal Block (SSB) transmission symbol to be less than/less than on NTX-RX*Tc.
  • SSB Synchronous Broadcast Signal Block
  • the interval between the last symbol of the symbol is smaller/less than NRX-TX*Tc, and/or the HD-FDD UE does not expect a PUSCH or PUCCH or PRACH repeated transmission of the last symbol and the Synchronous Broadcast Signal Block (SSB) transmission symbol
  • the spacing between the first symbols is smaller/less than NTX-RX*Tc.
  • Method 6-3 For half-duplex terminals, PUSCH repeated transmission scheduled by uplink DCI format, or PUCCH transmission scheduled by DCI, or PRACH triggered by PDCCH order:
  • the interval between the last symbol of the symbol is smaller/less than NRX-TX*Tc, and/or the HD-FDD UE does not expect a PUSCH or PUCCH or PRACH repeated transmission of the last symbol and the Synchronous Broadcast Signal Block (SSB) transmission symbol
  • the spacing between the first symbols is smaller/less than NTX-RX*Tc.
  • Method 6-4 For half-duplex terminals, PUSCH repeated transmission scheduled by uplink DCI format, or PUCCH transmission scheduled by DCI, or PRACH triggered by PDCCH order:
  • the transmission method provided by the embodiment of the present application realizes the joint operation of the half-duplex RedCap terminal and the uplink coverage enhancement mechanism based on effective slot count, and particularly provides the uplink and downlink conversion time between PUSCH repetition type A and SSB resources.
  • Figure 3 is a second schematic flowchart of a transmission method provided by an embodiment of the present application. As shown in Figure 3, the method includes:
  • Step 301 The network side device receives the first capability information reported by the terminal; the first capability information is used to indicate that the terminal does not expect the network side device to enable or configure the available time slot count for the terminal; the network The side device does not enable or configure available time slot counting for the terminal;
  • the network-side device performs at least one of the following:
  • the terminal has half-duplex capability or does not have full-duplex capability.
  • the terminal includes a low-capability terminal (RedCap UE), such as RedCap half-duplex (HalfDuplex-frequency-division duplex, HD-FDD) UE.
  • RedCap UE low-capability terminal
  • Network-side devices include but are not limited to the types of network-side devices 12 listed above, and this application is not limited thereto.
  • the first capability information is used to indicate that the terminal does not expect the network side device to enable or configure the available time slot count for the terminal.
  • the first capability information may include at least one of the following: 1) having half-duplex capability; 2) not having full-duplex capability.
  • the terminal reports the first capability information to the network side device, the terminal does not expect the network side device to enable available slot counting (AvailableSlotCounting) for the terminal.
  • the network side device receives the first capability information reported by the terminal, and the network side device The network side device does not enable or configure available time slot counting for the terminal.
  • Terminals with half-duplex capability or terminals without full-duplex capability do not support a mechanism in which the number of uplink repeated transmissions (such as PUSCH repetition Type A or PUCCH) is based on the available slot count.
  • the terminal reports to the network side device that the terminal is a half-duplex terminal, assuming that the terminal reports: RedCap UE with Half-duplex FDD operation type A (operation type A), the terminal does not expect the network
  • the side device configures or enables available time slot counting.
  • the target conditions include at least one of the following:
  • the number of transmissions is greater than 1, or the number of transmissions is equal to 1;
  • the target uplink transmission is an uplink transmission configured semi-statically by Radio Resource Control (RRC); or the target uplink transmission is a dynamically scheduled uplink transmission.
  • RRC Radio Resource Control
  • the switching time between the target uplink transmission and downlink reception includes at least one of the following:
  • the time interval between the last symbol received in the downlink and the first symbol transmitted in the target uplink is the time interval between the last symbol received in the downlink and the first symbol transmitted in the target uplink.
  • the uplink transmission of the RRC semi-static configuration includes at least one of the following:
  • RRC semi-statically configured physical uplink control channel PUCCH transmission
  • RRC semi-statically configured grant-scheduled PUSCH Type 2 CG PUSCH Type2;
  • Physical random access channel PRACH transmission Physical random access channel PRACH transmission.
  • the dynamically scheduled uplink transmission includes at least one of the following:
  • the first CG PUSCH after DCI activates CG PUSCH Type 2;
  • the downlink reception includes at least one of the following:
  • Synchronization signal/physical broadcast channel block SSB Synchronization signal/physical broadcast channel block
  • Downlink search space SS associated with control resource set #0CORESET#0.
  • the SSB includes at least one of the following:
  • SSB configured by non-cell-defined SSB nonCellDefiningSSB related signaling
  • SSB configured by dedicated downlink partial bandwidth BWP-DownlinkDedicated signaling
  • SSB configured by UE-specific signaling
  • the SSB contained in the terminal's currently active BWP The SSB contained in the terminal's currently active BWP.
  • the first capability information reported by the terminal is received through the network side device; the first capability information is used to indicate that the terminal does not expect the network side device to enable or configure the terminal. Counting available time slots; the network side device does not enable or configure available time slot counting for the terminal based on the first capability information; or when the target conditions are met, the network side device performs at least one of the following: Determine the terminal The target time slot in which the target uplink transmission is located is an unavailable time slot for the target uplink transmission, or it is determined that the target time slot is not included in the target uplink transmission.
  • the terminal has half-duplex capability or does not have full-duplex capability.
  • the transmission method provided by the embodiment of the present application can realize unified processing when there is resource overlap between the target uplink transmission and downlink reception or the switching time between the target uplink transmission and downlink reception is insufficient, simplifying the behavior and complexity of the terminal, and by determining The target time slot where the terminal's target uplink transmission is located is an unavailable time slot for the target uplink transmission, or the target time slot is determined not to be included in the number of transmissions of the target uplink transmission, and then the target uplink transmission is transmitted in the next available time slot. This can improve uplink coverage.
  • the execution subject may be a transmission device.
  • a transmission device performing a transmission method is used as an example to illustrate the transmission device provided by the embodiment of the present application.
  • Figure 4 is one of the schematic structural diagrams of a transmission device provided by an embodiment of the present application. As shown in Figure 4, the transmission device 400 is applied to a terminal and includes:
  • the first transmission module 401 is configured to report first capability information to the network side device; the first capability information is used to indicate that the terminal does not expect the network side device to enable or configure the available time slot count for the terminal;
  • the terminal has half-duplex capability or does not have full-duplex capability.
  • the terminal when the first capability information is reported to the network side device, the terminal does not expect the network side device to enable or configure the available time slot count for the terminal; or when the target conditions are met. , do at least one of the following: Determine whether it has half-duplex capability or not The target time slot where the target uplink transmission of a terminal with full-duplex capability is located is an unavailable time slot for the target uplink transmission, or it is determined that the target time slot is not included in the number of transmissions of the target uplink transmission; the difference between the target uplink transmission and the downlink reception is not expected.
  • the transmission device provided by the embodiment of the present application can realize unified processing when there is resource overlap between the target uplink transmission and downlink reception or the switching time between the target uplink transmission and downlink reception is insufficient, simplifying the behavior and complexity of the terminal, and by determining The target time slot where the terminal's target uplink transmission is located is an unavailable time slot for the target uplink transmission, or the target time slot is determined not to be included in the number of transmissions of the target uplink transmission, and then the target uplink transmission is transmitted in the next available time slot. This can improve uplink coverage.
  • the target conditions include at least one of the following:
  • the number of transmissions is greater than 1, or the number of transmissions is equal to 1;
  • the target uplink transmission is an uplink transmission configured semi-statically by Radio Resource Control (RRC); or the target uplink transmission is a dynamically scheduled uplink transmission.
  • RRC Radio Resource Control
  • the switching time between the target uplink transmission and downlink reception includes at least one of the following:
  • the time interval between the last symbol received in the downlink and the first symbol transmitted in the target uplink is the time interval between the last symbol received in the downlink and the first symbol transmitted in the target uplink.
  • the uplink transmission of the RRC semi-static configuration includes at least one of the following:
  • RRC semi-statically configured physical uplink control channel PUCCH transmission
  • RRC semi-statically configured grant scheduled PUSCH type 1 CG PUSCH Type1;
  • RRC semi-statically configured grant-scheduled PUSCH Type 2 CG PUSCH Type2;
  • Physical random access channel PRACH transmission Physical random access channel PRACH transmission.
  • the dynamically scheduled uplink transmission includes at least one of the following:
  • the first CG PUSCH after DCI activates CG PUSCH Type 2;
  • the first transmission module 401 is further used for:
  • the target time slot in which the terminal's target uplink transmission is located is an unavailable time slot for the target uplink transmission, or it is determined that the target time slot is not counted. into the number of transmissions of the target uplink transmission; or,
  • the first transmission module 401 is further used for:
  • the target time slot in which the terminal's target uplink transmission is located is an available time slot for the target uplink transmission, or it is determined that the target time slot is included in the target uplink transmission Among the number of transmissions of the target uplink transmission; or,
  • the target time slot in which the terminal's target uplink transmission is located is the available time for the target uplink transmission. slot, or determine that the target time slot is included in the number of transmissions of the target uplink transmission; or,
  • the AvailableSlotCounting is started or enabled and the number of transmissions K>1, when the interval between the first symbol of the target uplink transmission and the last symbol of the downlink reception is less than the first threshold, and/or the When the interval between the last symbol of the target uplink transmission and the first symbol of the downlink reception is less than the second threshold, determine that the target time slot in which the terminal's target uplink transmission is located is an available time slot for the target uplink transmission, or determine that the The target time slot is included in the number of transmissions of the target uplink transmission.
  • the downlink reception includes at least one of the following:
  • Synchronization signal/physical broadcast channel block SSB Synchronization signal/physical broadcast channel block
  • Downlink search space SS associated with control resource set #0 CORESET#0.
  • the SSB includes at least one of the following:
  • SSB configured by non-cell-defined SSB nonCellDefiningSSB related signaling
  • SSB configured by dedicated downlink partial bandwidth BWP-DownlinkDedicated signaling
  • SSB configured by UE-specific signaling
  • the SSB contained in the terminal's currently active BWP The SSB contained in the terminal's currently active BWP.
  • the first capability information includes at least one of the following:
  • the terminal includes: a low-capability terminal RedCap UE.
  • the transmission device in the embodiment of the present application may be an electronic device, such as an electronic device with an operating system, or may be a component in the electronic device, such as an integrated circuit or chip.
  • the electronic device may be a terminal or other devices other than the terminal.
  • terminals may include but are not limited to the types of terminals 11 listed above, and other devices may be servers, network attached storage (Network Attached Storage, NAS), etc., which are not specifically limited in the embodiment of this application.
  • NAS Network Attached Storage
  • the transmission device provided by the embodiment of the present application can implement each process implemented by the method embodiment shown in Figure 2 and achieve the same technical effect. To avoid duplication, the details will not be described here.
  • Figure 5 is a second structural schematic diagram of a transmission device provided by an embodiment of the present application. As shown in Figure 5, the transmission device 500 is applied to network side equipment and includes:
  • the second transmission module 501 is used to receive the first capability information reported by the terminal; the first capability information is used to indicate that the terminal does not expect the network side device to enable or configure the available time slot count for the terminal; processing Module 502, configured to disable or configure available time slot counting for the terminal;
  • the second transmission module 501 is used to perform the following steps when the target condition is met: One item missing:
  • the terminal has half-duplex capability or does not have full-duplex capability.
  • the transmission device receives the first capability information reported by the terminal; the first capability information is used to indicate that the terminal does not expect the network side device to enable or configure the available time slot count for the terminal. ; Disabling or not configuring the available time slot count for the terminal based on the first capability information; or if the target condition is met, performing at least one of the following: Determining that the target time slot in which the terminal's target uplink transmission is located is the Unavailable time slots for target uplink transmission, or determine that the target time slot is not counted in the number of transmissions for the target uplink transmission; configure that there is no resource overlap between target uplink transmission and downlink reception, or configure target uplink transmission and downlink reception The switching time is not less than the target time; the target uplink reception is given up; the target uplink transmission is received; and the downlink transmission is performed; wherein the terminal has half-duplex capability or does not have full-duplex capability.
  • the transmission device provided by the embodiment of the present application can realize unified processing when there is resource overlap between the target uplink transmission and downlink reception or the switching time between the target uplink transmission and downlink reception is insufficient, simplifying the behavior and complexity of the terminal, and by determining The target time slot where the terminal's target uplink transmission is located is an unavailable time slot for the target uplink transmission, or the target time slot is determined not to be included in the number of transmissions of the target uplink transmission, and then the target uplink transmission is transmitted in the next available time slot. This can improve uplink coverage.
  • the target conditions include at least one of the following:
  • the number of transmissions is greater than 1, or the number of transmissions is equal to 1;
  • the target uplink transmission is an uplink transmission configured semi-statically by Radio Resource Control (RRC); or the target uplink transmission is a dynamically scheduled uplink transmission.
  • RRC Radio Resource Control
  • the switching time between the target uplink transmission and downlink reception includes at least one of the following:
  • the time interval between the last symbol received in the downlink and the first symbol transmitted in the target uplink is the time interval between the last symbol received in the downlink and the first symbol transmitted in the target uplink.
  • the uplink transmission of the RRC semi-static configuration includes at least one of the following:
  • RRC semi-statically configured physical uplink control channel PUCCH transmission
  • RRC semi-statically configured grant-scheduled PUSCH Type 2 CG PUSCH Type2;
  • Physical random access channel PRACH transmission Physical random access channel PRACH transmission.
  • the dynamically scheduled uplink transmission includes at least one of the following:
  • the first CG PUSCH after DCI activates CG PUSCH Type 2;
  • the second transmission module 501 is further used to:
  • the target time slot in which the terminal's target uplink transmission is located is an unavailable time slot for the target uplink transmission, or it is determined that the target time slot is not counted. into the number of transmissions of the target uplink transmission; or,
  • the second transmission module 501 is further used to:
  • the target time slot in which the terminal's target uplink transmission is located is an available time slot for the target uplink transmission, or it is determined that the target time slot is included in the target uplink transmission Among the number of transmissions of the target uplink transmission; or,
  • the target time slot in which the terminal's target uplink transmission is located is the available time for the target uplink transmission. slot, or determine that the target time slot is included in the number of transmissions of the target uplink transmission; or,
  • the AvailableSlotCounting is started or enabled and the number of transmissions K>1, when the interval between the first symbol of the target uplink transmission and the last symbol of the downlink reception is less than the first threshold, and/or the When the interval between the last symbol of the target uplink transmission and the first symbol of the downlink reception is less than the second threshold, determine that the target time slot in which the terminal's target uplink transmission is located is an available time slot for the target uplink transmission, or determine that the The target time slot is included in the number of transmissions of the target uplink transmission.
  • the downlink reception includes at least one of the following:
  • Synchronization signal/physical broadcast channel block SSB Synchronization signal/physical broadcast channel block
  • Downlink search space SS associated with control resource set #0 CORESET#0.
  • the SSB includes at least one of the following:
  • SSB configured by non-cell-defined SSB nonCellDefiningSSB related signaling
  • SSB configured by dedicated downlink partial bandwidth BWP-DownlinkDedicated signaling
  • SSB configured by UE-specific signaling
  • the SSB contained in the terminal's currently active BWP The SSB contained in the terminal's currently active BWP.
  • the first capability information includes at least one of the following:
  • the terminal includes: a low-capability terminal RedCap UE.
  • Figure 6 is a schematic structural diagram of a communication device provided by an embodiment of the present application.
  • the communication device 600 includes a processor 601 and a memory 602.
  • the memory 602 stores programs that can run on the processor 601. or instructions.
  • the communication device 600 is a terminal
  • the program or instructions are executed by the processor 601
  • each step of the above terminal-side transmission method embodiment is implemented, and the same technical effect can be achieved.
  • the communication device 600 is a network-side device
  • the program or instruction is executed by the processor 601
  • the steps of the above-mentioned network-side device-side transmission method embodiment are implemented, and the same technical effect can be achieved. To avoid duplication, they will not be described again here. .
  • An embodiment of the present application also provides a terminal, including a processor and a communication interface; wherein:
  • the communication interface is used to report first capability information to the network side device; the first capability information is used to indicate that the terminal does not expect the network side device to enable or configure available time slot counts for the terminal;
  • the processor is configured to perform at least one of the following when the target condition is met:
  • the terminal has half-duplex capability or does not have full-duplex capability.
  • This terminal embodiment corresponds to the above-mentioned terminal-side method embodiment.
  • Each implementation process and implementation manner of the above-mentioned method embodiment can be applied to this terminal embodiment, and can achieve the same technical effect.
  • Figure 7 is a schematic structural diagram of a terminal provided by an embodiment of the present application.
  • the terminal 700 includes but is not limited to: a radio frequency unit 701, a network module 702, an audio output unit 703, an input unit 704, a sensor 705, and a display unit. 706. At least some components of the user input unit 707, the interface unit 708, the memory 709, the processor 710, etc.
  • the terminal 700 may also include a power supply (such as a battery) that supplies power to various components.
  • the power supply may be logically connected to the processor 710 through the power management system, thereby through The power management system implements functions such as managing charging, discharging, and power consumption management.
  • the terminal structure shown in FIG. 7 does not constitute a limitation on the terminal.
  • the terminal may include more or fewer components than shown in the figure, or some components may be combined or arranged differently, which will not be described again here.
  • the input unit 704 may include a graphics processing unit (Graphics Processing Unit, GPU) 7041 and a microphone 7042.
  • the graphics processor 7041 is responsible for the image capture device (GPU) in the video capture mode or the image capture mode. Process the image data of still pictures or videos obtained by cameras (such as cameras).
  • the display unit 706 may include a display panel 7061, which may be configured in the form of a liquid crystal display, an organic light emitting diode, or the like.
  • the user input unit 707 includes a touch panel 7071 and at least one of other input devices 7072 .
  • Touch panel 7071 also called touch screen.
  • the touch panel 7071 may include two parts: a touch detection device and a touch controller.
  • Other input devices 7072 may include but are not limited to physical keyboards, function keys (such as volume control keys, switch keys, etc.), trackballs, mice, and joysticks, which will not be described again here.
  • the radio frequency unit 701 after receiving downlink data from the network side device, can transmit it to the processor 710 for processing; in addition, the radio frequency unit 701 can send uplink data to the network side device.
  • the radio frequency unit 701 includes, but is not limited to, an antenna, amplifier, transceiver, coupler, low noise amplifier, duplexer, etc.
  • Memory 709 may be used to store software programs or instructions as well as various data.
  • the memory 709 may mainly include a first storage area for storing programs or instructions and a second storage area for storing data, wherein the first storage area may store an operating system, an application program or instructions required for at least one function (such as a sound playback function, Image playback function, etc.) etc.
  • memory 709 may include volatile memory or non-volatile memory, or memory 709 may include both volatile and non-volatile memory.
  • the non-volatile memory can be read-only memory (Read-Only Memory, ROM), programmable read-only memory (Programmable ROM, PROM), erasable programmable read-only memory (Erasable PROM, EPROM), electrically removable memory. Erase programmable read-only memory (Electrically EPROM, EEPROM) or flash memory.
  • Volatile memory can be random access memory (Random Access Memory, RAM), static random access memory (Static RAM, SRAM), dynamic random access memory (Dynamic RAM, DRAM), synchronous dynamic random access memory (Synchronous DRAM, SDRAM), double data rate synchronous dynamic random access memory (Double Data Rate SDRAM, DDRSDRAM), enhanced synchronous dynamic random access memory (Enhanced SDRAM, ESDRAM), synchronous connection dynamic random access memory (Synch link DRAM, SLDRAM) and Direct Rambus RAM (DRRAM).
  • RAM Random Access Memory
  • Static RAM static random access memory
  • DRAM dynamic random access memory
  • DRAM synchronous dynamic random access memory
  • SDRAM double data rate synchronous dynamic random access memory
  • Double Data Rate SDRAM Double Data Rate SDRAM
  • ESDRAM enhanced synchronous dynamic random access memory
  • Synch link DRAM, SLDRAM synchronous connection dynamic random access memory
  • DRRAM Direct Rambus RAM
  • the processor 710 may include one or more processing units; optionally, the processor 710 integrates an application processor and a modem processor, where the application processor mainly handles operations related to the operating system, user interface, application programs, etc., Modem processors mainly process wireless communication signals, such as baseband processors. It can be understood that the above-mentioned modem processor may not be integrated into the processor 710.
  • the radio frequency unit 701 is used to report the first capability information to the network side device; the first capability information is used to indicate that the terminal does not expect the network side device to enable or configure the available time slot count for the terminal;
  • the processor 710 is configured to perform at least one of the following if the target condition is met:
  • the terminal has half-duplex capability or does not have full-duplex capability.
  • the terminal provided in the embodiment of the present application reports the first capability information to the network side device.
  • the terminal does not expect the network side device to enable or configure the available time slot count for the terminal; or has half-duplex capability or does not have full-duplex capability.
  • the terminal with duplex capability performs at least one of the following: the target time slot where the determined target uplink transmission is located is an unavailable time slot for the target uplink transmission, or the target time slot is determined not to be included in the target uplink transmission. In the number of transmissions; resource overlap between the target uplink transmission and downlink reception is not expected, or resource overlap between the target uplink transmission and downlink reception is not expected.
  • the switching time is less than the target time; the target uplink transmission is abandoned; the downlink reception is performed.
  • the terminal provided by the embodiment of the present application can realize unified processing when there is resource overlap between the target uplink transmission and downlink reception or the switching time between the target uplink transmission and downlink reception is insufficient, simplifying the behavior and complexity of the terminal, and by determining the terminal
  • the target time slot where the target uplink transmission is located is an unavailable time slot for the target uplink transmission, or it is determined that the target time slot is not included in the number of transmissions of the target uplink transmission, and then the target uplink transmission is transmitted in the next available time slot, so Can improve uplink coverage.
  • the target conditions include at least one of the following:
  • the number of transmissions is greater than 1, or the number of transmissions is equal to 1;
  • the target uplink transmission is an uplink transmission configured semi-statically by Radio Resource Control (RRC); or the target uplink transmission is a dynamically scheduled uplink transmission.
  • RRC Radio Resource Control
  • the switching time between the target uplink transmission and downlink reception includes at least one of the following:
  • the time interval between the last symbol received in the downlink and the first symbol transmitted in the target uplink is the time interval between the last symbol received in the downlink and the first symbol transmitted in the target uplink.
  • the uplink transmission of the RRC semi-static configuration includes at least one of the following:
  • RRC semi-statically configured physical uplink control channel PUCCH transmission
  • RRC semi-statically configured grant-scheduled PUSCH Type 2 CG PUSCH Type2;
  • Physical random access channel PRACH transmission Physical random access channel PRACH transmission.
  • the dynamically scheduled uplink transmission includes at least one of the following:
  • the first CG PUSCH after DCI activates CG PUSCH Type 2;
  • processor 710 is further used to:
  • the target time slot in which the terminal's target uplink transmission is located is an unavailable time slot for the target uplink transmission, or it is determined that the target time slot is not counted. into the number of transmissions of the target uplink transmission; or,
  • processor 710 is further used to:
  • the target time slot in which the terminal's target uplink transmission is located is an available time slot for the target uplink transmission, or it is determined that the target time slot is included in the target uplink transmission Among the number of transmissions of the target uplink transmission; or,
  • the target time slot in which the terminal's target uplink transmission is located is the available time for the target uplink transmission. slot, or determine that the target time slot is included in the number of transmissions of the target uplink transmission; or,
  • the AvailableSlotCounting is started or enabled and the number of transmissions K>1, when the interval between the first symbol of the target uplink transmission and the last symbol of the downlink reception is less than the first threshold, and/or the When the interval between the last symbol of the target uplink transmission and the first symbol of the downlink reception is less than the second threshold, determine that the target time slot in which the terminal's target uplink transmission is located is an available time slot for the target uplink transmission, or determine that the The target time slot is included in the number of transmissions of the target uplink transmission.
  • the downlink reception includes at least one of the following:
  • Synchronization signal/physical broadcast channel block SSB Synchronization signal/physical broadcast channel block
  • Downlink search space SS associated with control resource set #0 CORESET#0.
  • the SSB includes at least one of the following:
  • SSB configured by non-cell-defined SSB nonCellDefiningSSB related signaling
  • SSB configured by dedicated downlink partial bandwidth BWP-DownlinkDedicated signaling
  • SSB configured by UE-specific signaling
  • the SSB contained in the terminal's currently active BWP The SSB contained in the terminal's currently active BWP.
  • the first capability information includes at least one of the following:
  • the terminal includes: a low-capability terminal RedCap UE.
  • An embodiment of the present application also provides a network side device, including a processor and a communication interface; wherein:
  • the communication interface is used to receive the first capability information reported by the terminal; the first capability information is used to indicate that the terminal does not expect the network side device to enable or configure available time slot counts for the terminal; the processing The device is used to disable or configure available time slot counting for the terminal;
  • the processor is configured to perform at least one of the following when the target condition is met:
  • the terminal has half-duplex capability or does not have full-duplex capability.
  • This network-side device embodiment corresponds to the above-mentioned network-side device method embodiment.
  • Each implementation process and implementation manner of the above-mentioned method embodiment can be applied to this network-side device embodiment, and can achieve the same technical effect.
  • FIG 8 is a schematic structural diagram of a network side device provided by an embodiment of the present application.
  • the The network side device 800 includes: an antenna 801, a radio frequency device 802, a baseband device 803, a processor 804 and a memory 805.
  • Antenna 801 is connected to radio frequency device 802.
  • the radio frequency device 802 receives information through the antenna 801 and sends the received information to the baseband device 803 for processing.
  • the baseband device 803 processes the information to be sent and sends it to the radio frequency device 802.
  • the radio frequency device 802 processes the received information and then sends it out through the antenna 801.
  • the method performed by the network side device in the above embodiment can be implemented in the baseband device 803, which includes a baseband processor.
  • the baseband device 803 may include, for example, at least one baseband board on which multiple chips are disposed, as shown in FIG. Program to perform the network device operations shown in the above method embodiments.
  • the network side device may also include a network interface 806, which is, for example, a common public radio interface (CPRI).
  • a network interface 806, which is, for example, a common public radio interface (CPRI).
  • CPRI common public radio interface
  • the network side device 800 in this embodiment of the present invention also includes: instructions or programs stored in the memory 805 and executable on the processor 804.
  • the processor 804 calls the instructions or programs in the memory 805 to perform the transmission as described above. method and achieve the same technical effect. To avoid repetition, we will not repeat it here.
  • Embodiments of the present application also provide a transmission system, including: a terminal and a network-side device.
  • the terminal can be used to perform the steps of the terminal-side transmission method as described above.
  • the network-side device can be used to perform the above-described steps. The steps of the transmission method on the network side and device side.
  • Embodiments of the present application also provide a readable storage medium.
  • the readable storage medium may be volatile or non-volatile.
  • the readable storage medium stores a program or instructions. The program Or when the instruction is executed by the processor, each process of the above-mentioned transmission method embodiment is implemented, and the same technical effect can be achieved. To avoid repetition, the details will not be described here.
  • the processor is the processor in the terminal described in the above embodiment.
  • the readable storage medium includes computer readable storage media, such as computer read-only memory ROM, random access memory RAM, magnetic disk or optical disk, etc.
  • An embodiment of the present application further provides a chip.
  • the chip includes a processor and a communication interface.
  • the communication interface is coupled to the processor.
  • the processor is used to run programs or instructions to implement each of the above transmission method embodiments. The process can achieve the same technical effect. To avoid repetition, it will not be described again here.
  • chips mentioned in the embodiments of this application may also be called system-on-chip, system-on-a-chip, system-on-chip or system-on-chip, etc.
  • Embodiments of the present application further provide a computer program/program product.
  • the computer program/program product is stored in a storage medium.
  • the computer program/program product is executed by at least one processor to implement the above transmission method embodiment.
  • Each process can achieve the same technical effect. To avoid duplication, it will not be described again here.
  • the methods of the above embodiments can be implemented by means of software plus the necessary general hardware platform. Of course, it can also be implemented by hardware, but in many cases the former is better. implementation.
  • the technical solution of the present application can be embodied in the form of a computer software product that is essentially or contributes to the existing technology.
  • the computer software product is stored in a storage medium (such as ROM/RAM, disk , CD), including several instructions to make a terminal (can be a mobile phone, computer, server server, air conditioner, or network device, etc.) to perform the methods described in various embodiments of this application.

Landscapes

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

Abstract

本申请公开了一种传输方法、装置、终端及存储介质,属于通信技术领域,本申请实施例的传输方法包括:终端向网络侧设备上报第一能力信息;所述第一能力信息用于指示终端不期望网络侧设备为所述终端使能或配置可用时隙计数;或者,终端在目标条件满足的情况下,执行以下至少一项:确定所述终端的目标上行传输所在的目标时隙为所述目标上行传输的不可用时隙,或者确定所述目标时隙不计入所述目标上行传输的传输次数中;不期望目标上行传输和下行接收之间存在资源重叠,或者不期望目标上行传输和下行接收之间的切换时间小于目标时间;放弃所述目标上行传输;进行下行接收;其中,所述终端具有半双工能力或不具有全双工能力。

Description

传输方法、装置、终端及存储介质
相关申请的交叉引用
本申请要求于2022年03月25日提交的申请号为202210307763.5,发明名称为“传输方法、装置、终端及存储介质”的中国专利申请的优先权,其通过引用方式全部并入本申请。
技术领域
本申请属于通信技术领域,具体涉及一种传输方法、装置、终端及存储介质。
背景技术
在涉及工业无线传感器、视频监控及可穿戴设备等场景中,基于垂直行业的需求,终端需要在接收天线、发射天线数目、支持的带宽、终端处理数据和信号的时间及能力等方面降低复杂度,该类终端称为低能力终端(Redcued Capability User Equipment,RedCap UE)。
相关技术中,当终端不具有全双工能力时,在同一时间该终端不能同时进行上行传输和下行接收,且该终端的上行传输到下行接收或下行接收到上行传输之间需要一定的切换时间。当上行传输和下行接收的资源有冲突时,或当该终端的上行传输和下行接收之间的切换时间小于终端的切换能力或协议规定的时间时,终端放弃上行传输,导致上行覆盖差。
发明内容
本申请实施例提供一种传输方法、装置、终端及存储介质,能够解决上行覆盖差的问题。
第一方面,提供了一种传输方法,该方法包括:
终端向网络侧设备上报第一能力信息;所述第一能力信息用于指示所述终端不期望所述网络侧设备为所述终端使能或配置可用时隙计数;
或者,终端在目标条件满足的情况下,执行以下至少一项:
确定所述终端的目标上行传输所在的目标时隙为所述目标上行传输的不可用时隙,或者确定所述目标时隙不计入所述目标上行传输的传输次数中;
不期望目标上行传输和下行接收之间存在资源重叠,或者不期望目标上行传输和下行接收之间的切换时间小于目标时间;
放弃所述目标上行传输;
进行下行接收;
其中,所述终端具有半双工能力或不具有全双工能力。
第二方面,提供了一种传输方法,该方法包括:
网络侧设备接收终端上报的第一能力信息;所述第一能力信息用于指示所述终端不期望所述网络侧设备为所述终端使能或配置可用时隙计数;所述网络侧设备为所述终端不使能或不配置可用时隙计数;
或者,网络侧设备在目标条件满足的情况下,执行以下至少一项:
确定终端的目标上行传输所在的目标时隙为所述目标上行传输的不可用时隙,或者确定所述目标时隙不计入所述目标上行传输的传输次数中;
配置目标上行传输和下行接收之间不存在资源重叠,或者配置目标上行传输和下行接收之间的切换时间不小于目标时间;
放弃目标上行接收;
接收目标上行传输;
进行下行发送;
其中,所述终端具有半双工能力或不具有全双工能力。
第三方面,提供了一种传输装置,该装置包括:
第一传输模块,用于向网络侧设备上报第一能力信息;所述第一能力信息用于指示终端不期望所述网络侧设备为所述终端使能或配置可用时隙计数;
或者,在目标条件满足的情况下,执行以下至少一项:
确定所述终端的目标上行传输所在的目标时隙为所述目标上行传输的不可用时隙,或者确定所述目标时隙不计入所述目标上行传输的传输次数中;
不期望目标上行传输和下行接收之间存在资源重叠,或者不期望目标上行传输和下行接收之间的切换时间小于目标时间;
放弃所述目标上行传输;
进行下行接收;
其中,所述终端具有半双工能力或不具有全双工能力。
第四方面,提供了一种传输装置,该装置包括:
第二传输模块,用于接收终端上报的第一能力信息;所述第一能力信息用于指示所述终端不期望所述网络侧设备为所述终端使能或配置可用时隙计数;处理模块,用于为所述终端不使能或不配置可用时隙计数;
或者,第二传输模块,用于在目标条件满足的情况下,执行以下至少一项:
确定终端的目标上行传输所在的目标时隙为所述目标上行传输的不可用时隙,或者确定所述目标时隙不计入所述目标上行传输的传输次数中;
配置目标上行传输和下行接收之间不存在资源重叠,或者配置目标上行传输和下行接收之间的切换时间不小于目标时间;
放弃目标上行接收;
接收目标上行传输;
进行下行发送;
其中,所述终端具有半双工能力或不具有全双工能力。
第五方面,提供了一种终端,该终端包括处理器和存储器,所述存储器存储可在所述处理器上运行的程序或指令,所述程序或指令被所述处理器执行时实现如第一方面所述的方法的步骤。
第六方面,提供了一种终端,包括处理器及通信接口;其中:
所述通信接口用于向网络侧设备上报第一能力信息;所述第一能力信息用于指示终端不期望所述网络侧设备为所述终端使能或配置可用时隙计数;
或者,所述处理器用于在目标条件满足的情况下,执行以下至少一项:
确定所述终端的目标上行传输所在的目标时隙为所述目标上行传输的不可用时隙,或者确定所述目标时隙不计入所述目标上行传输的传输次数中;
不期望目标上行传输和下行接收之间存在资源重叠,或者不期望目标上行传输和下行接收之间的切换时间小于目标时间;
放弃所述目标上行传输;
进行下行接收;
其中,所述终端具有半双工能力或不具有全双工能力。
第七方面,提供了一种网络侧设备,该终端包括处理器和存储器,所述存储器存储可在所述处理器上运行的程序或指令,所述程序或指令被所述处理器执行时实现如第二方面所述的方法的步骤。
第八方面,提供了一种网络侧设备,包括处理器及通信接口;其中:
所述通信接口用于接收终端上报的第一能力信息;所述第一能力信息用于指示所述终端不期望所述网络侧设备为所述终端使能或配置可用时隙计数;所述处理器用于为所述终端不使能或不配置可用时隙计数;
或者,所述处理器用于在目标条件满足的情况下,执行以下至少一项:
确定终端的目标上行传输所在的目标时隙为所述目标上行传输的不可用时隙,或者确定所述目标时隙不计入所述目标上行传输的传输次数中;
配置目标上行传输和下行接收之间不存在资源重叠,或者配置目标上行传输和下行接收之间的切换时间不小于目标时间;
放弃目标上行接收;
接收目标上行传输;
进行下行发送;
其中,所述终端具有半双工能力或不具有全双工能力。
第九方面,提供了一种传输***,包括:终端及网络侧设备,所述终端可用于执行如第一方面所述的方法的步骤,所述网络侧设备可用于执行如第二方面所述的方法的步骤。
第十方面,提供了一种可读存储介质,所述可读存储介质上存储程序或指令,所述程序或指令被处理器执行时实现如第一方面所述的方法的步骤,或者实现如第二方面所述的方法的步骤。
第十一方面,提供了一种芯片,所述芯片包括处理器和通信接口,所述通信接口和所述处理器耦合,所述处理器用于运行程序或指令,实现如第一方面所述的方法,或者实现如第二方面所述的方法的步骤。
第十二方面,提供了一种计算机程序/程序产品,所述计算机程序/程序产品被存储在存储介质中,计算机程序/程序产品被至少一个处理器执行以实现如第一方面所述的方法的步骤,或者实现如第二方面所述的方法的步骤。
在本申请实施例中,通过终端在向网络侧设备上报第一能力信息的情况下,终端不期望网络侧设备为终端使能或配置可用时隙计数;或者具有半双工能力或不具有全双工能力的终端在目标条件满足的情况下,执行以下至少一项:确定终端的目标上行传输所在的目标时隙为目标上行传输的不可用时隙,或者确定目标时隙不计入目标上行传输的传输次数中;不期望目标上行传输和下行接收之间存在资源重叠,或者不期望目标上行传输和下行接收之间的切换时间小于目标时间;放弃目标上行传输;进行下行接收。本申请实施例提供的传输方法能够实现当目标上行传输和下行接收之间存在资源重叠或目标上行传输和下行接收之间的切换时间不够时的统一处理,简化终端的行为和复杂度,通过确定终端的目标上行传输所在的目标时隙为目标上行传输的不可用时隙,或者确定目标时隙不计入目标上行传输的传输次数中的方式,进而将目标上行传输在下一个可用时隙进行传输,如此能够提高上行覆盖。
附图说明
图1是本申请实施例可应用的无线通信***的示意图;
图2是本申请实施例提供的传输方法的流程示意图之一;
图3是本申请实施例提供的传输方法的流程示意图之二;
图4是本申请实施例提供的传输装置的结构示意图之一;
图5是本申请实施例提供的传输装置的结构示意图之二;
图6是本申请实施例提供的通信设备的结构示意图;
图7是本申请实施例提供的终端的结构示意图;
图8是本申请实施例提供的网络侧设备的结构示意图。
具体实施方式
下面将结合本申请实施例中的附图,对本申请实施例中的技术方案进行清楚描述,显然,所描述的实施例是本申请一部分实施例,而不是全部的实施例。基于本申请中的实施例,本领域普通技术人员所获得的所有其他实施例,都属于本申请保护的范围。
本申请的说明书和权利要求书中的术语“第一”、“第二”等是用于区别类似的对象,而不用于描述特定的顺序或先后次序。应该理解这样使用的术语在适当情况下可以互换,以便本申请的实施例能够以除了在这里图示或描述的那些以外的顺序实施,且“第一”、“第二”所区别的对象通常为一类,并不限定对象的个数,例如第一对象可以是一个,也可以是多个。此外,说明书以及权利要求中“和/或”表示所连接对象的至少其中之一,字符“/”一般表示前后关联对象是一种“或”的关系。
值得指出的是,本申请实施例所描述的技术不限于长期演进型(Long Term Evolution,LTE)/LTE的演进(LTE-Advanced,LTE-A)***,还可用于其他无线通信***,诸如码分多址(Code Division Multiple Access,CDMA)、时分多址(Time Division Multiple Access,TDMA)、频分多址(Frequency Division Multiple Access,FDMA)、正交频分多址(Orthogonal Frequency Division Multiple Access,OFDMA)、单载波频分多址(Single-carrier Frequency Division Multiple Access,SC-FDMA)和其他***。本申请实施例中的术语“***”和“网络”常被可互换地使用,所描述的技术既可用于以上提及的***和无线电技术,也可用于其他***和无线电技术。以下描述出于示例目的描 述了新空口(New Radio,NR)***,并且在以下大部分描述中使用NR术语,但是这些技术也可应用于NR***应用以外的通信***,如第6代(6th Generation,6G)通信***。
图1是本申请实施例可应用的无线通信***的示意图,图1示出的无线通信***包括终端11和网络侧设备12。其中,终端11可以是手机、平板电脑(Tablet Personal Computer)、膝上型电脑(Laptop Computer)或称为笔记本电脑、个人数字助理(Personal Digital Assistant,PDA)、掌上电脑、上网本、超级移动个人计算机(ultra-mobile personal computer,UMPC)、移动上网装置(Mobile Internet Device,MID)、增强现实(augmented reality,AR)/虚拟现实(virtual reality,VR)设备、机器人、可穿戴式设备(Wearable Device)、车载设备(VUE)、行人终端(PUE)、智能家居(具有无线通信功能的家居设备,如冰箱、电视、洗衣机或者家具等)、游戏机、个人计算机(personal computer,PC)、柜员机或者自助机等终端侧设备,可穿戴式设备包括:智能手表、智能手环、智能耳机、智能眼镜、智能首饰(智能手镯、智能手链、智能戒指、智能项链、智能脚镯、智能脚链等)、智能腕带、智能服装等。需要说明的是,在本申请实施例并不限定终端11的具体类型。
网络侧设备12可以包括接入网设备或核心网设备,其中,接入网设备也可以称为无线接入网设备、无线接入网(Radio Access Network,RAN)、无线接入网功能或无线接入网单元。接入网设备可以包括基站、WLAN接入点或WiFi节点等,基站可被称为节点B、演进节点B(eNB)、接入点、基收发机站(Base Transceiver Station,BTS)、无线电基站、无线电收发机、基本服务集(Basic Service Set,BSS)、扩展服务集(Extended Service Set,ESS)、家用B节点、家用演进型B节点、发送接收点(Transmitting Receiving Point,TRP)或所述领域中其他某个合适的术语,只要达到相同的技术效果,所述基站不限于特定技术词汇,需要说明的是,在本申请实施例中仅以NR***中的基站为例进行介绍,并不限定基站的具体类型。核心网设备可以包含但不限于如下至少一项:核心网节点、核心网功能、移动管理实体(Mobility  Management Entity,MME)、接入移动管理功能(Access and Mobility Management Function,AMF)、会话管理功能(Session Management Function,SMF)、用户平面功能(User Plane Function,UPF)、策略控制功能(Policy Control Function,PCF)、策略与计费规则功能单元(Policy and Charging Rules Function,PCRF)、边缘应用服务发现功能(Edge Application Server Discovery Function,EASDF)、统一数据管理(Unified Data Management,UDM),统一数据仓储(Unified Data Repository,UDR)、归属用户服务器(Home Subscriber Server,HSS)、集中式网络配置(Centralized network configuration,CNC)、网络存储功能(Network Repository Function,NRF),网络开放功能(Network Exposure Function,NEF)、本地NEF(LocalNEF,或L-NEF)、绑定支持功能(Binding Support Function,BSF)、应用功能(Application Function,AF)、位置管理功能(location manage function,LMF)、增强服务移动定位中心(Enhanced Serving Mobile Location Centre,E-SMLC)、网络数据分析功能(network data analytics function,NWDAF)等。需要说明的是,在本申请实施例中仅以NR***中的核心网设备为例进行介绍,并不限定核心网设备的具体类型。
下面结合附图,通过一些实施例及其应用场景对本申请实施例提供的传输方法进行详细地说明。
图2是本申请实施例提供的传输方法的流程示意图之一,如图2所示,该方法包括:
步骤201、终端向网络侧设备上报第一能力信息;所述第一能力信息用于指示所述终端不期望所述网络侧设备为所述终端使能或配置可用时隙计数;
或者,终端在目标条件满足的情况下,执行以下至少一项:
确定所述终端的目标上行传输所在的目标时隙为所述目标上行传输的不可用时隙,或者确定所述目标时隙不计入所述目标上行传输的传输次数中;
不期望目标上行传输和下行接收之间存在资源重叠,或者不期望目标上行传输和下行接收之间的切换时间小于目标时间;
放弃所述目标上行传输;
进行下行接收;
其中,所述终端具有半双工能力或不具有全双工能力。
例如,所述终端在目标条件满足的情况下,确定所述目标时隙不计入所述目标上行传输的K个时隙中,K>1或K=1,K为正整数。
需要说明的是,本申请实施例可应用于具有半双工能力或不具有全双工能力的终端的上行传输场景中。所述终端包括低能力终端(RedCap UE),例如RedCap半双工(Half Duplex-frequency-division duplex,HD-FDD)UE。网络侧设备包括但不限于上述所列举的网络侧设备12的类型,本申请对此并不限定。
实际中,第一能力信息用于指示终端不期望所述网络侧设备为所述终端使能或配置可用时隙计数。所述第一能力信息可以包括以下至少一项:1)具有半双工能力;2)不具有全双工能力。终端在向网络侧设备上报第一能力信息的情况下,终端不期望网络侧设备为所述终端使能可用时隙计数(AvailableSlotCounting)。网络侧设备接收终端上报的第一能力信息,所述网络侧设备为所述终端不使能或不配置可用时隙计数。
具有半双工能力的终端或不具有全双工能力的终端(例如RedCap HD-FDD UE)不支持上行重复传输(例如PUSCH repetition Type A或PUCCH)的次数基于可用时隙计数的机制。举个例子来说,当终端向网络侧设备上报该终端是半双工终端,假设该终端上报的是:RedCap UE with Half-duplex FDD操作类型A(operation type A),则该终端不期待网络侧设备为其配置或者使能可用时隙计数。
可选地,本申请实施例中的目标条件可以包括以下至少一项:
1)使能或配置可用时隙计数,或者不使能或不配置可用时隙计数;
具体地,网络侧设备为所述终端的上行传输使能或配置可用时隙计数。或者,网络侧设备为所述终端的上行传输不使能或不配置可用时隙计数。
2)目标上行传输和下行接收之间存在资源重叠;
3)目标上行传输和下行接收之间不存在资源重叠,且目标上行传输和下行接收之间的切换时间小于目标时间;
需要说明的是,目标上行传输和下行接收之间的切换时间,可以包括以下至少一项:a)目标上行传输的最后一个符号到所述下行接收的第一个符号之间的时间间隔;b)下行接收的最后一个符号和所述目标上行传输的第一个符号之间的时间间隔。
实际中,对于目标上行传输和下行接收之间不存在资源重叠,且目标上行传输和下行接收之间的切换时间小于目标时间的情况,也可简称为:上下行切换时间重叠。
以下行传输为同步信号/物理广播信道块(Synchronization Signal/PBCH block,SSB)为例,SSB和上行传输(如PUSCH)的资源没有重叠、但上行传输到下行接收之间的切换时间小于第一时间,或下行接收到上行传输之间的切换时间小于第二时间。目标时间的取值可以包括第一时间或第二时间。
4)传输次数大于1,或者传输次数等于1;
其中,所述上行传输的传输次数也可以称为重复次数K,可以记为K,K>1或K=1,K为正整数。
5)目标上行传输为无线资源控制(Radio Resource Control,RRC)半静态配置的上行传输;或者所述目标上行传输为动态调度的上行传输。
具体地,所述RRC半静态配置的上行传输可以包括以下至少一项:
a)RRC半静态配置的物理上行链路控制信道(Physical Uplink Control Channel,PUCCH)传输;
b)RRC半静态配置的授权调度(configured grant)的PUSCH类型1(CG PUSCH Type1);
c)RRC半静态配置的授权调度的PUSCH类型2(CG PUSCH Type2);
d)除了下行控制信息(Downlink Control Information,DCI)激活CG PUSCH Type2后的第一个CG PUSCH,其余的CG PUSCH Type 2。
e)物理随机接入信道(Physical Random Access Channel,PRACH)传输。
具体地,所述动态调度的上行传输可以包括以下至少一项:
A)由上行授权(UL grant)调度的PUSCH;实际中,上行授权包括:DCI format 0_0、DCI format 0_1或DCI format 0_2等。
B)DCI激活CG PUSCH Type 2后的第一个CG PUSCH;
C)由随机接入响应(Random Access Response,RAR)UL grant调度的PUSCH;
D)由使用临时小区无线网络临时标识符(Temporary Cell Radio Network Temporary Identifier,TC-RNTI)加扰的DCI format 0_0调度的PUSCH;
E)动态调度的PUCCH。
F)动态调度的PRACH;例如,动态调度的PRACH为由PDCCH order调度的PRACH的传输。
G)动态调度的探测参考信号(Sounding Reference Signal,SRS)。
可选地,所述下行接收可以包括以下至少一项:
1)SSB;
2)公共搜索空间类型0(Type0 Common Search Space,Type0 CSS)、Type0A CSS、Type1 CSS及Type2 CSS中至少一项;
3)与控制资源集合#0(CORESET#0)相关联的下行搜索空间(Search Space,SS)。
具体地,所述SSB可以包括以下至少一项:
a)由同步广播块在集合中的位置(ssb-PositionsInBurst)配置的SSB;
b)由非小区定义SSB(nonCellDefiningSSB)相关信令配置的SSB;
c)由专用下行部分带宽(BWP-DownlinkDedicated)信令配置的SSB;
d)由终端特定信令(UE-specific signalling)配置的SSB;
e)终端当前活动的BWP(active BWP)中所包含的SSB。
实际中,在终端确定所述终端的目标上行传输所在的目标时隙为所述目标上行传输的不可用时隙,或者确定所述目标时隙不计入所述目标上行传输的传输次数中的情况下,所述终端将所述目标上行传输在下一个可用时隙进 行上行传输。
本申请实施例提供的传输方法中,通过终端在向网络侧设备上报第一能力信息的情况下,终端不期望网络侧设备为终端使能或配置可用时隙计数;或者具有半双工能力或不具有全双工能力的终端在目标条件满足的情况下,执行以下至少一项:确定终端的目标上行传输所在的目标时隙为目标上行传输的不可用时隙,或者确定目标时隙不计入目标上行传输的传输次数中;不期望目标上行传输和下行接收之间存在资源重叠,或者不期望目标上行传输和下行接收之间的切换时间小于目标时间;放弃目标上行传输;进行下行接收。本申请实施例提供的传输方法能够实现当目标上行传输和下行接收之间存在资源重叠或目标上行传输和下行接收之间的切换时间不够时的统一处理,简化终端的行为和复杂度,通过确定终端的目标上行传输所在的目标时隙为目标上行传输的不可用时隙,或者确定目标时隙不计入目标上行传输的传输次数中的方式,进而将目标上行传输在下一个可用时隙进行传输,如此能够提高上行覆盖。
本申请实施例中,终端基于不同的目标条件所执行的终端行为,可以对应于以下至少一种情形:
情形一、针对上行传输为配置授权的PUSCH重复传输(CG PUSCH)、或半静态配置传输的PUCCH(configured PUCCH)、或不是由PDCCH order触发的其他PRACH的重复传输的情形,终端行为可以包括以下至少一种方式:
方式1-1、对于半双工终端的配置授权的PUSCH重复传输、或半静态配置传输的PUCCH、或者PRACH的重复传输,无论是否启用/使能AvailableSlotCounting,对于重复次数K=1和K>1,当PUSCH或PUCCH或PRACH重复传输的第一个符号和同步广播信号块(SSB)传输符号的最后一个符号之间的间隔小于/少于第一阈值(第一阈值例如为NRX-TX*Tc),和/或当PUSCH或PUCCH或PRACH重复传输的最后一个符号和同步广播信号块(SSB)传输符号的第一个符号之间的间隔小于/少于第二阈值(第二阈值 例如为NTX-RX*Tc)时,HD-FDD UE确定该PUSCH或PUCCH或PRACH所在的时隙为不可用时隙或者该时隙不计入PUSCH传输的K个时隙中,HD-FDD UE将PUSCH或PUCCH或PRACH重复传输推迟到下一个可用时隙。
可选地,Tc表示基本时间单元(Basic time unit);NRX-TX表示下行接收到上行传输之间的切换时间;NTX-RX表示上行传输到下行接收之间的切换时间。
方式1-2、对于半双工终端的配置授权的PUSCH重复传输、或半静态配置传输的PUCCH、或者PRACH的重复传输,无论是否启用/使能AvailableSlotCounting,对于重复次数K=1和K>1,当PUSCH或PUCCH或PRACH重复传输的第一个符号和同步广播信号块(SSB)传输符号的最后一个符号之间的间隔小于/少于NRX-TX*Tc,和/或当PUSCH或PUCCH或PRACH重复传输的最后一个符号和同步广播信号块(SSB)传输符号的第一个符号之间的间隔小于/少于NTX-RX*Tc时,HD-FDD UE不传输或者放弃传输该PUSCH或PUCCH或PRACH。
情形二、针对上行传输为DG(如PUSCH repetition scheduled by DCI format 0_1 or 0_2)、或dynamic PUCCH(如dynamic PUCCH scheduled by PDCCH)、或由PDCCH order触发的PRACH的情形,终端行为可以包括以下至少一种方式:
方式2-1、对于半双工终端,由上行DCI format调度的PUSCH重复传输、或由DCI调度的PUCCH传输、或由PDCCH order触发的PRACH,无论是否启用/使能AvailableSlotCounting,对于重复次数K=1和K>1,当PUSCH或PUCCH或PRACH重复传输的第一个符号和同步广播信号块(SSB)传输符号的最后一个符号之间的间隔小于/少于NRX-TX*Tc,和/或当PUSCH或PUCCH或PRACH重复传输的最后一个符号和同步广播信号块(SSB)传输符号的第一个符号之间的间隔小于/少于NTX-RX*Tc时,HD-FDD UE确定该PUSCH或PUCCH或PRACH所在的时隙为不可用时隙,或者该时隙不计入 PUSCH或PUCCH或PRACH传输的K个时隙中,HD-FDD UE将PUSCH或PUCCH或PRACH重复传输推迟到下一个可用时隙。
方式2-2、对于半双工终端,由上行DCI format调度的PUSCH重复传输、或由DCI调度的PUCCH传输、或由PDCCH order触发的PRACH,无论是否启用/使能AvailableSlotCounting,对于重复次数K=1和K>1,当PUSCH或PUCCH或PRACH重复传输的第一个符号和同步广播信号块(SSB)传输符号的最后一个符号之间的间隔小于/少于NRX-TX*Tc,和/或当PUSCH或PUCCH或PRACH重复传输的最后一个符号和同步广播信号块(SSB)传输符号的第一个符号之间的间隔小于/少于NTX-RX*Tc时,HD-FDD UE不传输该PUSCH或PUCCH或PRACH,即HD-FDD UE确定该PUSCH或PUCCH或PRACH所在的时隙为可用时隙,或者该时隙计入PUSCH或PUCCH或PRACH传输的K个时隙中。
方式2-3、对于半双工终端,由上行DCI format调度的PUSCH重复传输、或由DCI调度的PUCCH传输、或由PDCCH order触发的PRACH,无论是否启用/使能AvailableSlotCounting,对于重复次数K=1和K>1,HD-FDD UE不期望一个PUSCH或PUCCH或PRACH重复传输的第一个符号到同步广播信号块(SSB)传输符号的最后一个符号之间的间隔小于/少于NRX-TX*Tc,和/或HD-FDD UE不期望一个PUSCH或PUCCH或PRACH重复传输的最后一个符号和同步广播信号块(SSB)传输符号的第一个符号之间的间隔小于/少于NTX-RX*Tc。
情形三、针对上行传输为CG PUSCH、或configuredPUCCH、或不是由PDCCH order触发的其他PRACH的重复传输的情形,终端行为可以包括以下至少一种方式:
方式3-1、对于半双工终端的配置授权的PUSCH重复传输或半静态配置传输的PUCCH或不是由PDCCH order触发的其他PRACH的重复传输:
1)当启用/使能AvailableSlotCounting时,对于重复次数K=1和K>1,当PUSCH或PUCCH或PRACH重复传输的第一个符号和同步广播信号块 (SSB)传输符号的最后一个符号之间的间隔小于/少于NRX-TX*Tc,和/或当PUSCH或PUCCH或PRACH重复传输的最后一个符号和同步广播信号块(SSB)传输符号的第一个符号之间的间隔小于/少于NTX-RX*Tc时,HD-FDD UE确定该PUSCH或PUCCH或PRACH所在的时隙为不可用时隙或者该时隙不计入PUSCH传输的K个时隙中,HD-FDD UE将PUSCH或PUCCH或PRACH重复传输推迟到下一个可用时隙。
2)当没有启用/使能AvailableSlotCounting时,对于重复次数K=1和K>1,当PUSCH或PUCCH或PRACH重复传输的第一个符号和同步广播信号块(SSB)传输符号的最后一个符号之间的间隔小于/少于NRX-TX*Tc,和/或当PUSCH或PUCCH或PRACH重复传输的最后一个符号和同步广播信号块(SSB)传输符号的第一个符号之间的间隔小于/少于NTX-RX*Tc时,HD-FDD UE不传输或者放弃传输该PUSCH或PUCCH或PRACH。
情形四、针对上行传输为DG、或dynamic PUCCH、或由PDCCH order触发的PRACH的情形,终端行为可以包括以下至少一种方式:
方式4-1、对于半双工终端,由上行DCI format调度的PUSCH重复传输、或由DCI调度的PUCCH传输、或由PDCCH order触发的PRACH:
1)当启用/使能AvailableSlotCounting时,对于重复次数K=1和K>1,当PUSCH或PUCCH或PRACH重复传输的第一个符号和同步广播信号块(SSB)传输符号的最后一个符号之间的间隔小于/少于NRX-TX*Tc,和/或当PUSCH或PUCCH或PRACH重复传输的最后一个符号和同步广播信号块(SSB)传输符号的第一个符号之间的间隔小于/少于NTX-RX*Tc时,HD-FDD UE确定该PUSCH所在的时隙为不可用时隙或者该时隙不计入PUSCH或PUCCH或PRACH传输的K个时隙中,HD-FDD UE将PUSCH或PUCCH或PRACH重复传输推迟到下一个可用时隙。
2)当没有启用/使能AvailableSlotCounting时,对于重复次数K=1和K>1,HD-FDD UE不期望一个PUSCH或PUCCH或PRACH重复传输的第一个符号到同步广播信号块(SSB)传输符号的最后一个符号之间的间隔小于/少于 NRX-TX*Tc,和/或HD-FDD UE不期望一个PUSCH或PUCCH或PRACH重复传输的最后一个符号和同步广播信号块(SSB)传输符号的第一个符号之间的间隔小于/少于NTX-RX*Tc。
方式4-2、对于半双工终端,由上行DCI format调度的PUSCH重复传输、或由DCI调度的PUCCH传输、或由PDCCH order触发的PRACH:
1)当启用/使能AvailableSlotCounting时,对于重复次数K=1和K>1,当PUSCH或PUCCH或PRACH重复传输的第一个符号和同步广播信号块(SSB)传输符号的最后一个符号之间的间隔小于/少于NRX-TX*Tc,和/或当PUSCH或PUCCH或PRACH重复传输的最后一个符号和同步广播信号块(SSB)传输符号的第一个符号之间的间隔小于/少于NTX-RX*Tc时,HD-FDD UE不传输该PUSCH或PUCCH或PRACH,即HD-FDD UE确定该PUSCH或PUCCH或PRACH所在的时隙为可用时隙或者该时隙计入PUSCH传输的K个时隙中。
2)当没有启用/使能AvailableSlotCounting时,对于重复次数K=1和K>1,HD-FDD UE不期望一个PUSCH或PUCCH或PRACH重复传输的第一个符号到同步广播信号块(SSB)传输符号的最后一个符号之间的间隔小于/少于NRX-TX*Tc,和/或HD-FDD UE不期望一个PUSCH或PUCCH或PRACH重复传输的最后一个符号和同步广播信号块(SSB)传输符号的第一个符号之间的间隔小于/少于NTX-RX*Tc。
方式4-3、对于半双工终端,由上行DCI format调度的PUSCH重复传输、或由DCI调度的PUCCH传输、或由PDCCH order触发的PRACH:
1)当启用/使能AvailableSlotCounting时,对于重复次数K=1和K>1,当PUSCH或PUCCH或PRACH重复传输的第一个符号和同步广播信号块(SSB)传输符号的最后一个符号之间的间隔小于/少于NRX-TX*Tc,和/或当PUSCH或PUCCH或PRACH重复传输的最后一个符号和同步广播信号块(SSB)传输符号的第一个符号之间的间隔小于/少于NTX-RX*Tc时,HD-FDD UE确定该PUSCH或PUCCH或PRACH所在的时隙为不可用时隙 或者该时隙不计入PUSCH传输的K个时隙中,HD-FDD UE将PUSCH或PUCCH或PRACH重复传输推迟到下一个可用时隙。
2)当没有启用/使能AvailableSlotCounting时,对于重复次数K=1和K>1,HD-FDD UE不期望一个PUSCH或PUCCH或PRACH重复传输的第一个符号到同步广播信号块(SSB)传输符号的最后一个符号之间的间隔小于/少于NRX-TX*Tc,和/或HD-FDD UE不期望一个PUSCH或PUCCH或PRACH重复传输的最后一个符号和同步广播信号块(SSB)传输符号的第一个符号之间的间隔小于/少于NTX-RX*Tc。
情形五、针对上行传输为CG PUSCH、或configuredPUCCH、或不是由PDCCH order触发的其他PRACH的重复传输的情形,终端行为可以包括以下至少一种方式:
方式5-1、对于半双工终端的配置授权的PUSCH重复传输、或半静态配置传输的PUCCH、或不是由PDCCH order触发的其他PRACH的重复传输:
1)当启用/使能AvailableSlotCounting时:
(a)对于重复次数K>1,当PUSCH重复传输的第一个符号和同步广播信号块(SSB)传输符号的最后一个符号之间的间隔小于/少于NRX-TX*Tc,和/或当PUSCH或PUCCH或PRACH重复传输的最后一个符号和同步广播信号块(SSB)传输符号的第一个符号之间的间隔小于/少于NTX-RX*Tc时,HD-FDD UE确定该PUSCH或PUCCH或PRACH所在的时隙为不可用时隙,或者该时隙不计入PUSCH或PUCCH或PRACH传输的K个时隙中,HD-FDD UE将PUSCH或PUCCH或PRACH重复传输推迟到下一个可用时隙。
(b)对于重复次数K=1,当PUSCH重复传输的第一个符号和同步广播信号块(SSB)传输符号的最后一个符号之间的间隔小于/少于NRX-TX*Tc,和/或当PUSCH或PUCCH或PRACH重复传输的最后一个符号和同步广播信号块(SSB)传输符号的第一个符号之间的间隔小于/少于NTX-RX*Tc时,HD-FDD UE不传输该PUSCH或PUCCH或PRACH,即HD-FDD UE确定该PUSCH或PUCCH或PRACH所在的时隙为可用时隙,或者该时隙计入 PUSCH或PUCCH或PRACH传输的K个时隙中。
2)当没有启用/使能AvailableSlotCounting时,对于重复次数K=1和K>1,当PUSCH或PUCCH或PRACH重复传输的第一个符号和同步广播信号块(SSB)传输符号的最后一个符号之间的间隔小于/少于NRX-TX*Tc,和/或当PUSCH或PUCCH或PRACH重复传输的最后一个符号和同步广播信号块(SSB)传输符号的第一个符号之间的间隔小于/少于NTX-RX*Tc时,HD-FDD UE不传输该PUSCH或PUCCH或PRACH,即HD-FDD UE确定该PUSCH或PUCCH或PRACH所在的时隙为可用时隙,或者该时隙计入PUSCH或PUCCH或PRACH传输的K个时隙中。
情形六、针对上行传输为DG、或dynamic PUCCH、或由PDCCH order触发的PRACH的情形,终端行为可以包括以下至少一种方式:
方式6-1、对于半双工终端,由上行DCI format调度的PUSCH重复传输、或由DCI调度的PUCCH传输、或由PDCCH order触发的PRACH:
1)当启用/使能AvailableSlotCounting时:
(a)对于重复次数K>1,当PUSCH或PUCCH或PRACH重复传输的第一个符号和同步广播信号块(SSB)传输符号的最后一个符号之间的间隔小于/少于NRX-TX*Tc,和/或当PUSCH或PUCCH或PRACH重复传输的最后一个符号和同步广播信号块(SSB)传输符号的第一个符号之间的间隔小于/少于NTX-RX*Tc时,HD-FDD UE确定该PUSCH或PUCCH或PRACH所在的时隙为不可用时隙,或者该时隙不计入PUSCH或PUCCH或PRACH传输的K个时隙中,HD-FDD UE将PUSCH或PUCCH或PRACH重复传输推迟到下一个可用时隙。
(b)对于重复次数K=1,HD-FDD UE不期望一个PUSCH或PUCCH或PRACH重复传输的第一个符号到同步广播信号块(SSB)传输符号的最后一个符号之间的间隔小于/少于NRX-TX*Tc,和/或HD-FDD UE不期望一个PUSCH或PUCCH或PRACH重复传输的最后一个符号和同步广播信号块(SSB)传输符号的第一个符号之间的间隔小于/少于NTX-RX*Tc。
2)当没有启用/使能AvailableSlotCounting时,对于重复次数K=1和K>1,HD-FDD UE不期望一个PUSCH或PUCCH或PRACH重复传输的第一个符号到同步广播信号块(SSB)传输符号的最后一个符号之间的间隔小于/少于NRX-TX*Tc,和/或HD-FDD UE不期望一个PUSCH或PUCCH或PRACH重复传输的最后一个符号和同步广播信号块(SSB)传输符号的第一个符号之间的间隔小于/少于NTX-RX*Tc。
方式6-2、对于半双工终端,由上行DCI format调度的PUSCH重复传输、或由DCI调度的PUCCH传输、或由PDCCH order触发的PRACH:
1)当启用/使能AvailableSlotCounting时:
(a)对于重复次数K>1,当PUSCH或PUCCH或PRACH重复传输的第一个符号和同步广播信号块(SSB)传输符号的最后一个符号之间的间隔小于/少于NRX-TX*Tc,和/或当PUSCH或PUCCH或PRACH重复传输的最后一个符号和同步广播信号块(SSB)传输符号的第一个符号之间的间隔小于/少于NTX-RX*Tc时,HD-FDD UE不传输该PUSCH或PUCCH或PRACH,即HD-FDD UE确定该PUSCH或PUCCH或PRACH所在的时隙为可用时隙,或者该时隙计入PUSCH或PUCCH或PRACH传输的K个时隙中。
(b)对于重复次数K=1,HD-FDD UE不期望一个PUSCH或PUCCH或PRACH重复传输的第一个符号到同步广播信号块(SSB)传输符号的最后一个符号之间的间隔小于/少于NRX-TX*Tc,和/或HD-FDD UE不期望一个PUSCH或PUCCH或PRACH重复传输的最后一个符号和同步广播信号块(SSB)传输符号的第一个符号之间的间隔小于/少于NTX-RX*Tc。
2)当没有启用/使能AvailableSlotCounting时,对于重复次数K=1和K>1,HD-FDD UE不期望一个PUSCH或PUCCH或PRACH重复传输的第一个符号到同步广播信号块(SSB)传输符号的最后一个符号之间的间隔小于/少于NRX-TX*Tc,和/或HD-FDD UE不期望一个PUSCH或PUCCH或PRACH重复传输的最后一个符号和同步广播信号块(SSB)传输符号的第一个符号之间的间隔小于/少于NTX-RX*Tc。
方式6-3、对于半双工终端,由上行DCI format调度的PUSCH重复传输、或由DCI调度的PUCCH传输、或由PDCCH order触发的PRACH:
1)当启用/使能AvailableSlotCounting时:
(a)对于重复次数K>1,当PUSCH或PUCCH或PRACH重复传输的第一个符号和同步广播信号块(SSB)传输符号的最后一个符号之间的间隔小于/少于NRX-TX*Tc,和/或当PUSCH或PUCCH或PRACH重复传输的最后一个符号和同步广播信号块(SSB)传输符号的第一个符号之间的间隔小于/少于NTX-RX*Tc时,HD-FDD UE确定该PUSCH或PUCCH或PRACH所在的时隙为不可用时隙,或者该时隙不计入PUSCH或PUCCH或PRACH传输的K个时隙中,HD-FDD UE将PUSCH或PUCCH或PRACH重复传输推迟到下一个可用时隙。
(b)对于重复次数K=1,当PUSCH或PUCCH或PRACH重复传输的第一个符号和同步广播信号块(SSB)传输符号的最后一个符号之间的间隔小于/少于NRX-TX*Tc,和/或当PUSCH或PUCCH或PRACH重复传输的最后一个符号和同步广播信号块(SSB)传输符号的第一个符号之间的间隔小于/少于NTX-RX*Tc时,HD-FDD UE不传输该PUSCH或PUCCH或PRACH,即HD-FDD UE确定该PUSCH或PUCCH或PRACH所在的时隙为可用时隙,或者该时隙计入PUSCH或PUCCH或PRACH传输的K个时隙中。
2)当没有启用/使能AvailableSlotCounting时,对于重复次数K=1和K>1,HD-FDD UE不期望一个PUSCH或PUCCH或PRACH重复传输的第一个符号到同步广播信号块(SSB)传输符号的最后一个符号之间的间隔小于/少于NRX-TX*Tc,和/或HD-FDD UE不期望一个PUSCH或PUCCH或PRACH重复传输的最后一个符号和同步广播信号块(SSB)传输符号的第一个符号之间的间隔小于/少于NTX-RX*Tc。
方式6-4、对于半双工终端,由上行DCI format调度的PUSCH重复传输、或由DCI调度的PUCCH传输、或由PDCCH order触发的PRACH:
1)当启用/使能AvailableSlotCounting时:
(a)对于重复次数K>1,当PUSCH或PUCCH或PRACH重复传输的第一个符号和同步广播信号块(SSB)传输符号的最后一个符号之间的间隔小于/少于NRX-TX*Tc,和/或当PUSCH或PUCCH或PRACH重复传输的最后一个符号和同步广播信号块(SSB)传输符号的第一个符号之间的间隔小于/少于NTX-RX*Tc时,HD-FDD UE确定该PUSCH或PUCCH或PRACH所在的时隙为不可用时隙,或者该时隙不计入PUSCH或PUCCH或PRACH传输的K个时隙中,HD-FDD UE将PUSCH或PUCCH或PRACH重复传输推迟到下一个可用时隙。
(b)对于重复次数K=1,当PUSCH或PUCCH或PRACH重复传输的第一个符号和同步广播信号块(SSB)传输符号的最后一个符号之间的间隔小于/少于NRX-TX*Tc,和/或当PUSCH或PUCCH或PRACH重复传输的最后一个符号和同步广播信号块(SSB)传输符号的第一个符号之间的间隔小于/少于NTX-RX*Tc时,HD-FDD UE不传输该PUSCH或PUCCH或PRACH,即HD-FDD UE确定该PUSCH或PUCCH或PRACH所在的时隙为可用时隙,或者该时隙计入PUSCH或PUCCH或PRACH传输的K个时隙中。
2)当没有启用/使能AvailableSlotCounting时,对于重复次数K=1和K>1,当PUSCH或PUCCH或PRACH重复传输的第一个符号和SSB传输符号的最后一个符号之间的间隔小于/少于NRX-TX*Tc,和/或当PUSCH或PUCCH或PRACH重复传输的最后一个符号和同步广播信号块(SSB)传输符号的第一个符号之间的间隔小于/少于NTX-RX*Tc时,HD-FDD UE不传输该PUSCH或PUCCH或PRACH,即HD-FDD UE确定该PUSCH或PUCCH或PRACH所在的时隙为可用时隙,或者该时隙计入PUSCH或PUCCH或PRACH传输的K个时隙中。
本申请实施例提供的传输方法,实现了半双工RedCap终端和基于有效时隙计数的上行覆盖增强机制的联合操作,特别的提供了当PUSCH重复类型A和SSB资源之间的上下行转换时间不够时终端的行为。通过半双工RedCap终端支持基于有效时隙计数的上行重复传输,可以保证上行覆盖;通 过动态调度和授权调度的上行传输的统一处理,上行传输和下行传输有资源重叠或上下行转换时间不够的统一处理,重复传输次数K=1或K>1的统一处理,均能简化终端的行为和复杂度。
图3是本申请实施例提供的传输方法的流程示意图之二,如图3所示,该方法包括:
步骤301、网络侧设备接收终端上报的第一能力信息;所述第一能力信息用于指示所述终端不期望所述网络侧设备为所述终端使能或配置可用时隙计数;所述网络侧设备为所述终端不使能或不配置可用时隙计数;
或者,网络侧设备在目标条件满足的情况下,执行以下至少一项:
确定终端的目标上行传输所在的目标时隙为所述目标上行传输的不可用时隙,或者确定所述目标时隙不计入所述目标上行传输的传输次数中;
配置目标上行传输和下行接收之间不存在资源重叠,或者配置目标上行传输和下行接收之间的切换时间不小于目标时间;
放弃目标上行接收;
接收目标上行传输;
进行下行发送;
其中,所述终端具有半双工能力或不具有全双工能力。
需要说明的是,本申请实施例可应用于具有半双工能力或不具有全双工能力的终端的上行传输场景中。所述终端包括低能力终端(RedCap UE),例如RedCap半双工(HalfDuplex-frequency-division duplex,HD-FDD)UE。网络侧设备包括但不限于上述所列举的网络侧设备12的类型,本申请对此并不限定。
实际中,第一能力信息用于指示终端不期望所述网络侧设备为所述终端使能或配置可用时隙计数。所述第一能力信息可以包括以下至少一项:1)具有半双工能力;2)不具有全双工能力。终端在向网络侧设备上报第一能力信息的情况下,终端不期望网络侧设备为所述终端使能可用时隙计数(AvailableSlotCounting)。网络侧设备接收终端上报的第一能力信息,所述网 络侧设备为所述终端不使能或不配置可用时隙计数。
具有半双工能力的终端或不具有全双工能力的终端(例如RedCap HD-FDD UE)不支持上行重复传输(例如PUSCH repetition Type A或PUCCH)的次数基于可用时隙计数的机制。举个例子来说,当终端向网络侧设备上报该终端是半双工终端,假设该终端上报的是:RedCap UE with Half-duplex FDD操作类型A(operation type A),则该终端不期待网络侧设备为其配置或者使能可用时隙计数。
可选地,所述目标条件包括以下至少一项:
使能可用时隙计数,或者不使能可用时隙计数;
目标上行传输和下行接收之间存在资源重叠;
目标上行传输和下行接收之间不存在资源重叠,且目标上行传输和下行接收之间的切换时间小于目标时间;
传输次数大于1,或者传输次数等于1;
所述目标上行传输为无线资源控制RRC半静态配置的上行传输;或者所述目标上行传输为动态调度的上行传输。
可选地,所述目标上行传输和下行接收之间的切换时间,包括以下至少一项:
所述目标上行传输的最后一个符号到所述下行接收的第一个符号之间的时间间隔;
所述下行接收的最后一个符号和所述目标上行传输的第一个符号之间的时间间隔。
可选地,所述RRC半静态配置的上行传输包括以下至少一项:
RRC半静态配置的物理上行链路控制信道PUCCH传输;
RRC半静态配置的授权调度的PUSCH类型1 CG PUSCH Type1;
RRC半静态配置的授权调度的PUSCH类型2 CG PUSCH Type2;
除了下行控制信息DCI激活CG PUSCH Type2后的第一个CG PUSCH,其余的CG PUSCH Type 2;
物理随机接入信道PRACH传输。
可选地,所述动态调度的上行传输包括以下至少一项:
由上行授权UL grant调度的PUSCH;
DCI激活CG PUSCH Type 2后的第一个CG PUSCH;
由随机接入响应RAR UL grant调度的PUSCH;
由用临时小区无线网络临时标识符TC-RNTI加扰的DCI format 0_0调度的PUSCH;
动态调度的PUCCH;
动态调度的PRACH;
动态调度的探测参考信号SRS。
可选地,所述下行接收包括以下至少一项:
同步信号/物理广播信道块SSB;
公共搜索空间类型0 Type0 CSS、Type0A CSS、Type1 CSS及Type2 CSS中至少一项;
与控制资源集合#0CORESET#0相关联的下行搜索空间SS。
可选地,所述SSB包括以下至少一项:
由同步广播块在集合中的位置ssb-PositionsInBurst配置的SSB;
由非小区定义SSB nonCellDefiningSSB相关信令配置的SSB;
由专用下行部分带宽BWP-DownlinkDedicated信令配置的SSB;
由终端特定信令UE-specific signalling配置的SSB;
终端当前活动的BWP中所包含的SSB。
本申请实施例提供的传输方法中,通过网络侧设备接收终端上报的第一能力信息;所述第一能力信息用于指示所述终端不期望所述网络侧设备为所述终端使能或配置可用时隙计数;所述网络侧设备基于第一能力信息为所述终端不使能或不配置可用时隙计数;或者网络侧设备在目标条件满足的情况下,执行以下至少一项:确定终端的目标上行传输所在的目标时隙为所述目标上行传输的不可用时隙,或者确定所述目标时隙不计入所述目标上行传输 的传输次数中;配置目标上行传输和下行接收之间不存在资源重叠,或者配置目标上行传输和下行接收之间的切换时间不小于目标时间;放弃目标上行接收;接收目标上行传输;进行下行发送;其中,所述终端具有半双工能力或不具有全双工能力。本申请实施例提供的传输方法能够实现当目标上行传输和下行接收之间存在资源重叠或目标上行传输和下行接收之间的切换时间不够时的统一处理,简化终端的行为和复杂度,通过确定终端的目标上行传输所在的目标时隙为目标上行传输的不可用时隙,或者确定目标时隙不计入目标上行传输的传输次数中的方式,进而将目标上行传输在下一个可用时隙进行传输,如此能够提高上行覆盖。
本申请实施例提供的传输方法,执行主体可以为传输装置。本申请实施例中以传输装置执行传输方法为例,说明本申请实施例提供的传输装置。
图4是本申请实施例提供的传输装置的结构示意图之一,如图4所示,该传输装置400,应用于终端,包括:
第一传输模块401,用于向网络侧设备上报第一能力信息;所述第一能力信息用于指示终端不期望所述网络侧设备为所述终端使能或配置可用时隙计数;
或者,在目标条件满足的情况下,执行以下至少一项:
确定所述终端的目标上行传输所在的目标时隙为所述目标上行传输的不可用时隙,或者确定所述目标时隙不计入所述目标上行传输的传输次数中;
不期望目标上行传输和下行接收之间存在资源重叠,或者不期望目标上行传输和下行接收之间的切换时间小于目标时间;
放弃所述目标上行传输;
进行下行接收;
其中,所述终端具有半双工能力或不具有全双工能力。
本申请实施例提供的传输装置中,通过在向网络侧设备上报第一能力信息的情况下,终端不期望网络侧设备为终端使能或配置可用时隙计数;或者在目标条件满足的情况下,执行以下至少一项:确定具有半双工能力或不具 有全双工能力的终端的目标上行传输所在的目标时隙为目标上行传输的不可用时隙,或者确定目标时隙不计入目标上行传输的传输次数中;不期望目标上行传输和下行接收之间存在资源重叠,或者不期望目标上行传输和下行接收之间的切换时间小于目标时间;放弃目标上行传输;进行下行接收。本申请实施例提供的传输装置能够实现当目标上行传输和下行接收之间存在资源重叠或目标上行传输和下行接收之间的切换时间不够时的统一处理,简化终端的行为和复杂度,通过确定终端的目标上行传输所在的目标时隙为目标上行传输的不可用时隙,或者确定目标时隙不计入目标上行传输的传输次数中的方式,进而将目标上行传输在下一个可用时隙进行传输,如此能够提高上行覆盖。
可选地,所述目标条件包括以下至少一项:
使能可用时隙计数,或者不使能可用时隙计数;
目标上行传输和下行接收之间存在资源重叠;
目标上行传输和下行接收之间不存在资源重叠,且目标上行传输和下行接收之间的切换时间小于目标时间;
传输次数大于1,或者传输次数等于1;
所述目标上行传输为无线资源控制RRC半静态配置的上行传输;或者所述目标上行传输为动态调度的上行传输。
可选地,所述目标上行传输和下行接收之间的切换时间,包括以下至少一项:
所述目标上行传输的最后一个符号到所述下行接收的第一个符号之间的时间间隔;
所述下行接收的最后一个符号和所述目标上行传输的第一个符号之间的时间间隔。
可选地,所述RRC半静态配置的上行传输包括以下至少一项:
RRC半静态配置的物理上行链路控制信道PUCCH传输;
RRC半静态配置的授权调度的PUSCH类型1 CG PUSCH Type1;
RRC半静态配置的授权调度的PUSCH类型2 CG PUSCH Type2;
除了下行控制信息DCI激活CG PUSCH Type2后的第一个CG PUSCH,其余的CG PUSCH Type 2;
物理随机接入信道PRACH传输。
可选地,所述动态调度的上行传输包括以下至少一项:
由上行授权ULgrant调度的PUSCH;
DCI激活CG PUSCH Type 2后的第一个CG PUSCH;
由随机接入响应RAR UL grant调度的PUSCH;
由用临时小区无线网络临时标识符TC-RNTI加扰的DCI format 0_0调度的PUSCH;
动态调度的PUCCH;
动态调度的PRACH;
动态调度的探测参考信号SRS。
可选地,第一传输模块401,进一步用于:
在所述传输次数K=1和K>1的情况下,当所述目标上行传输的第一个符号和下行接收的最后一个符号间隔小于第一阈值,和/或所述目标上行传输的最后一个符号和下行接收的第一个符号间隔小于第二阈值时,确定所述终端的目标上行传输所在的目标时隙为所述目标上行传输的不可用时隙,或者确定所述目标时隙不计入所述目标上行传输的传输次数中;或,
在启动或使能可用时隙计数AvailableSlotCounting,且所述传输次数K=1和K>1的情况下,当所述目标上行传输的第一个符号和下行接收的最后一个符号间隔小于第一阈值,和/或所述目标上行传输的最后一个符号和下行接收的第一个符号间隔小于第二阈值时,确定所述终端的目标上行传输所在的目标时隙为所述目标上行传输的不可用时隙,或者确定所述目标时隙不计入所述目标上行传输的传输次数中;或,
在启动或使能可用时隙计数AvailableSlotCounting,且所述传输次数K>1的情况下,当所述目标上行传输的第一个符号和下行接收的最后一个符号间 隔小于第一阈值,和/或所述目标上行传输的最后一个符号和下行接收的第一个符号间隔小于第二阈值时,确定所述终端的目标上行传输所在的目标时隙为所述目标上行传输的不可用时隙,或者确定所述目标时隙不计入所述目标上行传输的传输次数中。
可选地,第一传输模块401,进一步用于:
在所述传输次数K=1和K>1的情况下,当所述目标上行传输的第一个符号和下行接收的最后一个符号间隔小于第一阈值,和/或所述目标上行传输的最后一个符号和下行接收的第一个符号间隔小于第二阈值时,确定所述终端的目标上行传输所在的目标时隙为所述目标上行传输的可用时隙,或者确定所述目标时隙计入所述目标上行传输的传输次数中;或,
在所述传输次数K=1和K>1的情况下,不期望所述目标上行传输的第一个符号和下行接收的最后一个符号间隔小于第一阈值,和/或不期望所述目标上行传输的最后一个符号和下行接收的第一个符号间隔小于第二阈值;或,
在所述传输次数K=1和K>1的情况下,当所述目标上行传输的第一个符号和下行接收的最后一个符号间隔小于第一阈值,和/或所述目标上行传输的最后一个符号和下行接收的第一个符号间隔小于第二阈值时,放弃所述目标上行传输;或,
在不启动或不使能所述AvailableSlotCounting,且所述传输次数K=1和K>1的情况下,当所述目标上行传输的第一个符号和下行接收的最后一个符号间隔小于第一阈值,和/或所述目标上行传输的最后一个符号和下行接收的第一个符号间隔小于第二阈值时,确定所述终端的目标上行传输所在的目标时隙为所述目标上行传输的可用时隙,或者确定所述目标时隙计入所述目标上行传输的传输次数中;或,
在不启动或不使能所述AvailableSlotCounting,且所述传输次数K=1和K>1的情况下,不期望所述目标上行传输的第一个符号和下行接收的最后一个符号间隔小于第一阈值,和/或不期望所述目标上行传输的最后一个符号和下行接收的第一个符号间隔小于第二阈值;或,
在不启动或不使能所述AvailableSlotCounting,且所述传输次数K=1和K>1的情况下,当所述目标上行传输的第一个符号和下行接收的最后一个符号间隔小于第一阈值,和/或所述目标上行传输的最后一个符号和下行接收的第一个符号间隔小于第二阈值时,放弃所述目标上行传输;或,
在启动或使能所述AvailableSlotCounting,且所述传输次数K=1和K>1的情况下,当所述目标上行传输的第一个符号和下行接收的最后一个符号间隔小于第一阈值,和/或所述目标上行传输的最后一个符号和下行接收的第一个符号间隔小于第二阈值时,确定所述终端的目标上行传输所在的目标时隙为所述目标上行传输的可用时隙,或者确定所述目标时隙计入所述目标上行传输的传输次数中;或,
在启动或使能所述AvailableSlotCounting,且所述传输次数K=1的情况下,当所述目标上行传输的第一个符号和下行接收的最后一个符号间隔小于第一阈值,和/或所述目标上行传输的最后一个符号和下行接收的第一个符号间隔小于第二阈值时,确定所述终端的目标上行传输所在的目标时隙为所述目标上行传输的可用时隙,或者确定所述目标时隙计入所述目标上行传输的传输次数中;或,
在启动或使能所述AvailableSlotCounting,且所述传输次数K=1的情况下,不期望所述目标上行传输的第一个符号和下行接收的最后一个符号间隔小于第一阈值,和/或不期望所述目标上行传输的最后一个符号和下行接收的第一个符号间隔小于第二阈值;或,
在启动或使能所述AvailableSlotCounting,且所述传输次数K>1的情况下,当所述目标上行传输的第一个符号和下行接收的最后一个符号间隔小于第一阈值,和/或所述目标上行传输的最后一个符号和下行接收的第一个符号间隔小于第二阈值时,确定所述终端的目标上行传输所在的目标时隙为所述目标上行传输的可用时隙,或者确定所述目标时隙计入所述目标上行传输的传输次数中。
可选地,所述下行接收包括以下至少一项:
同步信号/物理广播信道块SSB;
公共搜索空间类型0 Type0 CSS、Type0A CSS、Type1 CSS及Type2 CSS中至少一项;
与控制资源集合#0 CORESET#0相关联的下行搜索空间SS。
可选地,所述SSB包括以下至少一项:
由同步广播块在集合中的位置ssb-PositionsInBurst配置的SSB;
由非小区定义SSB nonCellDefiningSSB相关信令配置的SSB;
由专用下行部分带宽BWP-DownlinkDedicated信令配置的SSB;
由终端特定信令UE-specific signalling配置的SSB;
终端当前活动的BWP中所包含的SSB。
可选地,所述第一能力信息包括以下至少一项:
具有半双工能力;
不具有全双工能力。
可选地,所述终端包括:低能力终端RedCap UE。
本申请实施例中的传输装置可以是电子设备,例如具有操作***的电子设备,也可以是电子设备中的部件,例如集成电路或芯片。该电子设备可以是终端,也可以为除终端之外的其他设备。示例性的,终端可以包括但不限于上述所列举的终端11的类型,其他设备可以为服务器、网络附属存储器(Network Attached Storage,NAS)等,本申请实施例不作具体限定。
本申请实施例提供的传输装置能够实现图2所示的方法实施例实现的各个过程,并达到相同的技术效果,为避免重复,这里不再赘述。
图5是本申请实施例提供的传输装置的结构示意图之二,如图5所示,该传输装置500,应用于网络侧设备,包括:
第二传输模块501,用于接收终端上报的第一能力信息;所述第一能力信息用于指示所述终端不期望所述网络侧设备为所述终端使能或配置可用时隙计数;处理模块502,用于为所述终端不使能或不配置可用时隙计数;
或者,第二传输模块501,用于在目标条件满足的情况下,执行以下至 少一项:
确定终端的目标上行传输所在的目标时隙为所述目标上行传输的不可用时隙,或者确定所述目标时隙不计入所述目标上行传输的传输次数中;
配置目标上行传输和下行接收之间不存在资源重叠,或者配置目标上行传输和下行接收之间的切换时间不小于目标时间;
放弃目标上行接收;
接收目标上行传输;
进行下行发送;
其中,所述终端具有半双工能力或不具有全双工能力。
本申请实施例提供的传输装置,通过接收终端上报的第一能力信息;所述第一能力信息用于指示所述终端不期望所述网络侧设备为所述终端使能或配置可用时隙计数;基于第一能力信息为所述终端不使能或不配置可用时隙计数;或者在目标条件满足的情况下,执行以下至少一项:确定终端的目标上行传输所在的目标时隙为所述目标上行传输的不可用时隙,或者确定所述目标时隙不计入所述目标上行传输的传输次数中;配置目标上行传输和下行接收之间不存在资源重叠,或者配置目标上行传输和下行接收之间的切换时间不小于目标时间;放弃目标上行接收;接收目标上行传输;进行下行发送;其中,所述终端具有半双工能力或不具有全双工能力。本申请实施例提供的传输装置能够实现当目标上行传输和下行接收之间存在资源重叠或目标上行传输和下行接收之间的切换时间不够时的统一处理,简化终端的行为和复杂度,通过确定终端的目标上行传输所在的目标时隙为目标上行传输的不可用时隙,或者确定目标时隙不计入目标上行传输的传输次数中的方式,进而将目标上行传输在下一个可用时隙进行传输,如此能够提高上行覆盖。
可选地,所述目标条件包括以下至少一项:
使能可用时隙计数,或者不使能可用时隙计数;
目标上行传输和下行接收之间存在资源重叠;
目标上行传输和下行接收之间不存在资源重叠,且目标上行传输和下行 接收之间的切换时间小于目标时间;
传输次数大于1,或者传输次数等于1;
所述目标上行传输为无线资源控制RRC半静态配置的上行传输;或者所述目标上行传输为动态调度的上行传输。
可选地,所述目标上行传输和下行接收之间的切换时间,包括以下至少一项:
所述目标上行传输的最后一个符号到所述下行接收的第一个符号之间的时间间隔;
所述下行接收的最后一个符号和所述目标上行传输的第一个符号之间的时间间隔。
可选地,所述RRC半静态配置的上行传输包括以下至少一项:
RRC半静态配置的物理上行链路控制信道PUCCH传输;
RRC半静态配置的授权调度的PUSCH类型1 CG PUSCH Type1;
RRC半静态配置的授权调度的PUSCH类型2 CG PUSCH Type2;
除了下行控制信息DCI激活CG PUSCH Type2后的第一个CG PUSCH,其余的CG PUSCH Type 2;
物理随机接入信道PRACH传输。
可选地,所述动态调度的上行传输包括以下至少一项:
由上行授权UL grant调度的PUSCH;
DCI激活CG PUSCH Type 2后的第一个CG PUSCH;
由随机接入响应RAR UL grant调度的PUSCH;
由用临时小区无线网络临时标识符TC-RNTI加扰的DCI format 0_0调度的PUSCH;
动态调度的PUCCH;
动态调度的PRACH;
动态调度的探测参考信号SRS。
可选地,所述第二传输模块501,进一步用于:
在所述传输次数K=1和K>1的情况下,当所述目标上行传输的第一个符号和下行接收的最后一个符号间隔小于第一阈值,和/或所述目标上行传输的最后一个符号和下行接收的第一个符号间隔小于第二阈值时,确定所述终端的目标上行传输所在的目标时隙为所述目标上行传输的不可用时隙,或者确定所述目标时隙不计入所述目标上行传输的传输次数中;或,
在启动或使能可用时隙计数AvailableSlotCounting,且所述传输次数K=1和K>1的情况下,当所述目标上行传输的第一个符号和下行接收的最后一个符号间隔小于第一阈值,和/或所述目标上行传输的最后一个符号和下行接收的第一个符号间隔小于第二阈值时,确定所述终端的目标上行传输所在的目标时隙为所述目标上行传输的不可用时隙,或者确定所述目标时隙不计入所述目标上行传输的传输次数中;或,
在启动或使能可用时隙计数AvailableSlotCounting,且所述传输次数K>1的情况下,当所述目标上行传输的第一个符号和下行接收的最后一个符号间隔小于第一阈值,和/或所述目标上行传输的最后一个符号和下行接收的第一个符号间隔小于第二阈值时,确定所述终端的目标上行传输所在的目标时隙为所述目标上行传输的不可用时隙,或者确定所述目标时隙不计入所述目标上行传输的传输次数中。
可选地,所述第二传输模块501,进一步用于:
在所述传输次数K=1和K>1的情况下,当所述目标上行传输的第一个符号和下行接收的最后一个符号间隔小于第一阈值,和/或所述目标上行传输的最后一个符号和下行接收的第一个符号间隔小于第二阈值时,确定所述终端的目标上行传输所在的目标时隙为所述目标上行传输的可用时隙,或者确定所述目标时隙计入所述目标上行传输的传输次数中;或,
在所述传输次数K=1和K>1的情况下,获知所述终端不期望所述目标上行传输的第一个符号和下行接收的最后一个符号间隔小于第一阈值,和/或获知所述终端不期望所述目标上行传输的最后一个符号和下行接收的第一个符号间隔小于第二阈值;或,
在所述传输次数K=1和K>1的情况下,当所述目标上行传输的第一个符号和下行接收的最后一个符号间隔小于第一阈值,和/或所述目标上行传输的最后一个符号和下行接收的第一个符号间隔小于第二阈值时,放弃所述目标上行接收;或,
在不启动或不使能所述AvailableSlotCounting,且所述传输次数K=1和K>1的情况下,当所述目标上行传输的第一个符号和下行接收的最后一个符号间隔小于第一阈值,和/或所述目标上行传输的最后一个符号和下行接收的第一个符号间隔小于第二阈值时,确定所述终端的目标上行传输所在的目标时隙为所述目标上行传输的可用时隙,或者确定所述目标时隙计入所述目标上行传输的传输次数中;或,
在不启动或不使能所述AvailableSlotCounting,且所述传输次数K=1和K>1的情况下,获知所述终端不期望所述目标上行传输的第一个符号和下行接收的最后一个符号间隔小于第一阈值,和/或获知所述终端不期望所述目标上行传输的最后一个符号和下行接收的第一个符号间隔小于第二阈值;或,
在不启动或不使能所述AvailableSlotCounting,且所述传输次数K=1和K>1的情况下,当所述目标上行传输的第一个符号和下行接收的最后一个符号间隔小于第一阈值,和/或所述目标上行传输的最后一个符号和下行接收的第一个符号间隔小于第二阈值时,放弃所述目标上行接收;或,
在启动或使能所述AvailableSlotCounting,且所述传输次数K=1和K>1的情况下,当所述目标上行传输的第一个符号和下行接收的最后一个符号间隔小于第一阈值,和/或所述目标上行传输的最后一个符号和下行接收的第一个符号间隔小于第二阈值时,确定所述终端的目标上行传输所在的目标时隙为所述目标上行传输的可用时隙,或者确定所述目标时隙计入所述目标上行传输的传输次数中;或,
在启动或使能所述AvailableSlotCounting,且所述传输次数K=1的情况下,当所述目标上行传输的第一个符号和下行接收的最后一个符号间隔小于第一阈值,和/或所述目标上行传输的最后一个符号和下行接收的第一个符号间隔 小于第二阈值时,确定所述终端的目标上行传输所在的目标时隙为所述目标上行传输的可用时隙,或者确定所述目标时隙计入所述目标上行传输的传输次数中;或,
在启动或使能所述AvailableSlotCounting,且所述传输次数K=1的情况下,获知所述终端不期望所述目标上行传输的第一个符号和下行接收的最后一个符号间隔小于第一阈值,和/或获知所述终端不期望所述目标上行传输的最后一个符号和下行接收的第一个符号间隔小于第二阈值;或,
在启动或使能所述AvailableSlotCounting,且所述传输次数K>1的情况下,当所述目标上行传输的第一个符号和下行接收的最后一个符号间隔小于第一阈值,和/或所述目标上行传输的最后一个符号和下行接收的第一个符号间隔小于第二阈值时,确定所述终端的目标上行传输所在的目标时隙为所述目标上行传输的可用时隙,或者确定所述目标时隙计入所述目标上行传输的传输次数中。
可选地,所述下行接收包括以下至少一项:
同步信号/物理广播信道块SSB;
公共搜索空间类型0 Type0 CSS、Type0A CSS、Type1 CSS及Type2 CSS中至少一项;
与控制资源集合#0 CORESET#0相关联的下行搜索空间SS。
可选地,所述SSB包括以下至少一项:
由同步广播块在集合中的位置ssb-PositionsInBurst配置的SSB;
由非小区定义SSB nonCellDefiningSSB相关信令配置的SSB;
由专用下行部分带宽BWP-DownlinkDedicated信令配置的SSB;
由终端特定信令UE-specific signalling配置的SSB;
终端当前活动的BWP中所包含的SSB。
可选地,所述第一能力信息包括以下至少一项:
具有半双工能力;
不具有全双工能力。
可选地,所述终端包括:低能力终端RedCap UE。
图6是本申请实施例提供的通信设备的结构示意图,如图6所示,该通信设备600,包括处理器601和存储器602,存储器602上存储有可在所述处理器601上运行的程序或指令,例如,该通信设备600为终端时,该程序或指令被处理器601执行时实现上述终端侧传输方法实施例的各个步骤,且能达到相同的技术效果。该通信设备600为网络侧设备时,该程序或指令被处理器601执行时实现上述网络侧设备侧传输方法实施例的各个步骤,且能达到相同的技术效果,为避免重复,这里不再赘述。
本申请实施例还提供一种终端,包括处理器和通信接口;其中:
所述通信接口用于向网络侧设备上报第一能力信息;所述第一能力信息用于指示终端不期望所述网络侧设备为所述终端使能或配置可用时隙计数;
或者,所述处理器用于在目标条件满足的情况下,执行以下至少一项:
确定所述终端的目标上行传输所在的目标时隙为所述目标上行传输的不可用时隙,或者确定所述目标时隙不计入所述目标上行传输的传输次数中;
不期望目标上行传输和下行接收之间存在资源重叠,或者不期望目标上行传输和下行接收之间的切换时间小于目标时间;
放弃所述目标上行传输;
进行下行接收;
其中,所述终端具有半双工能力或不具有全双工能力。
该终端实施例与上述终端侧方法实施例对应,上述方法实施例的各个实施过程和实现方式均可适用于该终端实施例中,且能达到相同的技术效果。
图7是本申请实施例提供的终端的结构示意图,如图7所示,该终端700包括但不限于:射频单元701、网络模块702、音频输出单元703、输入单元704、传感器705、显示单元706、用户输入单元707、接口单元708、存储器709以及处理器710等中的至少部分部件。
本领域技术人员可以理解,终端700还可以包括给各个部件供电的电源(比如电池),电源可以通过电源管理***与处理器710逻辑相连,从而通过 电源管理***实现管理充电、放电、以及功耗管理等功能。图7中示出的终端结构并不构成对终端的限定,终端可以包括比图示更多或更少的部件,或者组合某些部件,或者不同的部件布置,在此不再赘述。
应理解的是,本申请实施例中,输入单元704可以包括图形处理单元(Graphics Processing Unit,GPU)7041和麦克风7042,图形处理器7041对在视频捕获模式或图像捕获模式中由图像捕获装置(如摄像头)获得的静态图片或视频的图像数据进行处理。显示单元706可包括显示面板7061,可以采用液晶显示器、有机发光二极管等形式来配置显示面板7061。用户输入单元707包括触控面板7071以及其他输入设备7072中的至少一种。触控面板7071,也称为触摸屏。触控面板7071可包括触摸检测装置和触摸控制器两个部分。其他输入设备7072可以包括但不限于物理键盘、功能键(比如音量控制按键、开关按键等)、轨迹球、鼠标、操作杆,在此不再赘述。
本申请实施例中,射频单元701接收来自网络侧设备的下行数据后,可以传输给处理器710进行处理;另外,射频单元701可以向网络侧设备发送上行数据。通常,射频单元701包括但不限于天线、放大器、收发信机、耦合器、低噪声放大器、双工器等。
存储器709可用于存储软件程序或指令以及各种数据。存储器709可主要包括存储程序或指令的第一存储区和存储数据的第二存储区,其中,第一存储区可存储操作***、至少一个功能所需的应用程序或指令(比如声音播放功能、图像播放功能等)等。此外,存储器709可以包括易失性存储器或非易失性存储器,或者,存储器709可以包括易失性和非易失性存储器两者。其中,非易失性存储器可以是只读存储器(Read-Only Memory,ROM)、可编程只读存储器(Programmable ROM,PROM)、可擦除可编程只读存储器(Erasable PROM,EPROM)、电可擦除可编程只读存储器(Electrically EPROM,EEPROM)或闪存。易失性存储器可以是随机存取存储器(Random Access Memory,RAM),静态随机存取存储器(Static RAM,SRAM)、动态随机存取存储器(Dynamic RAM,DRAM)、同步动态随机存取存储器 (Synchronous DRAM,SDRAM)、双倍数据速率同步动态随机存取存储器(Double Data Rate SDRAM,DDRSDRAM)、增强型同步动态随机存取存储器(Enhanced SDRAM,ESDRAM)、同步连接动态随机存取存储器(Synch link DRAM,SLDRAM)和直接内存总线随机存取存储器(Direct Rambus RAM,DRRAM)。本申请实施例中的存储器709包括但不限于这些和任意其它适合类型的存储器。
处理器710可包括一个或多个处理单元;可选的,处理器710集成应用处理器和调制解调处理器,其中,应用处理器主要处理涉及操作***、用户界面和应用程序等的操作,调制解调处理器主要处理无线通信信号,如基带处理器。可以理解的是,上述调制解调处理器也可以不集成到处理器710中。
其中,射频单元701用于向网络侧设备上报第一能力信息;所述第一能力信息用于指示终端不期望所述网络侧设备为所述终端使能或配置可用时隙计数;
或者,处理器710用于在目标条件满足的情况下,执行以下至少一项:
确定所述终端的目标上行传输所在的目标时隙为所述目标上行传输的不可用时隙,或者确定所述目标时隙不计入所述目标上行传输的传输次数中;
不期望目标上行传输和下行接收之间存在资源重叠,或者不期望目标上行传输和下行接收之间的切换时间小于目标时间;
放弃所述目标上行传输;
进行下行接收;
其中,所述终端具有半双工能力或不具有全双工能力。
本申请实施例提供的终端,通过在向网络侧设备上报第一能力信息的情况下,终端不期望网络侧设备为终端使能或配置可用时隙计数;或者具有半双工能力或不具有全双工能力的终端在目标条件满足的情况下,执行以下至少一项:确定的目标上行传输所在的目标时隙为目标上行传输的不可用时隙,或者确定目标时隙不计入目标上行传输的传输次数中;不期望目标上行传输和下行接收之间存在资源重叠,或者不期望目标上行传输和下行接收之间的 切换时间小于目标时间;放弃目标上行传输;进行下行接收。本申请实施例提供的终端能够实现当目标上行传输和下行接收之间存在资源重叠或目标上行传输和下行接收之间的切换时间不够时的统一处理,简化终端的行为和复杂度,通过确定终端的目标上行传输所在的目标时隙为目标上行传输的不可用时隙,或者确定目标时隙不计入目标上行传输的传输次数中的方式,进而将目标上行传输在下一个可用时隙进行传输,如此能够提高上行覆盖。
可选地,所述目标条件包括以下至少一项:
使能可用时隙计数,或者不使能可用时隙计数;
目标上行传输和下行接收之间存在资源重叠;
目标上行传输和下行接收之间不存在资源重叠,且目标上行传输和下行接收之间的切换时间小于目标时间;
传输次数大于1,或者传输次数等于1;
所述目标上行传输为无线资源控制RRC半静态配置的上行传输;或者所述目标上行传输为动态调度的上行传输。
可选地,所述目标上行传输和下行接收之间的切换时间,包括以下至少一项:
所述目标上行传输的最后一个符号到所述下行接收的第一个符号之间的时间间隔;
所述下行接收的最后一个符号和所述目标上行传输的第一个符号之间的时间间隔。
可选地,所述RRC半静态配置的上行传输包括以下至少一项:
RRC半静态配置的物理上行链路控制信道PUCCH传输;
RRC半静态配置的授权调度的PUSCH类型1 CG PUSCH Type1;
RRC半静态配置的授权调度的PUSCH类型2 CG PUSCH Type2;
除了下行控制信息DCI激活CG PUSCH Type2后的第一个CG PUSCH,其余的CG PUSCH Type 2;
物理随机接入信道PRACH传输。
可选地,所述动态调度的上行传输包括以下至少一项:
由上行授权UL grant调度的PUSCH;
DCI激活CG PUSCH Type 2后的第一个CG PUSCH;
由随机接入响应RAR UL grant调度的PUSCH;
由用临时小区无线网络临时标识符TC-RNTI加扰的DCI format 0_0调度的PUSCH;
动态调度的PUCCH;
动态调度的PRACH;
动态调度的探测参考信号SRS。
可选地,所述处理器710,进一步用于:
在所述传输次数K=1和K>1的情况下,当所述目标上行传输的第一个符号和下行接收的最后一个符号间隔小于第一阈值,和/或所述目标上行传输的最后一个符号和下行接收的第一个符号间隔小于第二阈值时,确定所述终端的目标上行传输所在的目标时隙为所述目标上行传输的不可用时隙,或者确定所述目标时隙不计入所述目标上行传输的传输次数中;或,
在启动或使能可用时隙计数AvailableSlotCounting,且所述传输次数K=1和K>1的情况下,当所述目标上行传输的第一个符号和下行接收的最后一个符号间隔小于第一阈值,和/或所述目标上行传输的最后一个符号和下行接收的第一个符号间隔小于第二阈值时,确定所述终端的目标上行传输所在的目标时隙为所述目标上行传输的不可用时隙,或者确定所述目标时隙不计入所述目标上行传输的传输次数中;或,
在启动或使能可用时隙计数AvailableSlotCounting,且所述传输次数K>1的情况下,当所述目标上行传输的第一个符号和下行接收的最后一个符号间隔小于第一阈值,和/或所述目标上行传输的最后一个符号和下行接收的第一个符号间隔小于第二阈值时,确定所述终端的目标上行传输所在的目标时隙为所述目标上行传输的不可用时隙,或者确定所述目标时隙不计入所述目标上行传输的传输次数中。
可选地,所述处理器710,进一步用于:
在所述传输次数K=1和K>1的情况下,当所述目标上行传输的第一个符号和下行接收的最后一个符号间隔小于第一阈值,和/或所述目标上行传输的最后一个符号和下行接收的第一个符号间隔小于第二阈值时,确定所述终端的目标上行传输所在的目标时隙为所述目标上行传输的可用时隙,或者确定所述目标时隙计入所述目标上行传输的传输次数中;或,
在所述传输次数K=1和K>1的情况下,不期望所述目标上行传输的第一个符号和下行接收的最后一个符号间隔小于第一阈值,和/或不期望所述目标上行传输的最后一个符号和下行接收的第一个符号间隔小于第二阈值;或,
在所述传输次数K=1和K>1的情况下,当所述目标上行传输的第一个符号和下行接收的最后一个符号间隔小于第一阈值,和/或所述目标上行传输的最后一个符号和下行接收的第一个符号间隔小于第二阈值时,放弃所述目标上行传输;或,
在不启动或不使能所述AvailableSlotCounting,且所述传输次数K=1和K>1的情况下,当所述目标上行传输的第一个符号和下行接收的最后一个符号间隔小于第一阈值,和/或所述目标上行传输的最后一个符号和下行接收的第一个符号间隔小于第二阈值时,确定所述终端的目标上行传输所在的目标时隙为所述目标上行传输的可用时隙,或者确定所述目标时隙计入所述目标上行传输的传输次数中;或,
在不启动或不使能所述AvailableSlotCounting,且所述传输次数K=1和K>1的情况下,不期望所述目标上行传输的第一个符号和下行接收的最后一个符号间隔小于第一阈值,和/或不期望所述目标上行传输的最后一个符号和下行接收的第一个符号间隔小于第二阈值;或,
在不启动或不使能所述AvailableSlotCounting,且所述传输次数K=1和K>1的情况下,当所述目标上行传输的第一个符号和下行接收的最后一个符号间隔小于第一阈值,和/或所述目标上行传输的最后一个符号和下行接收的第一个符号间隔小于第二阈值时,放弃所述目标上行传输;或,
在启动或使能所述AvailableSlotCounting,且所述传输次数K=1和K>1的情况下,当所述目标上行传输的第一个符号和下行接收的最后一个符号间隔小于第一阈值,和/或所述目标上行传输的最后一个符号和下行接收的第一个符号间隔小于第二阈值时,确定所述终端的目标上行传输所在的目标时隙为所述目标上行传输的可用时隙,或者确定所述目标时隙计入所述目标上行传输的传输次数中;或,
在启动或使能所述AvailableSlotCounting,且所述传输次数K=1的情况下,当所述目标上行传输的第一个符号和下行接收的最后一个符号间隔小于第一阈值,和/或所述目标上行传输的最后一个符号和下行接收的第一个符号间隔小于第二阈值时,确定所述终端的目标上行传输所在的目标时隙为所述目标上行传输的可用时隙,或者确定所述目标时隙计入所述目标上行传输的传输次数中;或,
在启动或使能所述AvailableSlotCounting,且所述传输次数K=1的情况下,不期望所述目标上行传输的第一个符号和下行接收的最后一个符号间隔小于第一阈值,和/或不期望所述目标上行传输的最后一个符号和下行接收的第一个符号间隔小于第二阈值;或,
在启动或使能所述AvailableSlotCounting,且所述传输次数K>1的情况下,当所述目标上行传输的第一个符号和下行接收的最后一个符号间隔小于第一阈值,和/或所述目标上行传输的最后一个符号和下行接收的第一个符号间隔小于第二阈值时,确定所述终端的目标上行传输所在的目标时隙为所述目标上行传输的可用时隙,或者确定所述目标时隙计入所述目标上行传输的传输次数中。
可选地,所述下行接收包括以下至少一项:
同步信号/物理广播信道块SSB;
公共搜索空间类型0 Type0 CSS、Type0A CSS、Type1 CSS及Type2 CSS中至少一项;
与控制资源集合#0 CORESET#0相关联的下行搜索空间SS。
可选地,所述SSB包括以下至少一项:
由同步广播块在集合中的位置ssb-PositionsInBurst配置的SSB;
由非小区定义SSB nonCellDefiningSSB相关信令配置的SSB;
由专用下行部分带宽BWP-DownlinkDedicated信令配置的SSB;
由终端特定信令UE-specific signalling配置的SSB;
终端当前活动的BWP中所包含的SSB。
可选地,所述第一能力信息包括以下至少一项:
具有半双工能力;
不具有全双工能力。
可选地,所述终端包括:低能力终端RedCap UE。
本申请实施例还提供一种网络侧设备,包括处理器和通信接口;其中:
所述通信接口用于接收终端上报的第一能力信息;所述第一能力信息用于指示所述终端不期望所述网络侧设备为所述终端使能或配置可用时隙计数;所述处理器用于为所述终端不使能或不配置可用时隙计数;
或者,所述处理器用于在目标条件满足的情况下,执行以下至少一项:
确定终端的目标上行传输所在的目标时隙为所述目标上行传输的不可用时隙,或者确定所述目标时隙不计入所述目标上行传输的传输次数中;
配置目标上行传输和下行接收之间不存在资源重叠,或者配置目标上行传输和下行接收之间的切换时间不小于目标时间;
放弃目标上行接收;
接收目标上行传输;
进行下行发送;
其中,所述终端具有半双工能力或不具有全双工能力。
该网络侧设备实施例与上述网络侧设备方法实施例对应,上述方法实施例的各个实施过程和实现方式均可适用于该网络侧设备实施例中,且能达到相同的技术效果。
图8是本申请实施例提供的网络侧设备的结构示意图,如图8所示,该 网络侧设备800包括:天线801、射频装置802、基带装置803、处理器804和存储器805。天线801与射频装置802连接。在上行方向上,射频装置802通过天线801接收信息,将接收的信息发送给基带装置803进行处理。在下行方向上,基带装置803对要发送的信息进行处理,并发送给射频装置802,射频装置802对收到的信息进行处理后经过天线801发送出去。
以上实施例中网络侧设备执行的方法可以在基带装置803中实现,该基带装置803包括基带处理器。
基带装置803例如可以包括至少一个基带板,该基带板上设置有多个芯片,如图8所示,其中一个芯片例如为基带处理器,通过总线接口与存储器805连接,以调用存储器805中的程序,执行以上方法实施例中所示的网络设备操作。
该网络侧设备还可以包括网络接口806,该接口例如为通用公共无线接口(commonpublic radio interface,CPRI)。
具体地,本发明实施例的网络侧设备800还包括:存储在存储器805上并可在处理器804上运行的指令或程序,处理器804调用存储器805中的指令或程序执行如上所述的传输方法,并达到相同的技术效果,为避免重复,故不在此赘述。
本申请实施例还提供了一种传输***,包括:终端及网络侧设备,所述终端可用于执行如上所述的终端侧的传输方法的步骤,所述网络侧设备可用于执行如上所述的网络侧设备侧的传输方法的步骤。
本申请实施例还提供一种可读存储介质,所述可读存储介质可以是以易失性的,也可以是非易失性的,所述可读存储介质上存储有程序或指令,该程序或指令被处理器执行时实现上述传输方法实施例的各个过程,且能达到相同的技术效果,为避免重复,这里不再赘述。
其中,所述处理器为上述实施例中所述的终端中的处理器。所述可读存储介质,包括计算机可读存储介质,如计算机只读存储器ROM、随机存取存储器RAM、磁碟或者光盘等。
本申请实施例另提供了一种芯片,所述芯片包括处理器和通信接口,所述通信接口和所述处理器耦合,所述处理器用于运行程序或指令,实现上述传输方法实施例的各个过程,且能达到相同的技术效果,为避免重复,这里不再赘述。
应理解,本申请实施例提到的芯片还可以称为***级芯片,***芯片,芯片***或片上***芯片等。
本申请实施例另提供了一种计算机程序/程序产品,所述计算机程序/程序产品被存储在存储介质中,所述计算机程序/程序产品被至少一个处理器执行以实现上述传输方法实施例的各个过程,且能达到相同的技术效果,为避免重复,这里不再赘述。
需要说明的是,在本文中,术语“包括”、“包含”或者其任何其他变体意在涵盖非排他性的包含,从而使得包括一系列要素的过程、方法、物品或者装置不仅包括那些要素,而且还包括没有明确列出的其他要素,或者是还包括为这种过程、方法、物品或者装置所固有的要素。在没有更多限制的情况下,由语句“包括一个……”限定的要素,并不排除在包括该要素的过程、方法、物品或者装置中还存在另外的相同要素。此外,需要指出的是,本申请实施方式中的方法和装置的范围不限按示出或讨论的顺序来执行功能,还可包括根据所涉及的功能按基本同时的方式或按相反的顺序来执行功能,例如,可以按不同于所描述的次序来执行所描述的方法,并且还可以添加、省去、或组合各种步骤。另外,参照某些示例所描述的特征可在其他示例中被组合。
通过以上的实施方式的描述,本领域的技术人员可以清楚地了解到上述实施例方法可借助软件加必需的通用硬件平台的方式来实现,当然也可以通过硬件,但很多情况下前者是更佳的实施方式。基于这样的理解,本申请的技术方案本质上或者说对现有技术做出贡献的部分可以以计算机软件产品的形式体现出来,该计算机软件产品存储在一个存储介质(如ROM/RAM、磁碟、光盘)中,包括若干指令用以使得一台终端(可以是手机,计算机,服 务器,空调器,或者网络设备等)执行本申请各个实施例所述的方法。
上面结合附图对本申请的实施例进行了描述,但是本申请并不局限于上述的具体实施方式,上述的具体实施方式仅仅是示意性的,而不是限制性的,本领域的普通技术人员在本申请的启示下,在不脱离本申请宗旨和权利要求所保护的范围情况下,还可做出很多形式,均属于本申请的保护之内。

Claims (27)

  1. 一种传输方法,包括:
    终端向网络侧设备上报第一能力信息;所述第一能力信息用于指示所述终端不期望所述网络侧设备为所述终端使能或配置可用时隙计数;
    或者,终端在目标条件满足的情况下,执行以下至少一项:
    确定所述终端的目标上行传输所在的目标时隙为所述目标上行传输的不可用时隙,或者确定所述目标时隙不计入所述目标上行传输的传输次数中;
    不期望目标上行传输和下行接收之间存在资源重叠,或者不期望目标上行传输和下行接收之间的切换时间小于目标时间;
    放弃所述目标上行传输;
    进行下行接收;
    其中,所述终端具有半双工能力或不具有全双工能力。
  2. 根据权利要求1所述的传输方法,其中,所述目标条件包括以下至少一项:
    使能可用时隙计数,或者不使能可用时隙计数;
    目标上行传输和下行接收之间存在资源重叠;
    目标上行传输和下行接收之间不存在资源重叠,且目标上行传输和下行接收之间的切换时间小于目标时间;
    传输次数大于1,或者传输次数等于1;
    所述目标上行传输为无线资源控制RRC半静态配置的上行传输;或者所述目标上行传输为动态调度的上行传输。
  3. 根据权利要求2所述的传输方法,其中,所述目标上行传输和下行接收之间的切换时间,包括以下至少一项:
    所述目标上行传输的最后一个符号到所述下行接收的第一个符号之间的时间间隔;
    所述下行接收的最后一个符号和所述目标上行传输的第一个符号之间的 时间间隔。
  4. 根据权利要求2或3所述的传输方法,其中,所述RRC半静态配置的上行传输包括以下至少一项:
    RRC半静态配置的物理上行链路控制信道PUCCH传输;
    RRC半静态配置的授权调度的PUSCH类型1 CG PUSCH Type1;
    RRC半静态配置的授权调度的PUSCH类型2 CG PUSCH Type2;
    除了下行控制信息DCI激活CG PUSCH Type2后的第一个CG PUSCH,其余的CG PUSCH Type 2;
    物理随机接入信道PRACH传输。
  5. 根据权利要求2至4中任一项所述的传输方法,其中,所述动态调度的上行传输包括以下至少一项:
    由上行授权UL grant调度的PUSCH;
    DCI激活CG PUSCH Type 2后的第一个CG PUSCH;
    由随机接入响应RAR UL grant调度的PUSCH;
    由用临时小区无线网络临时标识符TC-RNTI加扰的DCI format 0_0调度的PUSCH;
    动态调度的PUCCH;
    动态调度的PRACH;
    动态调度的探测参考信号SRS。
  6. 根据权利要求2至5中任一项所述的传输方法,其中,所述终端在目标条件满足的情况下,确定所述终端的目标上行传输所在的目标时隙为所述目标上行传输的不可用时隙,或者确定所述目标时隙不计入所述目标上行传输的传输次数中,包括:
    在所述传输次数K=1和K>1的情况下,当所述目标上行传输的第一个符号和下行接收的最后一个符号间隔小于第一阈值,和/或所述目标上行传输的最后一个符号和下行接收的第一个符号间隔小于第二阈值时,确定所述终端的目标上行传输所在的目标时隙为所述目标上行传输的不可用时隙,或者确 定所述目标时隙不计入所述目标上行传输的传输次数中;或,
    在启动或使能可用时隙计数AvailableSlotCounting,且所述传输次数K=1和K>1的情况下,当所述目标上行传输的第一个符号和下行接收的最后一个符号间隔小于第一阈值,和/或所述目标上行传输的最后一个符号和下行接收的第一个符号间隔小于第二阈值时,确定所述终端的目标上行传输所在的目标时隙为所述目标上行传输的不可用时隙,或者确定所述目标时隙不计入所述目标上行传输的传输次数中;或,
    在启动或使能可用时隙计数AvailableSlotCounting,且所述传输次数K>1的情况下,当所述目标上行传输的第一个符号和下行接收的最后一个符号间隔小于第一阈值,和/或所述目标上行传输的最后一个符号和下行接收的第一个符号间隔小于第二阈值时,确定所述终端的目标上行传输所在的目标时隙为所述目标上行传输的不可用时隙,或者确定所述目标时隙不计入所述目标上行传输的传输次数中。
  7. 根据权利要求2至5中任一项所述的传输方法,其中,所述终端放弃所述目标上行传输,包括:
    在所述传输次数K=1和K>1的情况下,当所述目标上行传输的第一个符号和下行接收的最后一个符号间隔小于第一阈值,和/或所述目标上行传输的最后一个符号和下行接收的第一个符号间隔小于第二阈值时,确定所述终端的目标上行传输所在的目标时隙为所述目标上行传输的可用时隙,或者确定所述目标时隙计入所述目标上行传输的传输次数中;或,
    在所述传输次数K=1和K>1的情况下,所述终端不期望所述目标上行传输的第一个符号和下行接收的最后一个符号间隔小于第一阈值,和/或所述终端不期望所述目标上行传输的最后一个符号和下行接收的第一个符号间隔小于第二阈值;或,
    在所述传输次数K=1和K>1的情况下,当所述目标上行传输的第一个符号和下行接收的最后一个符号间隔小于第一阈值,和/或所述目标上行传输的最后一个符号和下行接收的第一个符号间隔小于第二阈值时,所述终端放弃 所述目标上行传输;或,
    在不启动或不使能所述AvailableSlotCounting,且所述传输次数K=1和K>1的情况下,当所述目标上行传输的第一个符号和下行接收的最后一个符号间隔小于第一阈值,和/或所述目标上行传输的最后一个符号和下行接收的第一个符号间隔小于第二阈值时,确定所述终端的目标上行传输所在的目标时隙为所述目标上行传输的可用时隙,或者确定所述目标时隙计入所述目标上行传输的传输次数中;或,
    在不启动或不使能所述AvailableSlotCounting,且所述传输次数K=1和K>1的情况下,所述终端不期望所述目标上行传输的第一个符号和下行接收的最后一个符号间隔小于第一阈值,和/或所述终端不期望所述目标上行传输的最后一个符号和下行接收的第一个符号间隔小于第二阈值;或,
    在不启动或不使能所述AvailableSlotCounting,且所述传输次数K=1和K>1的情况下,当所述目标上行传输的第一个符号和下行接收的最后一个符号间隔小于第一阈值,和/或所述目标上行传输的最后一个符号和下行接收的第一个符号间隔小于第二阈值时,所述终端放弃所述目标上行传输;或,
    在启动或使能所述AvailableSlotCounting,且所述传输次数K=1和K>1的情况下,当所述目标上行传输的第一个符号和下行接收的最后一个符号间隔小于第一阈值,和/或所述目标上行传输的最后一个符号和下行接收的第一个符号间隔小于第二阈值时,确定所述终端的目标上行传输所在的目标时隙为所述目标上行传输的可用时隙,或者确定所述目标时隙计入所述目标上行传输的传输次数中;或,
    在启动或使能所述AvailableSlotCounting,且所述传输次数K=1的情况下,当所述目标上行传输的第一个符号和下行接收的最后一个符号间隔小于第一阈值,和/或所述目标上行传输的最后一个符号和下行接收的第一个符号间隔小于第二阈值时,确定所述终端的目标上行传输所在的目标时隙为所述目标上行传输的可用时隙,或者确定所述目标时隙计入所述目标上行传输的传输次数中;或,
    在启动或使能所述AvailableSlotCounting,且所述传输次数K=1的情况下,所述终端不期望所述目标上行传输的第一个符号和下行接收的最后一个符号间隔小于第一阈值,和/或所述终端不期望所述目标上行传输的最后一个符号和下行接收的第一个符号间隔小于第二阈值;或,
    在启动或使能所述AvailableSlotCounting,且所述传输次数K>1的情况下,当所述目标上行传输的第一个符号和下行接收的最后一个符号间隔小于第一阈值,和/或所述目标上行传输的最后一个符号和下行接收的第一个符号间隔小于第二阈值时,确定所述终端的目标上行传输所在的目标时隙为所述目标上行传输的可用时隙,或者确定所述目标时隙计入所述目标上行传输的传输次数中。
  8. 根据权利要求1至7中任一项所述的传输方法,其中,所述下行接收包括以下至少一项:
    同步信号/物理广播信道块SSB;
    公共搜索空间类型0 Type0 CSS、Type0A CSS、Type1 CSS及Type2 CSS中至少一项;
    与控制资源集合#0 CORESET#0相关联的下行搜索空间SS。
  9. 根据权利要求8所述的传输方法,其中,所述SSB包括以下至少一项:
    由同步广播块在集合中的位置ssb-PositionsInBurst配置的SSB;
    由非小区定义SSB nonCellDefiningSSB相关信令配置的SSB;
    由专用下行部分带宽BWP-DownlinkDedicated信令配置的SSB;
    由终端特定信令UE-specific signalling配置的SSB;
    终端当前活动的BWP中所包含的SSB。
  10. 根据权利要求1至9中任一项所述的传输方法,其中,所述第一能力信息包括以下至少一项:
    具有半双工能力;
    不具有全双工能力。
  11. 根据权利要求1至10中任一项所述的传输方法,其中,所述终端包 括:低能力终端RedCap UE。
  12. 一种传输方法,包括:
    网络侧设备接收终端上报的第一能力信息;所述第一能力信息用于指示所述终端不期望所述网络侧设备为所述终端使能或配置可用时隙计数;所述网络侧设备为所述终端不使能或不配置可用时隙计数;
    或者,网络侧设备在目标条件满足的情况下,执行以下至少一项:
    确定终端的目标上行传输所在的目标时隙为所述目标上行传输的不可用时隙,或者确定所述目标时隙不计入所述目标上行传输的传输次数中;
    配置目标上行传输和下行接收之间不存在资源重叠,或者配置目标上行传输和下行接收之间的切换时间不小于目标时间;
    放弃目标上行接收;
    接收目标上行传输;
    进行下行发送;
    其中,所述终端具有半双工能力或不具有全双工能力。
  13. 根据权利要求12所述的传输方法,其中,所述目标条件包括以下至少一项:
    使能可用时隙计数,或者不使能可用时隙计数;
    目标上行传输和下行接收之间存在资源重叠;
    目标上行传输和下行接收之间不存在资源重叠,且目标上行传输和下行接收之间的切换时间小于目标时间;
    传输次数大于1,或者传输次数等于1;
    所述目标上行传输为无线资源控制RRC半静态配置的上行传输;或者所述目标上行传输为动态调度的上行传输。
  14. 根据权利要求13所述的传输方法,其中,所述目标上行传输和下行接收之间的切换时间,包括以下至少一项:
    所述目标上行传输的最后一个符号到所述下行接收的第一个符号之间的时间间隔;
    所述下行接收的最后一个符号和所述目标上行传输的第一个符号之间的时间间隔。
  15. 根据权利要求13或14所述的传输方法,其中,所述RRC半静态配置的上行传输包括以下至少一项:
    RRC半静态配置的物理上行链路控制信道PUCCH传输;
    RRC半静态配置的授权调度的PUSCH类型1 CG PUSCH Type1;
    RRC半静态配置的授权调度的PUSCH类型2 CG PUSCH Type2;
    除了下行控制信息DCI激活CG PUSCH Type2后的第一个CG PUSCH,其余的CG PUSCH Type 2;
    物理随机接入信道PRACH传输。
  16. 根据权利要求13至15任一项所述的传输方法,其中,所述动态调度的上行传输包括以下至少一项:
    由上行授权UL grant调度的PUSCH;
    DCI激活CG PUSCH Type 2后的第一个CG PUSCH;
    由随机接入响应RAR UL grant调度的PUSCH;
    由用临时小区无线网络临时标识符TC-RNTI加扰的DCI format 0_0调度的PUSCH;
    动态调度的PUCCH;
    动态调度的PRACH;
    动态调度的探测参考信号SRS。
  17. 根据权利要求13至16中任一项所述的传输方法,其中,所述网络侧设备在目标条件满足的情况下,确定终端的目标上行传输所在的目标时隙为所述目标上行传输的不可用时隙,或者确定所述目标时隙不计入所述目标上行传输的传输次数中,包括:
    在所述传输次数K=1和K>1的情况下,当所述目标上行传输的第一个符号和下行接收的最后一个符号间隔小于第一阈值,和/或所述目标上行传输的最后一个符号和下行接收的第一个符号间隔小于第二阈值时,确定所述终端 的目标上行传输所在的目标时隙为所述目标上行传输的不可用时隙,或者确定所述目标时隙不计入所述目标上行传输的传输次数中;或,
    在启动或使能可用时隙计数AvailableSlotCounting,且所述传输次数K=1和K>1的情况下,当所述目标上行传输的第一个符号和下行接收的最后一个符号间隔小于第一阈值,和/或所述目标上行传输的最后一个符号和下行接收的第一个符号间隔小于第二阈值时,确定所述终端的目标上行传输所在的目标时隙为所述目标上行传输的不可用时隙,或者确定所述目标时隙不计入所述目标上行传输的传输次数中;或,
    在启动或使能可用时隙计数AvailableSlotCounting,且所述传输次数K>1的情况下,当所述目标上行传输的第一个符号和下行接收的最后一个符号间隔小于第一阈值,和/或所述目标上行传输的最后一个符号和下行接收的第一个符号间隔小于第二阈值时,确定所述终端的目标上行传输所在的目标时隙为所述目标上行传输的不可用时隙,或者确定所述目标时隙不计入所述目标上行传输的传输次数中。
  18. 根据权利要求13至16中任一项所述的传输方法,其中,所述网络侧设备放弃所述目标上行接收,包括:
    在所述传输次数K=1和K>1的情况下,当所述目标上行传输的第一个符号和下行接收的最后一个符号间隔小于第一阈值,和/或所述目标上行传输的最后一个符号和下行接收的第一个符号间隔小于第二阈值时,确定所述终端的目标上行传输所在的目标时隙为所述目标上行传输的可用时隙,或者确定所述目标时隙计入所述目标上行传输的传输次数中;或,
    在所述传输次数K=1和K>1的情况下,获知所述终端不期望所述目标上行传输的第一个符号和下行接收的最后一个符号间隔小于第一阈值,和/或获知所述终端不期望所述目标上行传输的最后一个符号和下行接收的第一个符号间隔小于第二阈值;或,
    在所述传输次数K=1和K>1的情况下,当所述目标上行传输的第一个符号和下行接收的最后一个符号间隔小于第一阈值,和/或所述目标上行传输的 最后一个符号和下行接收的第一个符号间隔小于第二阈值时,所述网络侧设备放弃所述目标上行接收;或,
    在不启动或不使能所述AvailableSlotCounting,且所述传输次数K=1和K>1的情况下,当所述目标上行传输的第一个符号和下行接收的最后一个符号间隔小于第一阈值,和/或所述目标上行传输的最后一个符号和下行接收的第一个符号间隔小于第二阈值时,确定所述终端的目标上行传输所在的目标时隙为所述目标上行传输的可用时隙,或者确定所述目标时隙计入所述目标上行传输的传输次数中;或,
    在不启动或不使能所述AvailableSlotCounting,且所述传输次数K=1和K>1的情况下,获知所述终端不期望所述目标上行传输的第一个符号和下行接收的最后一个符号间隔小于第一阈值,和/或获知所述终端不期望所述目标上行传输的最后一个符号和下行接收的第一个符号间隔小于第二阈值;或,
    在不启动或不使能所述AvailableSlotCounting,且所述传输次数K=1和K>1的情况下,当所述目标上行传输的第一个符号和下行接收的最后一个符号间隔小于第一阈值,和/或所述目标上行传输的最后一个符号和下行接收的第一个符号间隔小于第二阈值时,所述网络侧设备放弃所述目标上行接收;或,
    在启动或使能所述AvailableSlotCounting,且所述传输次数K=1和K>1的情况下,当所述目标上行传输的第一个符号和下行接收的最后一个符号间隔小于第一阈值,和/或所述目标上行传输的最后一个符号和下行接收的第一个符号间隔小于第二阈值时,确定所述终端的目标上行传输所在的目标时隙为所述目标上行传输的可用时隙,或者确定所述目标时隙计入所述目标上行传输的传输次数中;或,
    在启动或使能所述AvailableSlotCounting,且所述传输次数K=1的情况下,当所述目标上行传输的第一个符号和下行接收的最后一个符号间隔小于第一阈值,和/或所述目标上行传输的最后一个符号和下行接收的第一个符号间隔小于第二阈值时,确定所述终端的目标上行传输所在的目标时隙为所述目标 上行传输的可用时隙,或者确定所述目标时隙计入所述目标上行传输的传输次数中;或,
    在启动或使能所述AvailableSlotCounting,且所述传输次数K=1的情况下,获知所述终端不期望所述目标上行传输的第一个符号和下行接收的最后一个符号间隔小于第一阈值,和/或获知所述终端不期望所述目标上行传输的最后一个符号和下行接收的第一个符号间隔小于第二阈值;或,
    在启动或使能所述AvailableSlotCounting,且所述传输次数K>1的情况下,当所述目标上行传输的第一个符号和下行接收的最后一个符号间隔小于第一阈值,和/或所述目标上行传输的最后一个符号和下行接收的第一个符号间隔小于第二阈值时,确定所述终端的目标上行传输所在的目标时隙为所述目标上行传输的可用时隙,或者确定所述目标时隙计入所述目标上行传输的传输次数中。
  19. 根据权利要求12至18中任一项所述的传输方法,其中,所述下行接收包括以下至少一项:
    同步信号/物理广播信道块SSB;
    公共搜索空间类型0 Type0 CSS、Type0A CSS、Type1 CSS及Type2 CSS中至少一项;
    与控制资源集合#0 CORESET#0相关联的下行搜索空间SS。
  20. 根据权利要求19所述的传输方法,其中,所述SSB包括以下至少一项:
    由同步广播块在集合中的位置ssb-PositionsInBurst配置的SSB;
    由非小区定义SSB nonCellDefiningSSB相关信令配置的SSB;
    由专用下行部分带宽BWP-DownlinkDedicated信令配置的SSB;
    由终端特定信令UE-specific signalling配置的SSB;
    终端当前活动的BWP中所包含的SSB。
  21. 根据权利要求12至20中任一项所述的传输方法,其中,所述第一能力信息包括以下至少一项:
    具有半双工能力;
    不具有全双工能力。
  22. 根据权利要求12至21中任一项所述的传输方法,其中,所述终端包括:低能力终端RedCap UE。
  23. 一种传输装置,包括:
    第一传输模块,用于向网络侧设备上报第一能力信息;所述第一能力信息用于指示终端不期望所述网络侧设备为所述终端使能或配置可用时隙计数;
    或者,在目标条件满足的情况下,执行以下至少一项:
    确定所述终端的目标上行传输所在的目标时隙为所述目标上行传输的不可用时隙,或者确定所述目标时隙不计入所述目标上行传输的传输次数中;
    不期望目标上行传输和下行接收之间存在资源重叠,或者不期望目标上行传输和下行接收之间的切换时间小于目标时间;
    放弃所述目标上行传输;
    进行下行接收;
    其中,所述终端具有半双工能力或不具有全双工能力。
  24. 一种传输装置,包括:
    第二传输模块,用于接收终端上报的第一能力信息;所述第一能力信息用于指示所述终端不期望所述网络侧设备为所述终端使能或配置可用时隙计数;处理模块,用于为所述终端不使能或不配置可用时隙计数;
    或者,第二传输模块,用于在目标条件满足的情况下,执行以下至少一项:
    确定终端的目标上行传输所在的目标时隙为所述目标上行传输的不可用时隙,或者确定所述目标时隙不计入所述目标上行传输的传输次数中;
    配置目标上行传输和下行接收之间不存在资源重叠,或者配置目标上行传输和下行接收之间的切换时间不小于目标时间;
    放弃目标上行接收;
    接收目标上行传输;
    进行下行发送;
    其中,所述终端具有半双工能力或不具有全双工能力。
  25. 一种终端,包括处理器和存储器,所述存储器存储可在所述处理器上运行的程序或指令,所述程序或指令被所述处理器执行时实现如权利要求1至11任一项所述的传输方法的步骤。
  26. 一种网络侧设备,包括处理器和存储器,所述存储器存储可在所述处理器上运行的程序或指令,所述程序或指令被所述处理器执行时实现如权利要求12至22任一项所述的传输方法的步骤。
  27. 一种可读存储介质,所述可读存储介质上存储程序或指令,所述程序或指令被处理器执行时实现如权利要求1-11任一项所述的传输方法的步骤,或实现如权利要求12至22任一项所述的传输方法的步骤。
PCT/CN2023/082843 2022-03-25 2023-03-21 传输方法、装置、终端及存储介质 WO2023179618A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202210307763.5A CN116866891A (zh) 2022-03-25 2022-03-25 传输方法、装置、终端及存储介质
CN202210307763.5 2022-03-25

Publications (1)

Publication Number Publication Date
WO2023179618A1 true WO2023179618A1 (zh) 2023-09-28

Family

ID=88099989

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2023/082843 WO2023179618A1 (zh) 2022-03-25 2023-03-21 传输方法、装置、终端及存储介质

Country Status (2)

Country Link
CN (1) CN116866891A (zh)
WO (1) WO2023179618A1 (zh)

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106464452A (zh) * 2014-05-09 2017-02-22 高通股份有限公司 Hd‑fdd harq 操作
CN110249677A (zh) * 2017-02-02 2019-09-17 高通股份有限公司 新无线***中的半双工操作
KR20210000314A (ko) * 2018-05-22 2021-01-04 삼성전자주식회사 리소스 구성 방법, 장치 및 그 저장 매체
WO2022027591A1 (en) * 2020-08-07 2022-02-10 Qualcomm Incorporated Gap configuration in wireless communications

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106464452A (zh) * 2014-05-09 2017-02-22 高通股份有限公司 Hd‑fdd harq 操作
CN110249677A (zh) * 2017-02-02 2019-09-17 高通股份有限公司 新无线***中的半双工操作
KR20210000314A (ko) * 2018-05-22 2021-01-04 삼성전자주식회사 리소스 구성 방법, 장치 및 그 저장 매체
WO2022027591A1 (en) * 2020-08-07 2022-02-10 Qualcomm Incorporated Gap configuration in wireless communications

Also Published As

Publication number Publication date
CN116866891A (zh) 2023-10-10

Similar Documents

Publication Publication Date Title
WO2021159515A1 (zh) 数据传输方法及数据传输装置
US20230412342A1 (en) Resource set configuration method, apparatus, and storage medium
KR102657672B1 (ko) 데이터 전송 방법, 장치, 시스템 및 저장 매체
WO2023116591A1 (zh) 传输确定方法、装置、终端、网络侧设备和存储介质
WO2023284796A1 (zh) Tci状态的指示方法、装置、终端和网络侧设备
WO2023179618A1 (zh) 传输方法、装置、终端及存储介质
WO2024032542A1 (zh) 发射通道切换的处理方法、终端及网络侧设备
WO2024061261A1 (zh) 资源配置方法及装置、终端及网络侧设备
WO2024114492A1 (zh) 测量方法、装置、终端及网络侧设备
WO2024001952A1 (zh) 参数确定方法、终端及网络侧设备
WO2023116905A1 (zh) 定位参考信号的处理方法、设备及可读存储介质
WO2024001985A1 (zh) 通信方法及终端
WO2023116903A1 (zh) Sl信号处理方法、设备及可读存储介质
WO2023165393A1 (zh) 传输方法、装置、终端和存储介质
WO2023198026A1 (zh) 发射功率确定方法、装置、终端、网络侧设备及存储介质
WO2023198071A1 (zh) 信息传输方法、装置、终端及网络侧设备
WO2023198173A1 (zh) 确定sl定位参考信号资源的方法、终端及网络侧设备
WO2022242557A1 (zh) 控制信道监测方法和设备
WO2023186156A1 (zh) Dmrs端口信息的指示方法、终端及网络侧设备
WO2024022316A1 (zh) 下行参考信号发送方法、装置、终端及网络侧设备
WO2023131288A1 (zh) 资源确定方法、装置、终端和网络侧设备
WO2023109759A1 (zh) Prach传输方法、装置及终端
WO2023202632A1 (zh) 资源分配方法、设备及可读存储介质
WO2024082313A1 (zh) 一种传输配置指示状态确定方法、装置、设备及存储介质
WO2024146482A1 (zh) 一种传输参数配置方法、装置及终端设备

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

Country of ref document: EP

Kind code of ref document: A1