Transmission method and device of auxiliary information of receiving terminal, terminal and network side equipment

Abstract

The application discloses a kind of transmission methods of receiving terminal auxiliary information, device, terminal and network side equipment, belong to communication technical field, the transmission method of receiving terminal auxiliary information of the embodiment of the application includes: terminal receives the first information sent by network side equipment;The first information includes at least one of the following: LBT type, the trigger information of sounding reference signal SRS, the trigger information of physical uplink control channel PUCCH, the scheduling information of physical uplink shared channel PUSCH;After the terminal executes Listen Before Talk LBT successfully, the terminal sends receiving terminal auxiliary information to the network side equipment according to the first information;Wherein, the receiving terminal auxiliary information includes at least one of the following: SRS, PUCCH or PUSCH.

Description

Technical Field

[0001] This application belongs to the field of communication technology, and specifically relates to a method, apparatus, terminal and network-side equipment for transmitting auxiliary information at the receiving end. Background Technology

[0002] In future communication systems, shared spectrum, such as unlicensed bands, can supplement licensed bands to help operators expand service capacity. To maintain consistency with NR deployments and maximize NR-based unlicensed access, unlicensed bands can operate in the 5GHz, 37GHz, and 60GHz bands. Because unlicensed bands are shared by various radio access technologies (RATs), such as Wi-Fi, radar, and Long Term Evolution License Assisted Access (LTE-LAA), in some countries or regions, their use must comply with relevant rules to ensure fair use of the resource by all devices. These rules may include Listen Before Talk (LBT) and Maximum Channel Occupancy Time (MCOT). When a transmission node needs to send information, it first performs a Level Bypass (LBT) test, which involves energy detection (ED) of surrounding nodes. If the detected power is below a certain threshold, the channel is considered idle, and the transmission node can transmit. Conversely, if the detected power is above a certain threshold, the channel is considered busy, and the transmission node cannot transmit. Transmission nodes can be base stations, user equipment (UE), Wi-Fi access points (APs), etc. After a transmission node begins transmission, the Channel Occupancy Time (COT) cannot exceed the Channel Capacity Time (MCOT).

[0003] like Figure 1As shown, gNB1 performs a Line-of-Sight (LBT) test before sending data. It detects that the channel is empty, so gNB1 sends data to UE1, and UE1 receives the data. At this time, UE2 needs to send data and performs an LBT test. Because gNB1 is relatively far away, UE2 detects that the channel is empty and begins sending data. However, since gNB2 and gNB1 are on a line-of-sight (LOS) channel, gNB2 can receive the information sent by gNB1. Therefore, gNB2 will experience interference when receiving data from UE2. gNB1 is a hidden node of gNB2. To further reduce interference from the hidden receiving node, a Transmission Request / Clear-To-Send (RTS / CTS) handshake mechanism is introduced. The source node sends an RTS before data transmission. The RTS carries the Network Allocation Vector (NAV) value and the address of the destination node, indicating how long the node will occupy the channel. All nodes that receive this RTS will not attempt to transmit data within the NAV period. Upon receiving the RTS, the destination node replies with a CTS, which carries the NAV value and the address of the source node. All nodes that receive the CTS, except for the source and destination nodes, will not attempt to transmit within the NAV period, thus avoiding the problem of hidden nodes around the destination node.

[0004] The information fed back by the receiver, such as the CTS mentioned above, can be called Receiver Assistance Information (RAI). In the 3GPP communication standard, a similar mechanism can be used to assist the base station in downlink transmission. The base station triggers the terminal to send RAI. After receiving the trigger information, the terminal sends RAI to the base station if it detects that the channel is empty. The base station can only initiate downlink transmission to the terminal after receiving the RAI from the terminal. This RAI indicates that there are no hidden interfering nodes at the terminal. How to send RAI according to the base station's instructions is a technical problem that urgently needs to be solved by those skilled in the art. Summary of the Invention

[0005] This application provides a method, apparatus, terminal, and network-side device for transmitting receiving auxiliary information, which solves the technical problem of how to send receiving auxiliary information according to the instructions of the base station.

[0006] Firstly, a method for transmitting auxiliary information at a receiving end is provided, applied to a terminal, the method comprising:

[0007] The terminal receives first information sent by the network-side device; the first information includes at least one of the following: Listen-Before-Speak (LBT) type, trigger information of Sound Reference Signal (SRS), trigger information of Physical Uplink Control Channel (PUCCH), and scheduling information of Physical Uplink Shared Channel (PUSCH).

[0008] After the terminal successfully performs LBT, the terminal sends receiving assistance information to the network-side device according to the first information; wherein the receiving assistance information includes at least one of the following: SRS, PUCCH or PUSCH.

[0009] Secondly, a method for transmitting receiving auxiliary information is provided, applied to a network-side device, the method comprising:

[0010] The network-side device sends first information to the terminal; the first information includes at least one of the following: Listen-Before-Speak (LBT) type, trigger information of Sound Reference Signal (SRS), trigger information of Physical Uplink Control Channel (PUCCH), and scheduling information of Physical Uplink Shared Channel (PUSCH);

[0011] The network-side device receives receiving assistance information sent by the terminal. The receiving assistance information is sent by the terminal based on the first information after the terminal successfully performs LBT. The receiving assistance information includes at least one of the following: SRS, PUCCH, or PUSCH.

[0012] Thirdly, a device for transmitting auxiliary information at the receiving end is provided, comprising:

[0013] The receiving module is used to receive first information sent by the network-side device; the first information includes at least one of the following: Listen-Before-Speak (LBT) type, trigger information of Sound Reference Signal (SRS), trigger information of Physical Uplink Control Channel (PUCCH), and scheduling information of Physical Uplink Shared Channel (PUSCH).

[0014] The sending module is used to send receiving assistance information to the network-side device according to the first information after the terminal successfully performs LBT; wherein the receiving assistance information includes at least one of the following: SRS, PUCCH or PUSCH.

[0015] Fourthly, a receiving auxiliary information transmission device is provided, comprising:

[0016] The sending module is used to send first information to the terminal; the first information includes at least one of the following: Listen-Before-Speak (LBT) type, trigger information of Sound Reference Signal (SRS), trigger information of Physical Uplink Control Channel (PUCCH), and scheduling information of Physical Uplink Shared Channel (PUSCH);

[0017] A receiving module is configured to receive receiving auxiliary information sent by the terminal, wherein the auxiliary information is sent by the terminal based on the first information after the terminal successfully performs LBT; wherein the auxiliary information includes at least one of the following: SRS, PUCCH, or PUSCH.

[0018] Fifthly, a terminal is provided, the terminal including a processor, a memory, and a program or instructions stored in the memory and executable on the processor, wherein the program or instructions, when executed by the processor, implement the steps of the method described in the first aspect.

[0019] In a sixth aspect, a terminal is provided, including a processor and a communication interface, wherein the communication interface is used to receive first information sent by a network-side device; the first information includes at least one of the following: LBT type, trigger information of sounding reference signal (SRS), trigger information of physical uplink control channel (PUCCH), and scheduling information of physical uplink shared channel (PUSCH); after successfully executing listen-before-speak LBT, receiving auxiliary information is sent to the network-side device according to the first information; wherein the receiving auxiliary information includes at least one of the following: SRS, PUCCH, or PUSCH; the processor is used to execute listen-before-speak LBT.

[0020] In a seventh aspect, a network-side device is provided, the network-side device including a processor, a memory, and a program or instructions stored in the memory and executable on the processor, wherein the program or instructions, when executed by the processor, implement the steps of the method as described in the second aspect.

[0021] Eighthly, a network-side device is provided, including a processor and a communication interface, wherein the communication interface is used to send first information to a terminal; the first information includes at least one of the following: LBT type, triggering information of sounding reference signal (SRS), triggering information of physical uplink control channel (PUCCH), and scheduling information of physical uplink shared channel (PUSCH); the communication interface is also used to receive receiving auxiliary information sent by the terminal, the receiving auxiliary information being sent by the terminal based on the first information after the terminal successfully performs listen-before-speak (LBT); wherein the receiving auxiliary information includes at least one of the following: SRS, PUCCH, or PUSCH.

[0022] A ninth aspect provides a readable storage medium on which a program or instructions are stored, which, when executed by a processor, implement the steps of the method described in the first aspect, or implement the steps of the method described in the second aspect.

[0023] In a tenth aspect, a chip is provided, the chip including a processor and a communication interface coupled to the processor, the processor being configured to run programs or instructions to implement the method as described in the first aspect, or to implement the method as described in the second aspect.

[0024] Eleventhly, a computer program / program product is provided, the computer program / program product being stored in a non-transient storage medium, the program / program product being executed by at least one processor to implement the steps of the method for transmitting receiving auxiliary information as described in the first or second aspect.

[0025] In this embodiment, the terminal receives first information sent by the network-side device. The first information is used to trigger the terminal to send receiving assistance information. The first information includes at least one of the following: LBT type, triggering information of sounding reference signal (SRS), triggering information of physical uplink control channel (PUCCH), and scheduling information of physical uplink shared channel (PUSCH). Further, after the terminal successfully performs listen-before-speak (LBT), the terminal sends receiving assistance information to the network-side device according to the instruction of the first information from the network-side device. The receiving assistance information includes at least one of the following: SRS, PUCCH, or PUSCH. After receiving the receiving assistance information, the network-side device can determine that there are no hidden nodes around the terminal. At this time, sending downlink information to the terminal will not be affected by hidden nodes. Attached Figure Description

[0026] Figure 1 This is an application scenario diagram of an embodiment of this application;

[0027] Figure 2 This is a structural diagram of a wireless communication system to which the embodiments of this application can be applied;

[0028] Figure 3 This is one of the flowcharts illustrating the method for transmitting receiving auxiliary information provided in the embodiments of this application;

[0029] Figure 4 This is one of the interactive flow diagrams of the receiving end auxiliary information transmission method provided in the embodiments of this application;

[0030] Figure 5 This is a second schematic flowchart of the method for transmitting receiving auxiliary information provided in the embodiments of this application;

[0031] Figure 6 This is one of the structural schematic diagrams of the receiving auxiliary information transmission device provided in the embodiments of this application;

[0032] Figure 7 This is a second schematic diagram of the structure of the receiving auxiliary information transmission device provided in the embodiments of this application;

[0033] Figure 8 This is a schematic diagram of the structure of the communication device provided in the embodiments of this application;

[0034] Figure 9 This is a schematic diagram of the hardware structure of the terminal provided in the embodiments of this application;

[0035] Figure 10 This is a schematic diagram of the structure of a network device according to an embodiment of this application. Detailed Implementation

[0036] The technical solutions of the embodiments of this application will be clearly described below with reference to the accompanying drawings. Obviously, the described embodiments are only some, not all, of the embodiments of this application. All other embodiments obtained by those skilled in the art based on the embodiments of this application are within the scope of protection of this application.

[0037] The terms "first," "second," etc., used in the specification and claims of this application are used to distinguish similar objects and not to describe a specific order or sequence. It should be understood that such terms can be used interchangeably where appropriate so that embodiments of this application can be implemented in orders other than those illustrated or described herein, and the objects distinguished by "first" and "second" are generally of the same class, not limited in number; for example, a first object can be one or more. Furthermore, in the specification and claims, "and / or" indicates at least one of the connected objects, and the character " / " generally indicates that the preceding and following objects are in an "or" relationship.

[0038] It is worth noting that the technologies described in this application are not limited to Long Term Evolution (LTE) / LTE-Advanced (LTE-A) systems, but can also be used in other wireless communication systems, such as 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), and other systems. The terms "system" and "network" in this application are often used interchangeably, and the described technologies can be used with the systems and radio technologies mentioned above, as well as with other systems and radio technologies. The following description describes New Radio (NR) systems for illustrative purposes, and the term NR is used in most of the following description; however, these technologies can also be applied to applications other than NR systems, such as 6th generation (6G) radio systems. th Generation 6G communication system.

[0039] Figure 2This diagram illustrates a structural diagram of a wireless communication system applicable to embodiments of this application. The wireless communication system includes a terminal 11 and a network-side device 12. In this context, terminal 11 can also be referred to as a terminal device or user equipment (UE). Terminal 11 can be a mobile phone, tablet computer, laptop computer, personal digital assistant (PDA), handheld computer, netbook, ultra-mobile personal computer (UMPC), mobile internet device (MID), augmented reality (AR) / virtual reality (VR) device, robot, wearable device, vehicle-mounted device (VUE), pedestrian terminal (PUE), smart home (home devices with wireless communication functions, such as refrigerators, televisions, washing machines, or furniture), etc. Wearable devices include: smartwatches, smart bracelets, smart headphones, smart glasses, smart jewelry (smart bracelets, smart chains, smart rings, smart necklaces, smart anklets, smart anklets, etc.), smart wristbands, smart clothing, game consoles, etc. It should be noted that the specific type of terminal 11 is not limited in this application embodiment. Network-side device 12 can be a base station or a core network. The base station can be referred to as a node B, evolved node B, access point, base transceiver station (BTS), radio base station, radio transceiver, basic service set (BSS), extended service set (ESS), B node, evolved B node (eNB), home B node, home evolved B node, WLAN access point, WiFi node, transmitting and receiving point (TRP), or any other suitable term in the field, as long as the same technical effect is achieved. The base station is not limited to specific technical terms. It should be noted that in this application embodiment, only the base station in the NR system is used as an example, but the specific type of base station is not limited.

[0040] The method for transmitting receiving auxiliary information provided in this application will be described in detail below with reference to the accompanying drawings and through some embodiments and application scenarios.

[0041] Figure 3This is one of the flowcharts illustrating the method for transmitting receiving auxiliary information provided in this application. For example... Figure 3 As shown, the method for transmitting receiving auxiliary information provided in this embodiment includes:

[0042] Step 101: The terminal receives the first information sent by the network-side device; the first information includes at least one of the following: LBT type, trigger information of the sounding reference signal SRS, trigger information of the physical uplink control channel PUCCH, and scheduling information of the physical uplink shared channel PUSCH;

[0043] Specifically, before transmitting downlink data, the network-side device sends first information to the terminal. The terminal receives the first information sent by the network-side device. The first information is used to trigger the terminal to send receiving auxiliary information. The first information may include at least one of the following: LBT type, triggering information of Sounding Reference Signal (SRS), triggering information of Physical Uplink Control Channel (PUCCH), and scheduling information of Physical Uplink Shared Channel (PUSCH). The LBT type can be predefined by the protocol, configured by the network-side device, or indicated by signaling, such as by Downlink Control Information (DCI) signaling.

[0044] Optionally, the triggering information for SRS, PUCCH, and PUSCH can be indicated by signaling, such as DCI signaling.

[0045] Optionally, when the first information does not contain an LBT type, the LBT type can be sent via Radio Resource Control (RRC) signaling or as defined by the protocol.

[0046] Optionally, LBT types (Categories) can be categorized into Category 1, Category 2, Category 3, and Category 4. Category 1 LBT involves the transmitting node not performing LBT, i.e., no LBT or immediate transmission. Category 2 LBT is a one-shot LBT, where the node performs an LBT before transmission; if the channel is empty, transmission occurs; otherwise, transmission does not. Category 3 and Category 4 LBT are back-off channel sensing mechanisms. When the transmitting node detects that the channel is busy, it backs off and continues listening until the channel is empty. The contention window size for Category 3 LBT is fixed; the contention window size for Category 4 LBT is variable. Furthermore, Category 4 LBT can also be called the Type 1 channel access mechanism, and Category 2 LBT can also be called the Type 2 channel access mechanism.

[0047] Step 102: After the terminal successfully executes LBT, the terminal sends receiving auxiliary information to the network-side device based on the first information.

[0048] Successful LBT execution means detecting that the channel is idle.

[0049] Optionally, the receiving end assistance information includes at least one of the following: SRS, PUCCH, or PUSCH.

[0050] Specifically, before sending the receiving assistance information, the terminal needs to perform LBT. After the LBT is successful (i.e., the channel is detected to be idle), the terminal sends the receiving assistance information. The specific content of the receiving assistance information needs to be determined according to the instructions of the first information.

[0051] Optionally, it is worth noting that during the process of the terminal sending receiving auxiliary information to the network-side device based on the first information, the terminal does not receive anything.

[0052] Optionally, the terminal can explicitly or implicitly indicate the channel status or LBT result, hidden nodes, and other information to the network-side device via SRS, PUCCH, or PUSCH. For example, when the network-side device receives the receiving-end auxiliary information, it means that the terminal's LBT was successful, or that there are no hidden nodes around the terminal, or that the terminal's channel is empty.

[0053] In this embodiment, the terminal receives first information sent by the network-side device. The first information is used to trigger the terminal to send receiving assistance information. The first information includes at least one of the following: LBT type, triggering information of sounding reference signal (SRS), triggering information of physical uplink control channel (PUCCH), and scheduling information of physical uplink shared channel (PUSCH). Further, after the terminal successfully performs the listen-before-speak LBT, the terminal sends receiving assistance information to the network-side device according to the instruction of the first information from the network-side device. After receiving the receiving assistance information, the network-side device can determine that there are no hidden nodes around the terminal. At this time, sending downlink information to the terminal will not be affected by hidden nodes.

[0054] In one embodiment, after the terminal sends receiving auxiliary information based on the first information, it further includes:

[0055] The terminal receives downlink channels or signals sent by the network side.

[0056] Specifically, if the network-side device receives SRS, PUCCH, or PUSCH of a specific time domain length, the network-side device sends downlink channels / signals such as Group Common (GC) - Physical Downlink Control Channel (PDCCH), PDSCH, and broadcast signals to the terminal.

[0057] In the above implementation, after receiving the receiving auxiliary information, the network-side device can determine that there are no hidden nodes around the terminal and can send downlink channels or signals to the terminal. At this time, sending downlink information to the terminal will not be affected by hidden nodes.

[0058] In one embodiment, the method further includes:

[0059] If the receiving auxiliary information is not successfully sent, the terminal will not perform PDSCH detection.

[0060] Specifically, if the receiving auxiliary information is not successfully transmitted, the terminal does not expect to receive the Physical Downlink Shared Channel (PDSCH) and does not perform PDSCH detection.

[0061] In the above implementation, if the receiving auxiliary information is not successfully sent, the terminal does not perform PDSCH detection, which can reduce the power consumption of the terminal.

[0062] In one embodiment, when the receiving-end auxiliary information includes SRS, the triggering information of SRS is indicated by at least one of the following in the downlink control information (DCI): the sounding reference signal SRS request field, the time domain resource allocation (TDRA) field, the frequency domain resource allocation (FDRA) field, the uplink shared channel (UL-SCH) indication field, and the first indication field.

[0063] When the receiving auxiliary information includes PUCCH, the triggering information of PUCCH is indicated by at least one of the following in the downlink control information (DCI): the sounding reference signal (SRS) request field, the time domain resource allocation (TDRA) field, the frequency domain resource allocation (FDRA) field, and the second indication field.

[0064] When the receiving-end auxiliary information includes the PUSCH, the PUSCH scheduling information includes at least one of the following: LBT type and PUSCH time domain length;

[0065] The first or second indication field is used to indicate whether the physical downlink shared channel (PDSCH) scheduled by DCI is detected.

[0066] Specifically, for the first indicator field and the second indicator field, the DCI may contain only the first indicator field, only the second indicator field, or both. The first indicator field and the second indicator field may be the same or different indicator fields in the DCI. Optionally, if the first indicator field and the second indicator field are the same field, they can be indicated by different fields in the field. Optionally, the DCI is a downlink assignment DCI.

[0067] When the receiving-end auxiliary information includes SRS, the triggering information of SRS is indicated by at least one of the following in the downlink control information (DCI): the sounding reference signal SRS request field, the time domain resource allocation (TDRA) field, the frequency domain resource allocation (TDRA) field, the uplink shared channel (UL-SCH) indication field, and the first indication field.

[0068] When the receiving auxiliary information includes PUCCH, the triggering information of PUCCH is indicated by at least one of the following in the downlink control information (DCI): the sounding reference signal (SRS) request field, the time domain resource allocation (TDRA) field, the frequency domain resource allocation (FDRA) field, and the second indication field.

[0069] Optionally, the first indicator field and the second indicator field can be newly added fields in the DCI, or some fields from the existing fields.

[0070] When the receiving-end auxiliary information includes PUSCH, the scheduling information of PUSCH includes at least one of the following: LBT type and PUSCH time domain length.

[0071] Optionally, PUSCH scheduling information can be carried via uplink allocation DCI.

[0072] When a network-side device instructs a terminal to send SRS, PUCCH, or PUSCH of a specific time domain length using a specific type of LBT, if the network-side device does not detect the corresponding signal or channel, it can continue to instruct the terminal to send SRS, PUCCH, or PUSCH of a specific time domain length using the specific type of LBT until the corresponding signal or channel is received. Before receiving SRS, PUCCH, or PUSCH of a specific time domain length, the network-side device will not send PDSCH to the terminal, and the terminal does not need to detect PDSCH.

[0073] For example, when a network-side device instructs a terminal to send SRS, PUCCH, or a PUSCH of a specific time length using type 2LBT, the terminal will not send SRS, PUCCH, or a PUSCH of a specific time length if it detects that the channel is busy. If the network-side device does not detect the corresponding signal or channel, it can continue to instruct the terminal to send SRS, PUCCH, or a PUSCH of a specific time length using type 2LBT until the corresponding signal or channel is received.

[0074] Optionally, a specific type of LBT includes at least one of the following: type 2 LBT, type 3 LBT, and type 4 LBT, wherein the competition window size of type 3 and type 4 LBT is a target value; optionally, the target value is an integer greater than or equal to 0 and less than or equal to 3.

[0075] Optionally, the length of a specific time domain is either one symbol or two symbols.

[0076] In the above embodiments, the terminal sends different receiving assistance information according to different instructions from the network-side device. After receiving the receiving assistance information, the network-side device can determine that there are no hidden nodes around the terminal. At this time, the downlink information sent to the terminal will not be affected by the hidden nodes.

[0077] In one embodiment, when the receiving auxiliary information includes SRS, the indication method of the first information may be one of the following:

[0078] One scenario:

[0079] The SRS request field in the uplink allocation DCI is set to a first preset value, and the uplink shared channel UL-SCH indication field is set to a second preset value.

[0080] Optionally, the network-side device triggers the terminal to send SRS via DCI format 0_1 ​​or DCI format 0_2.

[0081] Specifically, the SRS request field is set to a first preset value. The UL-SCH indicator field is set to a second preset value. After receiving the first information indication, if the LBT is successful, the terminal only sends the SRS and does not send the PUSCH. If the terminal fails to send the SRS, the terminal does not expect to receive the PDSCH and does not check the PDSCH.

[0082] Optionally, the first preset value is not all zero, and the second preset value is zero.

[0083] Another scenario:

[0084] In the downlink allocation DCI, the SRS request field takes the first preset value, the time domain resource allocation TDRA field takes the invalid value, and the frequency domain resource allocation FDRA field takes the valid value.

[0085] Optionally, the first preset value is not all zeros.

[0086] Specifically, the network-side device configures an invalid entry in the TDRA table via RRC. This invalid entry indicates that the scheduling is invalid. The time-domain resource length indicated by the invalid entry can be zero or the Start And Length Indicator Value (SLIV) value can be invalid.

[0087] Optionally, the network-side device triggers the terminal to send SRS via DCI format 1_1 or DCI format 1_2.

[0088] In this configuration, the SRS request field takes a value that is not all zeros, the TDRA field indicates an invalid value, and the FDRA field indicates a valid value. When the terminal receives this DCI indication, it does not check the PDSCH scheduled by this DCI and ignores invalid PDSCH scheduling.

[0089] When LBT succeeds, the terminal only sends SRS and does not send PUCCH. If the terminal fails to send SRS, the UE does not expect to receive PDSCH and does not perform PDSCH detection.

[0090] Optionally, the terminal ignores the PUCCH Resource Indicator (PRI) and the PDSCH-to-HARQ_feedback timing. The PDSCH-to-HARQ_feedback timing field is used to indicate how long it takes to send HARQ-ACK information after the PDSCH has completed data transmission.

[0091] Another scenario:

[0092] In the downlink allocation DCI, the first indication field takes the third preset value, the SRS request field takes the first preset value, and the FDRA field takes the valid value.

[0093] Optionally, the first preset value is not all zeros.

[0094] Optionally, a first indicator field can be added to DCI format 1_1 or DCI format 1_2, or an existing field can be reused, and an existing field in DCI can be used as the first indicator field, with the length of the first indicator field being at least one bit; or at least one bit can be added to the existing field to indicate whether the PDSCH of the DCI scheduling is detected.

[0095] Specifically, when the first indication field is 1 bit and takes the value of a third preset value, such as 1, the SRS request field is not all zeros, and the FDRA field indicates a valid value, the terminal does not check the PDSCH scheduled by the DCI and does not perform PUCCH transmission, i.e., it ignores the scheduling of PDSCH and PUCCH. Based on the DCI indication, the terminal only sends SRS when LBT is successful. If the terminal fails to send SRS, it does not expect to receive PDSCH.

[0096] Optionally, the terminal ignores PRI and PDSCH-to-HARQ_feedback timing. The PDSCH-to-HARQ_feedback timing field is used to indicate how long after PDSCH completes data transmission should HARQ-ACK information be sent.

[0097] In the above implementation, the terminal sends SRS as receiving assistance information according to the instructions of the network-side device. After receiving the receiving assistance information, the network-side device can determine that there are no hidden nodes around the terminal. At this time, the downlink information sent to the terminal will not be affected by the hidden nodes.

[0098] Optionally, the method further includes:

[0099] The first indication field takes the fourth preset value, the SRS request field takes the first preset value, and the FDRA field takes the valid value. The terminal receives the physical downlink shared channel (PDSCH) scheduled by the network-side equipment.

[0100] Optionally, the first preset value is not all zeros.

[0101] Specifically, when the first indication field is 1 bit and takes the fourth preset value, such as 0, the SRS request field takes the value of non-all zeros, and the FDRA field indicates a valid value, then the terminal receives the PDSCH according to the schedule and sends the SRS and PUCCH after the LBT is successful.

[0102] In the above embodiments, the terminal receives the PDSCH normally scheduled by the network-side device according to the instructions of the network-side device, and sends SRS and PUCCH.

[0103] In one embodiment, when the receiving auxiliary information includes PUCCH, the indication method of the first information may be one of the following:

[0104] One scenario:

[0105] In the downlink allocation DCI, the TDRA field has an invalid value, while the FDRA field has a valid value.

[0106] Specifically, the network-side device configures an invalid value in the TDRA table via RRC. This invalid value indicates that the scheduling is invalid, and the time-domain resource length indicated by the invalid value can be zero or the SLIV can be invalid.

[0107] Optionally, the network-side device triggers the terminal to send PUCCH via DCI format 1_1 or DCI format 1_2.

[0108] Optionally, the value of the SRS request field in the downlink allocation DCI is different from the value of the SRS request field when the receiving auxiliary information includes SRS. In this case, the value of the SRS request field in the downlink allocation DCI can be all zeros.

[0109] For example, the SRS request field is all zeros, the TDRA field indicates an invalid entry, and the FDRA field indicates a valid value. When the terminal receives this DCI indication, it ignores the invalid PDSCH scheduling. When LBT succeeds, the UE sends a PUCCH. If the UE fails to send a PUCCH, the UE does not expect to receive a PDSCH, i.e., it does not check the PDSCH.

[0110] Another scenario:

[0111] In the downlink allocation DCI, the value of the second indicator field is the third preset value, and the value of the FDRA field is a valid value.

[0112] Optionally, a second indicator field can be added to DCI format 1_1 or DCI format 1_2, or an existing field can be reused, and an existing field in DCI can be used as the second indicator field, with the length of the second indicator field being at least one bit; or at least one bit can be added to the existing field to indicate whether the PDSCH of the DCI scheduling is detected.

[0113] Optionally, the SRS request field can be set to all zeros.

[0114] Specifically, when the second indication field is 1 bit and takes the value of a third preset value, such as 1, the SRS request field is all zeros, and the FDRA indication is valid, the terminal ignores the PDSCH scheduling. The UE sends a PUCCH when LBT is successful, according to the DCI indication. If the terminal fails to send the PUCCH, it does not expect to receive the PDSCH.

[0115] In the above implementation, the terminal sends PUCCH as receiving assistance information according to the instructions of the network-side device. After receiving the receiving assistance information, the network-side device can determine that there are no hidden nodes around the terminal. At this time, the downlink information sent to the terminal will not be affected by the hidden nodes.

[0116] Optionally, the method further includes:

[0117] The second indication field takes the fourth preset value, and the FDRA field takes the valid value. The terminal receives the Physical Downlink Shared Channel (PDSCH) scheduled by the network-side equipment.

[0118] Optionally, the SRS request field can be set to all zeros.

[0119] Specifically, the second indication field is 1 bit and takes the fourth preset value, for example, the fourth preset value is 0, the SRS request field takes the value of all zeros, and the FDRA field indicates a valid value. Then the terminal receives the PDSCH according to the schedule and sends the PUCCH after the LBT is successful.

[0120] In the above embodiments, the terminal receives the PDSCH normally scheduled by the network-side device and sends the PUCCH according to the instructions of the network-side device.

[0121] In one embodiment, the LBT type indicated in the DCI is a preset type, the time domain length of the PUSCH is a preset length, and the receiver auxiliary information is the PUSCH.

[0122] Specifically, if the terminal receives a DCI instruction indicating a preset type LBT and a preset length PUSCH, the terminal performs the LBT according to the instruction. If the LBT is successful, the terminal sends the PUSCH. If the terminal has no data to transmit, it generates and sends a padding buffer status report (BSR). If the terminal fails to send a PUSCH of a specific length, the UE does not expect to receive a PDSCH.

[0123] Optionally, the preset length is either 1 symbol length or 2 symbol length.

[0124] Optionally, the preset type is LBT type 2, LBT type 3 or LBT type 4, wherein the competition window size of LBT type 3 and LBT type 4 is a target value; the target value is an integer greater than or equal to 0 and less than or equal to 3.

[0125] In the above implementation, the terminal sends PUSCH as receiving auxiliary information according to the instructions of the network-side device. After receiving the receiving auxiliary information, the network-side device can determine that there are no hidden nodes around the terminal. At this time, the downlink information sent to the terminal will not be affected by the hidden nodes.

[0126] In one embodiment, the method further includes:

[0127] The terminal receives a second message sent by the network-side device. This second message is sent by the network-side device after it has not received any receiving assistance information. The second message triggers the terminal to send receiving assistance information, which is sent after the terminal successfully performs LBT (Local Bit Bypass). Alternatively, the second message can be the first message sent by the network-side device even if it has not received receiving assistance information.

[0128] Optionally, the second information includes at least one of the following: LBT type, triggering information of the sounding reference signal SRS, triggering information of the physical uplink control channel PUCCH, and scheduling information of the physical uplink shared channel PUSCH.

[0129] Specifically, if the network-side device does not receive the receiving-end auxiliary information within a preset time period, it sends a second message to the terminal. The second message is used to trigger the terminal to send the receiving-end auxiliary information. After the terminal successfully executes LBT, it sends the receiving-end auxiliary information.

[0130] The network-side device may not have received the receiving auxiliary information because the terminal did not send it, or because the network-side device did not receive it after the terminal sent it due to signal interference or other reasons.

[0131] In the above implementation, after the network-side device does not receive the receiving-end assistance information, it sends a second message to trigger the terminal to send the receiving-end assistance information. After receiving the receiving-end assistance information, the network-side device can determine that there are no hidden nodes around the terminal. At this time, the downlink information sent to the terminal will not be affected by the hidden nodes.

[0132] like Figure 4 As shown, the method for transmitting receiving auxiliary information provided in this embodiment includes:

[0133] Step 100a: The network-side device sends first information to the terminal; the first information is used to trigger the terminal to send receiving auxiliary information.

[0134] Step 100b: The terminal executes Listen-Then-Speak (LBT).

[0135] Step 102: After the LBT (Listen Before Talk) is successfully executed on the terminal, send auxiliary information to the receiving end based on the first information;

[0136] Step 103a: After receiving the receiving end auxiliary information, the network-side device sends a downlink channel or signal to the terminal;

[0137] Alternatively, in step 103b, after the network-side device fails to receive the receiving auxiliary information, it sends a second message to trigger the terminal to send the receiving auxiliary information.

[0138] The method in this embodiment is similar in its specific implementation process and technical effects to the aforementioned terminal-side method embodiment. For details, please refer to the detailed description in the aforementioned method embodiment, which will not be repeated here.

[0139] Figure 5 This is a second schematic flowchart of the method for transmitting receiving auxiliary information provided in the embodiments of this application. For example... Figure 5 As shown, the method for transmitting receiving auxiliary information provided in this embodiment includes:

[0140] Step 201: The network-side device sends first information to the terminal; the first information includes at least one of the following: LBT type, trigger information of the sounding reference signal SRS, trigger information of the physical uplink control channel PUCCH, and scheduling information of the physical uplink shared channel PUSCH;

[0141] Step 202: The network-side device receives the receiving auxiliary information sent by the terminal. The receiving auxiliary information is sent by the terminal based on the first information after the terminal successfully performs LBT.

[0142] Optionally, the receiving end assistance information includes at least one of the following: SRS, PUCCH, or PUSCH;

[0143] When the receiving-end auxiliary information includes the SRS, the triggering information of the SRS is indicated by at least one of the following in the downlink control information (DCI): the probe reference signal SRS request field, the time domain resource allocation (TDRA) field, the frequency domain resource allocation (FDRA) field, the uplink shared channel (UL-SCH) indication field, and the first indication field.

[0144] When the receiving-end auxiliary information includes the PUCCH, the triggering information of the PUCCH is indicated by at least one of the following in the downlink control information (DCI): the sounding reference signal (SRS) request field, the time domain resource allocation (TDRA) field, the frequency domain resource allocation (FDRA) field, and the second indication field.

[0145] When the receiving-end auxiliary information includes the PUSCH, the scheduling information of the PUSCH includes at least one of the following: LBT type and PUSCH time domain length;

[0146] The first or second indication field is used to indicate whether the physical downlink shared channel (PDSCH) scheduled by the DCI is detected.

[0147] Optionally, if the receiving-end auxiliary information includes the SRS,

[0148] The SRS request field in the uplink allocation DCI is set to a first preset value, and the uplink shared channel UL-SCH indication field is set to a second preset value; or,

[0149] In the downlink allocation DCI, the SRS request field takes the first preset value, the time domain resource allocation TDRA field takes an invalid value, and the frequency domain resource allocation FDRA field takes a valid value; or,

[0150] In the downlink allocation DCI, the first indication field takes the value of the third preset value, the SRS request field takes the value of the first preset value, and the FDRA field takes the value of the valid value.

[0151] Optionally, the method further includes:

[0152] The first indication field is set to a fourth preset value, the SRS request field is set to a first preset value, and the FDRA field is set to a valid value. The terminal receives the Physical Downlink Shared Channel (PDSCH) scheduled by the network-side device.

[0153] Optionally, the first preset value is not all zero, and the second preset value is zero.

[0154] Optionally, if the receiver auxiliary information includes the PUCCH,

[0155] In the downlink allocation DCI, the TDRA field value is invalid, while the FDRA field value is valid; or,

[0156] In the downlink allocation DCI, the value of the second indicator field is the third preset value, and the value of the FDRA field is a valid value.

[0157] Optionally, the method further includes:

[0158] The value of the second indication field is a fourth preset value, and the value of the FDRA field is a valid value. The terminal receives the Physical Downlink Shared Channel (PDSCH) scheduled by the network-side device.

[0159] Optionally, the SRS request field in the downlink allocation DCI is set to all zeros.

[0160] Optionally, the LBT type indicated in the DCI is a preset type, and the time domain length of the PUSCH is a preset length, and the receiver auxiliary information is the PUSCH.

[0161] Optionally, the preset length is one symbol length or two symbol lengths.

[0162] Optionally, the preset type is LBT type 2, LBT type 3, or LBT type 4, wherein the competition window size of LBT type 3 and LBT type 4 is a target value; the target value is an integer greater than or equal to 0 and less than or equal to 3.

[0163] Optionally, the method further includes:

[0164] If the network-side device does not receive the receiving-end assistance information, the network-side device sends a second message to the terminal; the second message is used to trigger the terminal to send receiving-end assistance information, which is sent after the terminal successfully performs LBT.

[0165] Optionally, after receiving the receiving assistance information sent by the terminal, the network-side device further includes:

[0166] The network-side device sends downlink channels or signals to the terminal.

[0167] Optionally, when the first information does not contain an LBT type, the LBT type is sent via Radio Resource Control (RRC) signaling or is agreed upon by a protocol.

[0168] Optionally, when the second information does not contain an LBT type, the LBT type is sent via Radio Resource Control (RRC) signaling or is agreed upon by a protocol.

[0169] The method in this embodiment is similar to the terminal-side method embodiment in terms of its specific implementation process and technical effects. For details, please refer to the detailed description in the terminal-side method embodiment, which will not be repeated here.

[0170] It should be noted that the receiving auxiliary information transmission method provided in this application embodiment can be executed by a receiving auxiliary information transmission device, or by a processing module within the receiving auxiliary information transmission device for executing the receiving auxiliary information transmission method. This application embodiment uses the receiving auxiliary information transmission device executing the receiving auxiliary information transmission method as an example to illustrate the receiving auxiliary information transmission device provided in this application embodiment.

[0171] Figure 6 This is one of the structural schematic diagrams of the receiving auxiliary information transmission device provided in this application. For example... Figure 6 As shown, the receiving auxiliary information transmission device 600 provided in this embodiment includes:

[0172] The receiving module 601 is used to receive first information sent by the network-side device; the first information includes at least one of the following: Listen-Before-Speak (LBT) type, trigger information of Sound Reference Signal (SRS), trigger information of Physical Uplink Control Channel (PUCCH), and scheduling information of Physical Uplink Shared Channel (PUSCH).

[0173] The sending module 602 is used to send receiving assistance information to the network-side device according to the first information after the terminal successfully performs LBT; wherein the receiving assistance information includes at least one of the following: SRS, PUCCH or PUSCH.

[0174] In this embodiment, the receiving module receives first information sent by the network-side device. The first information is used to trigger the terminal to send receiving assistance information. The first information includes at least one of the following: LBT type, triggering information of sounding reference signal (SRS), triggering information of physical uplink control channel (PUCCH), and scheduling information of physical uplink shared channel (PUSCH). Further, after the terminal successfully performs the listen-before-speak LBT, the sending module sends receiving assistance information to the network-side device according to the instruction of the first information from the network-side device. The receiving assistance information includes at least one of the following: SRS, PUCCH, or PUSCH. After receiving the receiving assistance information, the network-side device can determine that there are no hidden nodes around the terminal. At this time, sending downlink information to the terminal will not be affected by hidden nodes.

[0175] Optionally, when the receiving-end auxiliary information includes the SRS, the triggering information of the SRS is indicated by at least one of the following in the downlink control information (DCI): the sounding reference signal SRS request field, the time domain resource allocation (TDRA) field, the frequency domain resource allocation (FDRA) field, the uplink shared channel (UL-SCH) indication field, and the first indication field.

[0176] Optionally, when the receiving-end auxiliary information includes the PUCCH, the triggering information of the PUCCH is indicated by at least one of the following in the downlink control information (DCI): the sounding reference signal (SRS) request field, the time domain resource allocation (TDRA) field, the frequency domain resource allocation (FDRA) field, and the second indication field.

[0177] When the receiving-end auxiliary information includes the PUSCH, the scheduling information of the PUSCH includes at least one of the following: LBT type and PUSCH time domain length;

[0178] The first or second indication field is used to indicate whether the physical downlink shared channel (PDSCH) scheduled by the DCI is detected.

[0179] Optionally, if the receiving-end auxiliary information includes the SRS,

[0180] The SRS request field in the uplink allocation DCI is set to a first preset value, and the uplink shared channel UL-SCH indication field is set to a second preset value; or,

[0181] In the downlink allocation DCI, the SRS request field takes the first preset value, the time domain resource allocation TDRA field takes an invalid value, and the frequency domain resource allocation FDRA field takes a valid value; or,

[0182] In the downlink allocation DCI, the first indication field takes the value of the third preset value, the SRS request field takes the value of the first preset value, and the FDRA field takes the value of the valid value.

[0183] Optionally, the receiving module 601 is also used for:

[0184] The first indication field is set to a fourth preset value, the SRS request field is set to a first preset value, and the FDRA field is set to a valid value, receiving the Physical Downlink Shared Channel (PDSCH) scheduled by the network-side device.

[0185] Optionally, the first preset value is not all zero, and the second preset value is zero.

[0186] Optionally, if the receiver auxiliary information includes the PUCCH,

[0187] In the downlink allocation DCI, the TDRA field value is invalid, while the FDRA field value is valid; or,

[0188] In the downlink allocation DCI, the value of the second indicator field is the third preset value, and the value of the FDRA field is a valid value.

[0189] Optionally, the receiving module 601 is also used for:

[0190] The second indication field takes the fourth preset value, and the FDRA field takes the valid value, receiving the Physical Downlink Shared Channel (PDSCH) scheduled by the network-side device.

[0191] Optionally, the SRS request field in the downlink allocation DCI is set to all zeros.

[0192] Optionally, the LBT type indicated in the DCI is a preset type, and the time domain length of the PUSCH is a preset length, and the receiver auxiliary information is the PUSCH.

[0193] Optionally, the preset length is one symbol length or two symbol lengths.

[0194] Optionally, the preset type is LBT type 2, LBT type 3, or LBT type 4, wherein the competition window size of LBT type 3 and LBT type 4 is a target value; the target value is an integer greater than or equal to 0 and less than or equal to 3.

[0195] Optionally, the LBT type includes at least one of the following: LBT type 2, LBT type 3, and LBT type 4, wherein the competition window size of LBT type 3 and LBT type 4 is a target value; the target value is an integer greater than or equal to 0 and less than or equal to 3.

[0196] Optionally, the receiving module 601 is also used for:

[0197] The terminal receives a second message sent by the network-side device, which is sent by the network-side device after it has not received the receiving end assistance information; the second message is used to trigger the terminal to send receiving end assistance information, which is sent by the terminal after it has successfully performed LBT.

[0198] Optionally, it also includes:

[0199] The processing module is configured not to perform PDSCH detection if the receiving auxiliary information is not successfully transmitted.

[0200] Optionally, the receiving module 601 is also used for:

[0201] Receive downlink channels or signals sent by the network side.

[0202] Optionally, when the first information does not contain an LBT type, the LBT type is sent via Radio Resource Control (RRC) signaling or is agreed upon by a protocol.

[0203] The apparatus of this embodiment can be used to execute the method of any of the aforementioned terminal-side method embodiments. Its specific implementation process and technical effects are similar to those of the terminal-side method embodiments. For details, please refer to the detailed description in the terminal-side method embodiments, which will not be repeated here.

[0204] Figure 7 This is the second schematic diagram of the structure of the receiving auxiliary information transmission device provided in this application. For example... Figure 7 As shown, the receiving auxiliary information transmission device 700 provided in this embodiment includes:

[0205] The sending module 701 is used to send first information to the terminal; the first information includes at least one of the following: Listen-Before-Speak (LBT) type, trigger information of Sound Reference Signal (SRS), trigger information of Physical Uplink Control Channel (PUCCH), and scheduling information of Physical Uplink Shared Channel (PUSCH).

[0206] The receiving module 702 is used to receive receiving auxiliary information sent by the terminal, wherein the auxiliary information is sent by the terminal based on the first information after the terminal successfully performs LBT; wherein the auxiliary information includes at least one of the following: SRS, PUCCH or PUSCH.

[0207] Optionally, when the receiving-end auxiliary information includes the SRS, the triggering information of the SRS is indicated by at least one of the following in the downlink control information (DCI): the sounding reference signal SRS request field, the time domain resource allocation (TDRA) field, the frequency domain resource allocation (FDRA) field, the uplink shared channel (UL-SCH) indication field, and the first indication field.

[0208] When the receiving-end auxiliary information includes the PUCCH, the triggering information of the PUCCH is indicated by at least one of the following in the downlink control information (DCI): the sounding reference signal (SRS) request field, the time domain resource allocation (TDRA) field, the frequency domain resource allocation (FDRA) field, and the second indication field.

[0209] When the receiving-end auxiliary information includes the PUSCH, the scheduling information of the PUSCH includes at least one of the following: LBT type and PUSCH time domain length;

[0210] The first or second indication field is used to indicate whether the physical downlink shared channel (PDSCH) scheduled by the DCI is detected.

[0211] Optionally, if the receiving-end auxiliary information includes the SRS,

[0212] The SRS request field in the uplink allocation DCI is set to a first preset value, and the uplink shared channel UL-SCH indication field is set to a second preset value; or,

[0213] In the downlink allocation DCI, the SRS request field takes the first preset value, the time domain resource allocation TDRA field takes an invalid value, and the frequency domain resource allocation FDRA field takes a valid value; or,

[0214] In the downlink allocation DCI, the first indication field takes the value of the third preset value, the SRS request field takes the value of the first preset value, and the FDRA field takes the value of the valid value.

[0215] Optionally, the transmitting module 701 is also used for:

[0216] The first indication field is set to a fourth preset value, the SRS request field is set to a first preset value, and the FDRA field is set to a valid value, and the Physical Downlink Shared Channel (PDSCH) is sent to the terminal.

[0217] Optionally, the first preset value is not all zero, and the second preset value is zero.

[0218] Optionally, if the receiver auxiliary information includes the PUCCH,

[0219] In the downlink allocation DCI, the TDRA field value is invalid, while the FDRA field value is valid; or,

[0220] In the downlink allocation DCI, the value of the second indicator field is the third preset value, and the value of the FDRA field is a valid value.

[0221] Optionally, the transmitting module 701 is also used for:

[0222] The second indication field takes the value of the fourth preset value, and the FDRA field takes the value of a valid value, and the Physical Downlink Shared Channel (PDSCH) is sent to the terminal.

[0223] Optionally, the SRS request field in the downlink allocation DCI is set to all zeros.

[0224] Optionally, the LBT type indicated in the DCI is a preset type, and the time domain length of the PUSCH is a preset length, and the receiver auxiliary information is the PUSCH.

[0225] Optionally, the preset length is one symbol length or two symbol lengths.

[0226] Optionally, the preset type is LBT type 2, LBT type 3, or LBT type 4, wherein the competition window size of LBT type 3 and LBT type 4 is a target value; the target value is an integer greater than or equal to 0 and less than or equal to 3.

[0227] Optionally, the LBT type includes at least one of the following: LBT type 2, LBT type 3, and LBT type 4, wherein the competition window size of LBT type 3 and LBT type 4 is a target value; the target value is an integer greater than or equal to 0 and less than or equal to 3.

[0228] Optionally, the transmitting module 701 is also used for:

[0229] If the network-side device does not receive the receiving-end assistance information, it sends a second message to the terminal; the second message is used to trigger the terminal to send receiving-end assistance information, which is sent after the terminal successfully performs LBT.

[0230] Optionally, the transmitting module 701 is also used for:

[0231] The network-side device sends downlink channels or signals to the terminal.

[0232] Optionally, when the first information does not contain an LBT type, the LBT type is sent via Radio Resource Control (RRC) signaling or is agreed upon by a protocol.

[0233] The apparatus of this embodiment can be used to execute the method of any of the aforementioned network-side method embodiments. Its specific implementation process and technical effects are similar to those in the network-side method embodiments. For details, please refer to the detailed description in the network-side method embodiments, which will not be repeated here.

[0234] The receiving auxiliary information transmission device in this application embodiment can be a device, a device or electronic device with an operating system, or a component, integrated circuit, or chip in a terminal. This device or electronic device can be a mobile terminal or a non-mobile terminal. For example, a mobile terminal can include, but is not limited to, the types of terminals 11 listed above, while a non-mobile terminal can be a server, network attached storage (NAS), personal computer (PC), television (TV), ATM, or self-service machine, etc. This application embodiment does not impose specific limitations.

[0235] The receiving auxiliary information transmission device provided in this application embodiment can achieve... Figures 3 to 5The various processes implemented in the method embodiments achieve the same technical effect, and will not be described again here to avoid repetition.

[0236] Optional, such as Figure 8 As shown, this application embodiment also provides a communication device 800, including a processor 801, a memory 802, and a program or instructions stored in the memory 802 and executable on the processor 801. For example, when the communication device 800 is a terminal, the program or instructions executed by the processor 801 implement the various processes of the above-described method embodiment for transmitting receiving auxiliary information, and achieve the same technical effect. When the communication device 800 is a network-side device, the program or instructions executed by the processor 801 implement the various processes of the above-described method embodiment for transmitting receiving auxiliary information, and achieve the same technical effect. To avoid repetition, further details are omitted here.

[0237] This application embodiment also provides a terminal, including a processor and a communication interface. The communication interface is used to receive first information sent by a network-side device. The first information includes at least one of the following: LBT type, trigger information of the Sound Reference Signal (SRS), trigger information of the Physical Uplink Control Channel (PUCCH), and scheduling information of the Physical Uplink Shared Channel (PUSCH). After successfully executing the Listen-Before-Speak LBT, the terminal sends receiving auxiliary information to the network-side device according to the first information. The processor is used to execute the Listen-Before-Speak LBT. This terminal embodiment corresponds to the above-described terminal-side method embodiment. All implementation processes and methods of the above-described method embodiments can be applied to this terminal embodiment and achieve the same technical effect. Specifically, Figure 9 A schematic diagram of the hardware structure of a terminal to implement an embodiment of this application.

[0238] The terminal 1000 includes, but is not limited to, at least some of the following components: radio frequency unit 1001, network module 1002, audio output unit 1003, input unit 1004, sensor 1005, display unit 1006, user input unit 1007, interface unit 1008, memory 1009, and processor 1010.

[0239] Those skilled in the art will understand that the terminal 1000 may also include a power supply (such as a battery) for supplying power to various components. The power supply may be logically connected to the processor 1010 through a power management system, thereby enabling functions such as managing charging, discharging, and power consumption through the power management system. Figure 9 The terminal structure shown does not constitute a limitation on the terminal. The terminal may include more or fewer components than shown, or combine certain components, or have different component arrangements, which will not be elaborated here.

[0240] It should be understood that, in this embodiment, the input unit 1004 may include a graphics processing unit (GPU) 10041 and a microphone 10042. The GPU 10041 processes image data of still images or videos obtained by an image capture device (such as a camera) in video capture mode or image capture mode. The display unit 1006 may include a display panel 10061, which may be configured in the form of a liquid crystal display, an organic light-emitting diode, or the like. The user input unit 1007 includes a touch panel 10071 and other input devices 10072. The touch panel 10071 is also called a touch screen. The touch panel 10071 may include a touch detection device and a touch controller. Other input devices 10072 may include, but are not limited to, physical keyboards, function keys (such as volume control buttons, power buttons, etc.), trackballs, mice, and joysticks, which will not be described in detail here.

[0241] In this embodiment, the radio frequency unit 1001 receives downlink data from the network-side device and processes it for the processor 1010; additionally, it sends uplink data to the network-side device. Typically, the radio frequency unit 1001 includes, but is not limited to, an antenna, at least one amplifier, a transceiver, a coupler, a low-noise amplifier, a duplexer, etc.

[0242] The memory 1009 can be used to store software programs or instructions and various data. The memory 1009 may primarily include a program or instruction storage area and a data storage area. The program or instruction storage area may store the operating system, application programs or instructions required for at least one function (such as sound playback, image playback, etc.). Furthermore, the memory 1009 may include high-speed random access memory and non-volatile memory, wherein the non-volatile memory may be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), or flash memory. For example, at least one disk storage device, flash memory device, or other non-volatile solid-state storage device.

[0243] Processor 1010 may include one or more processing units; optionally, processor 1010 may integrate an application processor and a modem processor, wherein the application processor mainly handles the operating system, user interface, and applications or instructions, and the modem processor mainly handles wireless communication, such as a baseband processor. It is understood that the aforementioned modem processor may also not be integrated into processor 1010.

[0244] The radio frequency unit 1001 is used to receive first information sent by the network-side device; the first information includes at least one of the following: LBT type, trigger information of the sounding reference signal SRS, trigger information of the physical uplink control channel PUCCH, and scheduling information of the physical uplink shared channel PUSCH.

[0245] The radio frequency unit 1001 is further configured to send receiving assistance information to the network-side device according to the first information after the terminal successfully performs LBT; wherein the receiving assistance information includes at least one of the following: SRS, PUCCH or PUSCH.

[0246] In this embodiment, the radio frequency unit receives first information sent by the network-side device. The first information is used to trigger the terminal to send receiving assistance information. The first information includes at least one of the following: LBT type, triggering information of sounding reference signal (SRS), triggering information of physical uplink control channel (PUCCH), and scheduling information of physical uplink shared channel (PUSCH). Further, after the terminal successfully performs the listen-before-speak LBT, the radio frequency unit sends receiving assistance information to the network-side device according to the instruction of the first information from the network-side device. The receiving assistance information includes at least one of the following: SRS, PUCCH, or PUSCH. After receiving the receiving assistance information, the network-side device can determine that there are no hidden nodes around the terminal. At this time, sending downlink information to the terminal will not be affected by hidden nodes.

[0247] Optionally, when the receiving-end auxiliary information includes the SRS, the triggering information of the SRS is indicated by at least one of the following in the downlink control information (DCI): the sounding reference signal SRS request field, the time domain resource allocation (TDRA) field, the frequency domain resource allocation (FDRA) field, the uplink shared channel (UL-SCH) indication field, and the first indication field.

[0248] Optionally, when the receiving-end auxiliary information includes the PUCCH, the triggering information of the PUCCH is indicated by at least one of the following in the downlink control information (DCI): the sounding reference signal (SRS) request field, the time domain resource allocation (TDRA) field, the frequency domain resource allocation (FDRA) field, and the second indication field.

[0249] When the receiving-end auxiliary information includes the PUSCH, the scheduling information of the PUSCH includes at least one of the following: LBT type and PUSCH time domain length;

[0250] The first or second indication field is used to indicate whether the physical downlink shared channel (PDSCH) scheduled by the DCI is detected.

[0251] In the above embodiments, the terminal sends different receiving assistance information according to different instructions from the network-side device. After receiving the receiving assistance information, the network-side device can determine that there are no hidden nodes around the terminal. At this time, the downlink information sent to the terminal will not be affected by the hidden nodes.

[0252] Optionally, if the receiving-end auxiliary information includes the SRS,

[0253] The SRS request field in the uplink allocation DCI is set to a first preset value, and the uplink shared channel UL-SCH indication field is set to a second preset value; or,

[0254] In the downlink allocation DCI, the SRS request field takes the first preset value, the time domain resource allocation TDRA field takes an invalid value, and the frequency domain resource allocation FDRA field takes a valid value; or,

[0255] In the downlink allocation DCI, the first indication field takes the value of the third preset value, the SRS request field takes the value of the first preset value, and the FDRA field takes the value of the valid value.

[0256] In the above implementation, the terminal sends SRS as receiving assistance information according to the instructions of the network-side device. After receiving the receiving assistance information, the network-side device can determine that there are no hidden nodes around the terminal. At this time, the downlink information sent to the terminal will not be affected by the hidden nodes.

[0257] Optionally, the radio frequency unit 1001 is also used for:

[0258] The first indication field is set to a fourth preset value, the SRS request field is set to a first preset value, and the FDRA field is set to a valid value, receiving the Physical Downlink Shared Channel (PDSCH) scheduled by the network-side device.

[0259] In the above embodiments, the terminal receives the PDSCH normally scheduled by the network-side device according to the instructions of the network-side device, and sends SRS and PUCCH.

[0260] Optionally, the first preset value is not all zero, and the second preset value is zero.

[0261] Optionally, if the receiver auxiliary information includes the PUCCH,

[0262] In the downlink allocation DCI, the TDRA field value is invalid, while the FDRA field value is valid; or,

[0263] In the downlink allocation DCI, the value of the second indicator field is the third preset value, and the value of the FDRA field is a valid value.

[0264] In the above implementation, the terminal sends PUCCH as receiving assistance information according to the instructions of the network-side device. After receiving the receiving assistance information, the network-side device can determine that there are no hidden nodes around the terminal. At this time, the downlink information sent to the terminal will not be affected by the hidden nodes.

[0265] Optionally, the radio frequency unit 1001 is also used for:

[0266] The second indication field takes the fourth preset value, and the FDRA field takes the valid value, receiving the Physical Downlink Shared Channel (PDSCH) scheduled by the network-side device.

[0267] Optionally, the SRS request field in the downlink allocation DCI is set to all zeros.

[0268] In the above embodiments, the terminal receives the PDSCH normally scheduled by the network-side device and sends the PUCCH according to the instructions of the network-side device.

[0269] Optionally, the LBT type indicated in the DCI is a preset type, and the time domain length of the PUSCH is a preset length, and the receiver auxiliary information is the PUSCH.

[0270] Optionally, the preset length is one symbol length or two symbol lengths.

[0271] Optionally, the preset type is LBT type 2, LBT type 3, or LBT type 4, wherein the competition window size of LBT type 3 and LBT type 4 is a target value; the target value is an integer greater than or equal to 0 and less than or equal to 3.

[0272] In the above implementation, the terminal sends PUSCH as receiving auxiliary information according to the instructions of the network-side device. After receiving the receiving auxiliary information, the network-side device can determine that there are no hidden nodes around the terminal. At this time, the downlink information sent to the terminal will not be affected by the hidden nodes.

[0273] Optionally, the LBT type includes at least one of the following: LBT type 2, LBT type 3, and LBT type 4, wherein the competition window size of LBT type 3 and LBT type 4 is a target value; the target value is an integer greater than or equal to 0 and less than or equal to 3.

[0274] Optionally, the radio frequency unit 1001 is also used for:

[0275] The terminal receives a second message sent by the network-side device, which is sent by the network-side device after it has not received the receiving end assistance information; the second message is used to trigger the terminal to send receiving end assistance information, which is sent by the terminal after it has successfully performed LBT.

[0276] In the above implementation, after the network-side device does not receive the receiving-end assistance information, it sends a second message to trigger the terminal to send the receiving-end assistance information. After receiving the receiving-end assistance information, the network-side device can determine that there are no hidden nodes around the terminal. At this time, the downlink information sent to the terminal will not be affected by the hidden nodes.

[0277] Optionally, the processor 1010 is configured not to perform PDSCH detection if the receiving auxiliary information is not successfully transmitted.

[0278] In the above implementation, if the receiving auxiliary information is not successfully sent, the terminal does not perform PDSCH detection, which can reduce the power consumption of the terminal.

[0279] Optionally, the radio frequency unit 1001 is also used for:

[0280] Receive downlink channels or signals sent by the network side.

[0281] In the above implementation, after receiving the receiving auxiliary information, the network-side device can determine that there are no hidden nodes around the terminal. At this time, sending downlink information to the terminal will not be affected by the hidden nodes.

[0282] Optionally, when the first information does not contain an LBT type, the LBT type is sent via Radio Resource Control (RRC) signaling or is agreed upon by a protocol.

[0283] This application embodiment also provides a network-side device, including a processor and a communication interface. The communication interface is used to send first information to a terminal. The first information includes at least one of the following: LBT type, triggering information of the Sound Reference Signal (SRS), triggering information of the Physical Uplink Control Channel (PUCCH), and scheduling information of the Physical Uplink Shared Channel (PUSCH). The communication interface is also used to receive receiving auxiliary information sent by the terminal. The receiving auxiliary information is sent by the terminal based on the first information after the terminal successfully performs the Listen-Before-Speak LBT. The receiving auxiliary information includes at least one of the following: SRS, PUCCH, or PUSCH. This network-side device embodiment corresponds to the above-described network-side device method embodiment. All implementation processes and methods of the above method embodiments can be applied to this network-side device embodiment and achieve the same technical effects.

[0284] Specifically, embodiments of this application also provide a network-side device. For example... Figure 10 As shown, the network device 170 includes an antenna 71, a radio frequency (RF) device 72, and a baseband device 73. The antenna 71 is connected to the RF device 72. In the uplink direction, the RF device 72 receives information through the antenna 71 and transmits the received information to the baseband device 73 for processing. In the downlink direction, the baseband device 73 processes the information to be transmitted and sends it to the RF device 72. The RF device 72 processes the received information and transmits it through the antenna 71.

[0285] The aforementioned frequency band processing device can be located in the baseband device 73. The method executed by the network device in the above embodiments can be implemented in the baseband device 73, which includes a processor 74 and a memory 75.

[0286] The baseband device 73 may include, for example, at least one baseband board on which multiple chips are disposed, such as... Figure 10 As shown, one of the chips, for example, is a processor 74, which is connected to a memory 75 to call the program in the memory 75 and execute the network device operations shown in the above method embodiment.

[0287] The baseband device 73 may also include a network interface 76 for exchanging information with the radio frequency device 72, such as a common public radio interface (CPRI).

[0288] Specifically, the network device in this application embodiment further includes: instructions or programs stored in memory 75 and executable on processor 74, wherein processor 74 calls the instructions or programs in memory 75 to execute. Figure 7 The methods executed by each module shown achieve the same technical effect, and to avoid repetition, they will not be described in detail here.

[0289] This application also provides a readable storage medium storing a program or instructions. When the program or instructions are executed by a processor, they implement the various processes of the above-described method for transmitting auxiliary information at the receiving end, and achieve the same technical effect. To avoid repetition, they will not be described again here.

[0290] The processor mentioned above is the processor in the terminal described in the above embodiments. 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.

[0291] This application embodiment also provides a chip, which 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 various processes of the above-described method embodiment for transmitting auxiliary information at the receiving end, and can achieve the same technical effect. To avoid repetition, it will not be described again here.

[0292] It should be understood that the chip mentioned in the embodiments of this application may also be referred to as a system-on-a-chip, system chip, chip system, or system-on-a-chip, etc.

[0293] This application also provides a computer program / program product, which is stored in a non-transient storage medium. The program / program product is executed by at least one processor to implement the various processes of the above-described method embodiment for transmitting auxiliary information at the receiving end, and can achieve the same technical effect. To avoid repetition, it will not be described again here.

[0294] It should be noted that, in this document, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitations, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes that element. Furthermore, it should be noted that the scope of the methods and apparatuses in the embodiments of this application is not limited to performing functions in the order shown or discussed, but may also include performing functions substantially simultaneously or in the reverse order, depending on the functions involved. For example, the described methods may be performed in a different order than described, and various steps may be added, omitted, or combined. Additionally, features described with reference to certain examples may be combined in other examples.

[0295] Through the above description of the embodiments, those skilled in the art can clearly understand that the methods of the above embodiments can be implemented by means of software plus necessary general-purpose hardware platforms. Of course, they can also be implemented by hardware, but in many cases the former is a better implementation method. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, can be embodied in the form of a computer software product. This computer software product is stored in a storage medium (such as ROM / RAM, magnetic disk, optical disk) and includes several instructions to cause a terminal (which may be a mobile phone, computer, server, or network device, etc.) to execute the methods described in the various embodiments of this application.

[0296] The embodiments of this application have been described above with reference to the accompanying drawings. However, this application is not limited to the specific embodiments described above. The specific embodiments described above are merely illustrative and not restrictive. Those skilled in the art can make many other forms under the guidance of this application without departing from the spirit and scope of the claims, and all of these forms are within the protection scope of this application.

Claims

1. A method for transmission of a donor assistance information, characterized in that, include: The terminal receives the first information sent by the network-side device; The first information includes: triggering information of the sounding reference signal (SRS), triggering information of the physical uplink control channel (PUCCH), or scheduling information of the physical uplink shared channel (PUSCH); After the terminal successfully performs LBT, the terminal sends receiving assistance information to the network-side device according to the first information; wherein, the receiving assistance information includes: SRS, PUCCH or PUSCH; When the receiving-end auxiliary information includes the SRS, the triggering information of the SRS is indicated by at least one of the following in the downlink control information (DCI): the sounding reference signal SRS request field, the time domain resource allocation (TDRA) field, the frequency domain resource allocation (FDRA) field, the uplink shared channel (UL-SCH) indication field, and the first indication field. When the receiving-end auxiliary information includes the PUCCH, the triggering information of the PUCCH is indicated by at least one of the following in the downlink control information (DCI): the sounding reference signal (SRS) request field, the time domain resource allocation (TDRA) field, the frequency domain resource allocation (FDRA) field, and the second indication field. When the receiving end auxiliary information includes the PUSCH, the scheduling information of the PUSCH includes at least one of the following: LBT type, time domain length of the PUSCH; the time domain length of the PUSCH is a preset length. The first or second indication field is used to indicate whether the physical downlink shared channel (PDSCH) scheduled by the DCI is detected.

2. The method of claim 1, wherein the transmission of the information is triggered by a request from the remote terminal. When the receiving-end auxiliary information includes the SRS. The SRS request field in the uplink allocation DCI is set to a first preset value, and the uplink shared channel UL-SCH indication field is set to a second preset value; or, In the downlink allocation DCI, the SRS request field takes the first preset value, the time domain resource allocation TDRA field takes an invalid value, and the frequency domain resource allocation FDRA field takes a valid value; or, In the downlink allocation DCI, the first indication field takes the value of the third preset value, the SRS request field takes the value of the first preset value, and the FDRA field takes the value of the valid value.

3. The method of claim 2, wherein the transmission of the information is triggered by a request from the UE. Also includes: The first indication field is set to a fourth preset value, the SRS request field is set to a first preset value, and the FDRA field is set to a valid value. The terminal receives the Physical Downlink Shared Channel (PDSCH) scheduled by the network-side device.

4. The method for transmitting receiving auxiliary information according to claim 2 or 3, The first preset value is not all zero, and the second preset value is zero.

5. The method of claim 1, wherein the transmission of the information is triggered by a request from the UE. When the receiver auxiliary information includes the PUCCH. In the downlink allocation DCI, the TDRA field value is invalid, while the FDRA field value is valid; or, In the downlink allocation DCI, the value of the second indicator field is the third preset value, and the value of the FDRA field is a valid value.

6. The method of claim 5, wherein the transmission of the information is triggered by a request from the UE. The method further includes: The value of the second indication field is a fourth preset value, and the value of the FDRA field is a valid value. The terminal receives the Physical Downlink Shared Channel (PDSCH) scheduled by the network-side device.

7. The method for transmitting receiving auxiliary information according to claim 5 or 6, characterized in that, The SRS request field in the downlink allocation DCI is set to all zeros.

8. The method of claim 1, wherein, The first information also includes: LBT type; The LBT type indicated in the DCI is a preset type, and the receiver auxiliary information is PUSCH.

9. The method for transmitting receiving auxiliary information according to claim 8, characterized in that, The preset length is either one symbol length or two symbol lengths.

10. The method for transmitting receiving auxiliary information according to claim 9, characterized in that, The preset type is LBT type 2, LBT type 3 or LBT type 4, wherein the competition window size of LBT type 3 and LBT type 4 is a target value; the target value is an integer greater than or equal to 0 and less than or equal to 3.

11. The method for transmitting receiving auxiliary information according to any one of claims 1-3, 5-6, or 8-10, characterized in that, The LBT type includes at least one of the following: LBT type 2, LBT type 3, and LBT type 4, wherein the competition window size of LBT type 3 and LBT type 4 is a target value; the target value is an integer greater than or equal to 0 and less than or equal to 3.

12. The method of claim 1-3, 5-6, or 8-10, wherein, The method further includes: The terminal receives second information sent by the network-side device, which is sent by the network-side device after it has not received the receiving end assistance information; the second information is used to trigger the terminal to send receiving end assistance information, which is sent by the terminal after it has successfully performed LBT.

13. The method of claim 1-3, 5-6, or 8-10, wherein, Also includes: If the receiving auxiliary information is not successfully sent, the terminal will not perform PDSCH detection.

14. The method of claim 1-3, 5-6, or 8-10, wherein, After the terminal sends receiving auxiliary information based on the first information, it further includes: The terminal receives downlink channels or signals sent by the network side.

15. The method of claim 1-3, 5-6, or 8-10, wherein, The first information also includes: LBT type; Alternatively, the LBT type may be transmitted via Radio Resource Control (RRC) signaling or as agreed upon by the protocol.

16. A method for transmitting a donor assistance information, the method comprising: include: The network-side device sends the first information to the terminal; The first information includes: triggering information of the sounding reference signal (SRS), triggering information of the physical uplink control channel (PUCCH), or scheduling information of the physical uplink shared channel (PUSCH); The network-side device receives receiving assistance information sent by the terminal. The receiving assistance information is sent by the terminal based on the first information after the terminal successfully performs LBT. The receiving assistance information includes: SRS, PUCCH, or PUSCH. When the receiving-end auxiliary information includes the SRS, the triggering information of the SRS is indicated by at least one of the following in the downlink control information (DCI): the probe reference signal SRS request field, the time domain resource allocation (TDRA) field, the frequency domain resource allocation (FDRA) field, the uplink shared channel (UL-SCH) indication field, and the first indication field. When the receiving-end auxiliary information includes the PUCCH, the triggering information of the PUCCH is indicated by at least one of the following in the downlink control information (DCI): the sounding reference signal (SRS) request field, the time domain resource allocation (TDRA) field, the frequency domain resource allocation (FDRA) field, and the second indication field. When the receiving end auxiliary information includes the PUSCH, the scheduling information of the PUSCH includes at least one of the following: LBT type, time domain length of the PUSCH; the time domain length of the PUSCH is a preset length. The first or second indication field is used to indicate whether the physical downlink shared channel (PDSCH) scheduled by the DCI is detected.

17. The method of claim 16, wherein the transmission of the information is triggered by a request from the UE. When the receiving-end auxiliary information includes the SRS. The SRS request field in the uplink allocation DCI is set to a first preset value, and the uplink shared channel UL-SCH indication field is set to a second preset value; or, In the downlink allocation DCI, the SRS request field takes the first preset value, the time domain resource allocation TDRA field takes an invalid value, and the frequency domain resource allocation FDRA field takes a valid value; or, In the downlink allocation DCI, the first indication field takes the value of the third preset value, the SRS request field takes the value of the first preset value, and the FDRA field takes the value of the valid value.

18. The method of claim 17, wherein the transmission of the information is triggered by a request from the UE. The method further includes: The first indication field is set to a fourth preset value, the SRS request field is set to a first preset value, and the FDRA field is set to a valid value. The network-side device sends the Physical Downlink Shared Channel (PDSCH) to the terminal.

19. The method for transmitting receiving auxiliary information according to claim 17 or 18, The first preset value is not all zero, and the second preset value is zero.

20. The method of claim 16, wherein the transmission of the information is triggered by a request from the remote terminal. When the receiver auxiliary information includes the PUCCH. In the downlink allocation DCI, the TDRA field value is invalid, while the FDRA field value is valid; or, In the downlink allocation DCI, the value of the second indicator field is the third preset value, and the value of the FDRA field is a valid value.

21. The method of claim 20, wherein the transmission of the information is triggered by a request from the UE. The method further includes: The second indication field takes the value of the fourth preset value, and the FDRA field takes the value of a valid value. The network-side device sends the Physical Downlink Shared Channel (PDSCH) to the terminal.

22. The method for transmitting receiving auxiliary information according to claim 20 or 21, characterized in that, The SRS request field in the downlink allocation DCI is set to all zeros.

23. The method of claim 16, wherein the transmission of the information is triggered by a request from the remote terminal. The first information also includes: LBT type; The LBT type indicated in the DCI is a preset type, and the receiver auxiliary information is PUSCH.

24. The method for transmitting receiving auxiliary information according to claim 23, characterized in that, The preset length is either one symbol length or two symbol lengths.

25. The method for transmitting receiving auxiliary information according to claim 24, characterized in that, The preset type is LBT type 2, LBT type 3 or LBT type 4, wherein the competition window size of LBT type 3 and LBT type 4 is a target value; the target value is an integer greater than or equal to 0 and less than or equal to 3.

26. The method for transmitting receiving auxiliary information according to any one of claims 16-18, 20, 21 or 23-25, characterized in that, The LBT type includes at least one of the following: LBT type 2, LBT type 3, and LBT type 4, wherein the competition window size of LBT type 3 and LBT type 4 is a target value; the target value is an integer greater than or equal to 0 and less than or equal to 3.

27. The method of claim 16-18, 20, 21, or 23-25, wherein, The method further includes: If the network-side device does not receive the receiving-end assistance information, the network-side device sends a second message to the terminal; the second message is used to trigger the terminal to send receiving-end assistance information, which is sent after the terminal successfully performs LBT.

28. The method of claim 16-18, 20, 21, or 23-25, wherein, After receiving the receiving auxiliary information sent by the terminal, the network-side device further includes: The network-side device sends downlink channels or signals to the terminal.

29. The method of claim 16-18, 20, 21, or 23-25, wherein, The first information also includes: LBT type; Alternatively, the LBT type may be transmitted via Radio Resource Control (RRC) signaling or as agreed upon by the protocol.

30. A device for transmitting a donor assistance information, the device comprising: include: The receiving module is used to receive the first information sent by the network-side device; The first information includes: triggering information of the sounding reference signal (SRS), triggering information of the physical uplink control channel (PUCCH), or scheduling information of the physical uplink shared channel (PUSCH); The sending module is used to send receiving assistance information to the network-side device according to the first information after the terminal successfully performs LBT; wherein the receiving assistance information includes: SRS, PUCCH or PUSCH; When the receiving-end auxiliary information includes the SRS, the triggering information of the SRS is indicated by at least one of the following in the downlink control information (DCI): the probe reference signal SRS request field, the time domain resource allocation (TDRA) field, the frequency domain resource allocation (FDRA) field, the uplink shared channel (UL-SCH) indication field, and the first indication field. When the receiving-end auxiliary information includes the PUCCH, the triggering information of the PUCCH is indicated by at least one of the following in the downlink control information (DCI): the sounding reference signal (SRS) request field, the time domain resource allocation (TDRA) field, the frequency domain resource allocation (FDRA) field, and the second indication field. When the receiving end auxiliary information includes the PUSCH, the scheduling information of the PUSCH includes at least one of the following: LBT type, time domain length of the PUSCH; the time domain length of the PUSCH is a preset length. The first or second indication field is used to indicate whether the physical downlink shared channel (PDSCH) scheduled by the DCI is detected.

31. A device for transmitting a donor assistance information, the device comprising: include: The sending module is used to send the first information to the terminal; The first information includes: triggering information of the sounding reference signal (SRS), triggering information of the physical uplink control channel (PUCCH), or scheduling information of the physical uplink shared channel (PUSCH); A receiving module is configured to receive receiving assistance information sent by the terminal, wherein the receiving assistance information is sent by the terminal based on the first information after the terminal successfully performs LBT; wherein the receiving assistance information includes SRS, PUCCH or PUSCH; When the receiving-end auxiliary information includes the SRS, the triggering information of the SRS is indicated by at least one of the following in the downlink control information (DCI): the probe reference signal SRS request field, the time domain resource allocation (TDRA) field, the frequency domain resource allocation (FDRA) field, the uplink shared channel (UL-SCH) indication field, and the first indication field. When the receiving-end auxiliary information includes the PUCCH, the triggering information of the PUCCH is indicated by at least one of the following in the downlink control information (DCI): the sounding reference signal (SRS) request field, the time domain resource allocation (TDRA) field, the frequency domain resource allocation (FDRA) field, and the second indication field. When the receiving end auxiliary information includes the PUSCH, the scheduling information of the PUSCH includes at least one of the following: LBT type, time domain length of the PUSCH; the time domain length of the PUSCH is a preset length. The first or second indication field is used to indicate whether the physical downlink shared channel (PDSCH) scheduled by the DCI is detected.

32. A terminal, characterized by It includes a processor, a memory, and a program or instructions stored in the memory and executable on the processor, wherein the program or instructions, when executed by the processor, implement the steps of the method for transmitting receiving auxiliary information as described in any one of claims 1 to 15.

33. A network-side device, comprising: It includes a processor, a memory, and a program or instructions stored in the memory and executable on the processor, wherein the program or instructions, when executed by the processor, implement the steps of the method for transmitting receiving auxiliary information as described in any one of claims 16 to 29.

34. A readable storage medium, characterized by The readable storage medium stores a program or instructions, which, when executed by a processor, implement the method for transmitting receiving auxiliary information as described in any one of claims 1-15, or implement the steps of the method for transmitting receiving auxiliary information as described in any one of claims 16-29.

Images