CN115884383A

CN115884383A - Method and device for transmitting auxiliary information of receiving end, terminal and network side equipment

Info

Publication number: CN115884383A
Application number: CN202111146548.3A
Authority: CN
Inventors: 姜蕾; 李�根
Original assignee: Vivo Software Technology Co Ltd
Current assignee: Vivo Software Technology Co Ltd
Priority date: 2021-09-28
Filing date: 2021-09-28
Publication date: 2023-03-31
Also published as: WO2023051540A1

Abstract

The application discloses a method, a device, a terminal and a network side device for transmitting auxiliary information of a receiving end, belonging to the technical field of communication, wherein the method for transmitting the auxiliary information of the receiving end comprises the following steps: a terminal receives first information sent by network side equipment; the first information includes at least one of: the method comprises the following steps of (1) LBT type, sounding reference signal SRS triggering information, physical uplink control channel PUCCH triggering information and physical uplink shared channel PUSCH scheduling information; after the terminal successfully executes listen before talk LBT, the terminal sends receiving end auxiliary information to the network side equipment according to the first information; wherein the receiving end auxiliary information comprises at least one of: SRS, PUCCH, or PUSCH.

Description

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

Technical Field

The application belongs to the technical field of communication, and particularly relates to a method, a device, a terminal and a network side device for transmitting auxiliary information of a receiving end.

Background

In future communication systems, a shared spectrum such as an unlicensed band (unlicensed band) may be used as a supplement to a licensed band (licensed band) to help an operator expand services. In order to maintain compliance with NR deployment and maximize NR-based unlicensed access as much as possible, unlicensed frequency bands may operate in the 5GHz,37ghz, and 60GHz bands. Since the unlicensed frequency band is shared by multiple Radio Access Technologies (RATs), such as wireless communication technologies (Wi-Fi), radar, long Term Evolution licensed Assisted Access (LTE-LAA), and the like, in some countries or regions, the unlicensed frequency band must meet corresponding rules when used to ensure that all devices can fairly use the resource, such as Listen Before Talk (LBT), maximum Channel Occupancy Time (MCOT), and the like. When a transmission node needs to send information and needs to perform LBT first, power Detection (ED) is performed on surrounding nodes, and when the detected power is lower than a threshold, a channel is considered to be empty (idle), and the transmission node can send the information. Otherwise, the channel is considered to be busy, and the transmitting node cannot transmit. The transmission node may be a base station, a User Equipment (UE), a Wi-Fi Access Point (AP), or the like. After the transmission node starts transmission, the Channel Occupancy Time (COT) cannot exceed the MCOT.

As shown in fig. 1, gNB1 performs LBT before sending data, and senses that the channel is empty, so that gNB1 sends data to UE1, and UE1 receives data. At this time, UE2 has data to send, and performs LBT, because gNB1 is far away, UE2 detects that the channel is empty, and starts sending data. However, since a Line Of Sight (LOS) channel exists between gNB2 and gNB1, gNB2 can receive information transmitted by gNB1, and at this time, gNB2 may be interfered when receiving data Of UE 2. The gbb 1 is a hidden node of the gbb 2. In order To further reduce the interference of the hidden node at the receiving end, a handshake mechanism of transmission Request/transmission acknowledgement (Request-To-Send/Clear-To-Send, RTS/CTS) is introduced. The source node sends RTS before data transmission, and the RTS carries a Network Allocation Vector (NAV) value and an address of a destination node, and indicates how long the node needs to occupy a channel. All nodes receiving the RTS do not attempt data transmission within the NAV time. After receiving RTS, the destination node replies a CTS, wherein the CTS carries a NAV value and the address of the source node. All nodes receiving the CTS except the source node and the destination node do not attempt transmission within the NAV time, thus avoiding the hidden node problem around the destination node.

The Information fed back by the receiving end, such as the CTS mentioned above, may be called receiving end auxiliary Information (Receiver Assistance Information). In the 3GPP communication standard, a similar mechanism can be adopted to assist the base station side in downlink transmission. The base station triggers the terminal to send the auxiliary information of the receiving end, the terminal sends the auxiliary information of the receiving end to the base station under the condition that the channel is monitored to be empty after receiving the triggering information, and the base station can carry out downlink transmission to the terminal after receiving the auxiliary information of the receiving end sent by the terminal side. The receiving side auxiliary information means that there is no interfering hidden node on the terminal side. Specifically, how to send the receiving end auxiliary information according to the indication of the base station end is a technical problem that needs to be solved urgently by those skilled in the art.

Disclosure of Invention

The embodiment of the application provides a method, a device, a terminal and a network side device for transmitting auxiliary information of a receiving end, and solves the technical problem of how to transmit the auxiliary information of the receiving end according to the indication of a base station end.

In a first aspect, a method for transmitting auxiliary information of a receiving end is provided, which is applied to a terminal, and includes:

a terminal receives first information sent by network side equipment; the first information includes at least one of: listen Before Talk (LBT) type, sounding Reference Signal (SRS) triggering information, physical Uplink Control Channel (PUCCH) triggering information and Physical Uplink Shared Channel (PUSCH) scheduling information;

after the terminal successfully executes the LBT, the terminal sends receiving end auxiliary information to the network side equipment according to the first information; wherein the receiving end auxiliary information comprises at least one of: SRS, PUCCH, or PUSCH.

In a second aspect, a method for transmitting auxiliary information at a receiving end is provided, and is applied to a network side device, and the method includes:

the network side equipment sends first information to the terminal; the first information includes at least one of: listen Before Talk (LBT) type, sounding Reference Signal (SRS) triggering information, physical Uplink Control Channel (PUCCH) triggering information and Physical Uplink Shared Channel (PUSCH) scheduling information;

the network side equipment receives receiving end auxiliary information sent by the terminal, wherein the receiving end auxiliary information is sent by the terminal according to the first information after the terminal successfully executes LBT; wherein the receiving side auxiliary information includes at least one of: SRS, PUCCH, or PUSCH.

In a third aspect, an apparatus for transmitting auxiliary information at a receiving end is provided, including:

the receiving module is used for receiving first information sent by network side equipment; the first information includes at least one of: listen Before Talk (LBT) type, sounding Reference Signal (SRS) triggering information, physical Uplink Control Channel (PUCCH) triggering information and Physical Uplink Shared Channel (PUSCH) scheduling information;

a sending module, configured to send, to the network side device, receiving end auxiliary information according to the first information after the terminal successfully performs LBT; wherein the receiving end auxiliary information comprises at least one of: SRS, PUCCH, or PUSCH.

In a fourth aspect, an apparatus for transmitting auxiliary information at a receiving end is provided, including:

the sending module is used for sending first information to the terminal; the first information includes at least one of: listen Before Talk (LBT) type, sounding Reference Signal (SRS) triggering information, physical Uplink Control Channel (PUCCH) triggering information and Physical Uplink Shared Channel (PUSCH) scheduling information;

a receiving module, configured to receive receiving-side auxiliary information sent by the terminal, where the receiving-side auxiliary information is sent by the terminal according to the first information after the terminal successfully performs LBT; wherein the receiving end auxiliary information comprises at least one of: SRS, PUCCH, or PUSCH.

In a fifth aspect, there is provided a terminal comprising a processor, a memory, and a program or instructions stored on the memory and executable on the processor, which when executed by the processor, performs the steps of the method according to the first aspect.

The sixth aspect provides a terminal, which includes a processor and a communication interface, where the communication interface is used to receive first information sent by a network-side device; the first information includes at least one of: the method comprises the following steps of (1) LBT type, sounding reference signal SRS triggering information, physical uplink control channel PUCCH triggering information and physical uplink shared channel PUSCH scheduling information; after the successful execution of Listen Before Talk (LBT), sending receiving end auxiliary information to the network side equipment according to the first information; wherein the receiving side auxiliary information includes at least one of: SRS, PUCCH, or PUSCH; the processor is configured to perform listen before talk, LBT.

In a seventh aspect, a network-side device is provided, which includes a processor, a memory, and a program or an instruction stored on the memory and executable on the processor, and when executed by the processor, the program or the instruction implements the steps of the method according to the second aspect.

The eighth aspect provides a network side device, which includes a processor and a communication interface, where the communication interface is used to send first information to a terminal; the first information includes at least one of: the method comprises the steps of determining the LBT type, the triggering information of a Sounding Reference Signal (SRS), the triggering information of a Physical Uplink Control Channel (PUCCH) and the scheduling information of a Physical Uplink Shared Channel (PUSCH); the communication interface is further configured to receive terminating auxiliary information sent by the terminal, where the terminating auxiliary information is sent by the terminal according to the first information after the terminal successfully performs listen before talk LBT; wherein the receiving end auxiliary information comprises at least one of: SRS, PUCCH, or PUSCH.

In a ninth aspect, there is provided a readable storage medium having stored thereon a program or instructions which, when executed by a processor, carries out the steps of the method of the first aspect or carries out the steps of the method of the second aspect.

In a tenth aspect, a chip is provided, the chip comprising a processor and a communication interface, the communication interface being coupled to the processor, the processor being configured to execute a program or instructions to implement the method according to the first aspect, or to implement the method according to the second aspect.

In an eleventh aspect, a computer program/program product is provided, which is stored in a non-transitory storage medium and which is executed by at least one processor to implement the steps of the method for transmitting terminating auxiliary information according to the first or second aspect.

In the embodiment of the application, a terminal receives first information sent by network side equipment; the first information is used for triggering the terminal to send the receiving terminal auxiliary information, and the first information comprises at least one of the following items: the method comprises the following steps of (1) LBT type, sounding reference signal SRS triggering information, physical uplink control channel PUCCH triggering information and physical uplink shared channel PUSCH scheduling information; further, after the terminal successfully performs listen before talk LBT, the terminal sends receiving-end auxiliary information to the network-side device according to the indication of the first information of the network-side device, where the receiving-end auxiliary information includes at least one of the following: after receiving the receiving end auxiliary information, the network side equipment can determine that no hidden node exists around the terminal, and at this time, downlink information is sent to the terminal and cannot be influenced by the hidden node.

Drawings

FIG. 1 is a diagram of an application scenario according to an embodiment of the present application;

fig. 2 is a block diagram of a wireless communication system to which an embodiment of the present application is applicable;

fig. 3 is a flowchart illustrating a method for transmitting auxiliary information of a receiving end according to an embodiment of the present disclosure;

fig. 4 is an interaction flow diagram of a transmission method of receiving side auxiliary information according to an embodiment of the present application;

fig. 5 is a second flowchart illustrating a method for transmitting auxiliary information of a receiving end according to an embodiment of the present application;

fig. 6 is a schematic structural diagram of a transmission apparatus for receiving side auxiliary information according to an embodiment of the present application;

fig. 7 is a second schematic structural diagram of a transmission apparatus for auxiliary information at a receiving end according to an embodiment of the present application;

fig. 8 is a schematic structural diagram of a communication device provided in an embodiment of the present application;

fig. 9 is a schematic hardware structure diagram of a terminal provided in an embodiment of the present application;

fig. 10 is a schematic structural diagram of a network device according to an embodiment of the present application.

Detailed Description

The technical solutions in the embodiments of the present application will be described below clearly with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are some, but not all, embodiments of the present application. All other embodiments that can be derived from the embodiments given herein by a person of ordinary skill in the art are intended to be within the scope of the present disclosure.

The terms first, second and the like in the description and in the claims of the present application are used for distinguishing between similar elements and not necessarily for describing a particular sequential or chronological order. It is to be understood that the terms so used are interchangeable under appropriate circumstances such that the embodiments of the application are capable of operation in other sequences than those illustrated or otherwise described herein, and that the terms "first" and "second" used herein generally refer to a class and do not limit the number of objects, for example, a first object can be one or more. In addition, "and/or" in the specification and the claims means at least one of connected objects, and a character "/" generally means that a preceding and succeeding related objects are in an "or" relationship.

It is noted that the techniques described in the embodiments of the present application are not limited to Long Term Evolution (LTE)/LTE Evolution (LTE-Advanced) systems, but may 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 (Single-carrier Frequency-Division Multiple Access (sc)), or Code Division Multiple Access (CDMA-a) systemsMultiple Access, SC-FDMA), and other systems. The terms "system" and "network" in the embodiments of the present application are often used interchangeably, and the described techniques can be used for both the above-mentioned systems and radio technologies, as well as for other systems and radio technologies. The following description describes a New Radio (NR) system for purposes of example, and NR terminology is used in much of the description below, but the techniques may also be applied to applications other than NR system applications, such as generation 6 (6) ^th Generation, 6G) communication system.

Fig. 2 shows a block diagram of a wireless communication system to which an embodiment of the present application is applicable. The wireless communication system includes a terminal 11 and a network-side device 12. Wherein, the terminal 11 may also be referred to as a terminal Device or a User Equipment (UE), the terminal 11 may be a Mobile phone, a Tablet Personal Computer (Tablet Personal Computer), a Laptop Computer (Laptop Computer) or a notebook Computer, a Personal Digital Assistant (PDA), a palm Computer, a netbook, a super Mobile Personal Computer (UMPC), a Mobile Internet Device (MID), an Augmented Reality (AR)/Virtual Reality (VR) Device, a robot, a Wearable Device (Wearable Device), a vehicle mounted Device (VUE), a pedestrian terminal (PUE), a smart home (a Device with wireless communication function, such as a refrigerator, a television, a washing machine, or furniture, etc.), and the Wearable Device includes: smart watch, smart bracelet, smart earphone, smart glasses, smart jewelry (smart bracelet, smart ring, smart necklace, smart anklet, etc.), smart wristband, smart garment, game console, etc. It should be noted that the embodiment of the present application does not limit the specific type of the terminal 11. The network-side device 12 may be a Base Station or a core network, where the Base Station may be referred to as a node B, an evolved node B, an access Point, a Base Transceiver Station (BTS), a radio Base Station, a radio Transceiver, a Basic Service Set (BSS), an Extended Service Set (ESS), a node B, an evolved node B (eNB), a home node B, a WLAN access Point, a WiFi node, a Transmit Receiving Point (TRP), or some other suitable terminology in the field, as long as the same technical effect is achieved, the Base Station is not limited to a specific technical vocabulary, and it should be noted that, in the embodiment of the present application, only the Base Station in the NR system is taken as an example, but a specific type of the Base Station is not limited.

The following describes in detail a transmission method of receiving side auxiliary information provided in the embodiments of the present application through some embodiments and application scenarios thereof with reference to the accompanying drawings.

Fig. 3 is a flowchart illustrating a method for transmitting auxiliary information of a receiving end according to an embodiment of the present disclosure. As shown in fig. 3, the method for transmitting auxiliary information at a receiving end according to this embodiment includes:

step 101, a terminal receives first information sent by network side equipment; the first information includes at least one of: the method comprises the following steps of (1) LBT type, sounding reference signal SRS triggering information, physical uplink control channel PUCCH triggering information and physical uplink shared channel PUSCH scheduling information;

specifically, the network side device sends first information to the terminal before performing downlink data transmission, the terminal receives the first information sent by the network side device, the first information is used for triggering the terminal to send auxiliary information of the receiving end, and the first information may include at least one of the following: an LBT type, trigger Information of a Sounding Reference Signal (SRS), trigger Information of a Physical Uplink Control Channel (PUCCH), scheduling Information of a Physical Uplink Shared Channel (PUSCH), where the LBT type may be predefined by a protocol or configured by a network side device or indicated by signaling, for example, indicated by Downlink Control Information (DCI) signaling.

Optionally, the trigger information of SRS, PUCCH, PUSCH may be indicated by signaling, for example, DCI signaling.

Alternatively, when the first information does not include an LBT type, the LBT type may be signaled through Radio Resource Control (RRC) signaling or agreed by a protocol.

Alternatively, the type of LBT (Category) may be divided into Category1, category 2, category3 and Category4.Category1 LBT is LBT not done by the sending node, i.e. no LBT or immediate transmission. The Category 2LBT is a one-shot LBT, that is, the node performs LBT once before transmission, and transmits if the channel is empty, and does not transmit if the channel is busy. Category3 and Category 4LBT are backoff (back-off) based channel sensing mechanisms, and when a transmission node senses that a channel is busy, the transmission node performs backoff and continues to sense the channel until sensing that the channel is empty. Wherein, the competition Window size (competition Window size) of the Category 3LBT is fixed; the contention Window (contention Window size) of Category 4LBT is variable. In addition, category 4LBT may also be called Type1 channel access mechanism, and Category 2LBT may also be called Type 2 channel access mechanism.

And 102, after the terminal successfully executes the LBT, the terminal sends receiving end auxiliary information to the network side equipment according to the first information.

Wherein, performing LBT successfully refers to hearing that the channel is idle.

Optionally, the receiving side auxiliary information includes at least one of: SRS, PUCCH, or PUSCH.

Specifically, the terminal needs to perform LBT before sending the receiving-end auxiliary information, and sends the receiving-end auxiliary information after LBT is successful (i.e., channel idle is sensed), where specific content of the receiving-end auxiliary information needs to be determined according to the indication of the first information.

Optionally, it is worth pointing out that, in the process that the terminal sends the receiving-end auxiliary information to the network-side device according to the first information, the terminal does not receive the receiving-end auxiliary information.

Optionally, the terminal may explicitly or implicitly indicate the channel condition or LBT result of the terminal side to the network side device through SRS, PUCCH, or PUSCH, and hide information such as nodes. For example, after the network side device receives the receiving side assistance information, it means that the LBT of the terminal is successful, or there is no hidden node around the terminal, or the terminal side channel is empty.

In the method of the embodiment, a terminal receives first information sent by network side equipment; the first information is used for triggering the terminal to send the receiving terminal auxiliary information, and the first information comprises at least one of the following items: the method comprises the following steps of (1) LBT type, sounding reference signal SRS triggering information, physical uplink control channel PUCCH triggering information and physical uplink shared channel PUSCH scheduling information; further, after the terminal successfully performs listen before talk LBT, the terminal sends receiving end auxiliary information to the network side device according to the indication of the first information of the network side device, and after receiving the receiving end auxiliary information, the network side device can determine that no hidden node exists around the terminal, and at this time, sends downlink information to the terminal, which will not be affected by the hidden node.

In an embodiment, after the terminal sends the receiving-end auxiliary information according to the first information, the method further includes:

and the terminal receives a downlink channel or signal sent by the network side.

Specifically, when the network side device receives the SRS, the PUCCH, or the PUSCH of the specific time domain length, the network side device transmits a Downlink Channel/signal such as a Group Common (GC) -Physical Downlink Control Channel (PDCCH), a PDSCH, a broadcast signal, and the like to the terminal.

In the foregoing embodiment, after receiving the receiving-end auxiliary information, the network-side device may determine that there is no hidden node around the terminal, may send a downlink channel or signal to the terminal, and at this time, send downlink information to the terminal, which will not be affected by the hidden node.

In an embodiment, the method further comprises:

when the receiving side assistance information is not successfully transmitted, the terminal does not perform PDSCH detection.

Specifically, when the reception side assistance information is not successfully transmitted, the terminal does not expect to receive a Physical Downlink Shared Channel (PDSCH) and does not perform PDSCH detection.

In the above embodiment, when the receiving side assistance information is not successfully transmitted, the terminal does not perform PDSCH detection, and power consumption of the terminal can be reduced.

In an embodiment, when the receiving-end auxiliary information includes an SRS, the SRS trigger information indicates at least one of a sounding reference signal SRS request field, a time domain resource allocation TDRA, a frequency domain resource allocation FDRA field, an uplink shared channel UL-SCH indication field, and a first indication field in a downlink control information DCI;

under the condition that the receiving end auxiliary information comprises the PUCCH, the triggering information of the PUCCH indicates at least one of a Sounding Reference Signal (SRS) request domain, a Time Domain Resource Allocation (TDRA), a Frequency Domain Resource Allocation (FDRA) domain and a second indication domain in Downlink Control Information (DCI);

in a case that the receiving side assistance information includes the PUSCH, scheduling information of the PUSCH includes at least one of: LBT type, time domain length of PUSCH;

wherein the first indication field or the second indication field is used for indicating whether to detect the physical downlink shared channel PDSCH scheduled by the DCI.

Specifically, for the first indication field and the second indication field, only the first indication field, only the second indication field, or both the first indication field and the second indication field may be included in the DCI. The first indication field and the second indication field may be the same or different indication fields in DCI, and optionally, if the first indication field and the second indication field are the same field, the indication may be performed by different fields in the field, and optionally, the DCI is a downlink allocation DCI (DL assignment DCI).

When the auxiliary information at the receiving end includes the SRS, the trigger information of the SRS indicates at least one of a SRS request field, a Time Domain Resource Allocation (TDRA), a Frequency Domain Resource allocation (TDRA) field, an Uplink Shared Channel (UL-SCH) indication field, and a first indication field through a sounding reference signal SRS request field in the DCI;

and under the condition that the receiving end auxiliary information comprises the PUCCH, the triggering information of the PUCCH indicates at least one of a Sounding Reference Signal (SRS) request domain, a Time Domain Resource Allocation (TDRA), a Frequency Domain Resource Allocation (FDRA) domain and a second indication domain in Downlink Control Information (DCI).

Optionally, the first indication field and the second indication field may be newly added fields in DCI, or partial fields in an original field.

In the case that the receiving side assistance information includes a PUSCH, the scheduling information of the PUSCH includes at least one of: LBT type, time domain length of PUSCH.

Optionally, the scheduling information of the PUSCH may be carried by the uplink allocation DCI.

When the network side device instructs the terminal to transmit the SRS, the PUCCH, or the PUSCH with the specific time domain length by using the specific type LBT, if the network side device does not detect the corresponding signal or channel, the network side device may continue to instruct the terminal to transmit the SRS, the PUCCH, or the PUSCH with the specific time domain length by using the specific type LBT until the corresponding signal or channel is received. Before not receiving SRS, PUCCH or PUSCH with specific time domain length, the network side equipment does not send PDSCH to the terminal, and the terminal does not need to detect PDSCH.

For example, when the network side device instructs the terminal to transmit the SRS, the PUCCH or the PUSCH with the specific time domain length by using type 2LBT, the terminal does not transmit the SRS, the PUCCH or the PUSCH with the specific time domain length when it senses that the channel is busy. If the network side device does not detect the corresponding signal or channel, the network side device may continue to instruct the terminal to transmit the SRS, the PUCCH, or the PUSCH with the specific time domain length by using type 2LBT until the corresponding signal or channel is received.

Optionally, the specific type of LBT comprises at least one of: type 2LBT, type 3LBT, type 4LBT, wherein the contention window size for type 3 and type 4LBT is a target value; optionally, the value range of the target value is an integer greater than or equal to 0 and less than or equal to 3.

Optionally, the specific time domain length is 1 symbol length or 2 symbol lengths.

In the above embodiment, the terminal sends different receiving end auxiliary information according to different instructions of the network side device, and after receiving the receiving end auxiliary information, the network side device may determine that there is no hidden node around the terminal, and at this time, sends downlink information to the terminal, which will not be affected by the hidden node.

In an embodiment, when the receiving side assistance information includes the SRS, the following situations exist as the indication manner of the first information:

one of the situations is:

the value of the SRS request domain in the uplink allocation DCI is a first preset value, and the value of the uplink shared channel UL-SCH indication domain is a second preset value.

Optionally, the network side device triggers the terminal to transmit the SRS through DCI format 0 _1or DCI format 0 _2.

Specifically, the SRS request field (request field) takes a value of a first preset value. And the UL-SCH indication (indicator field) takes the value as a second preset value. And after receiving the instruction of the first information, the terminal only transmits the SRS and does not transmit the PUSCH if the LBT is successful. If the terminal does not successfully transmit the SRS, the terminal does not expect to receive the PDSCH and does not detect the PDSCH.

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

In another case:

the value of the SRS request domain in the downlink allocation DCI is a first preset value, the value of the time domain resource allocation TDRA domain is an invalid value, and the value of the frequency domain resource allocation FDRA domain is an valid value.

Optionally, the first preset value is non-all-zero.

Specifically, the network side device configures an invalid value (invalid entry) in a TDRA table (table) through RRC. The invalid Value indicates that the scheduling is invalid, and the time domain resource Length indicated by the invalid Value may be zero or a Start And Length Indicator Value (SLIV) Value is an invalid Value.

Optionally, the network side device triggers the terminal to transmit the SRS through DCI format 1_1 or DCI format 1 _u2.

The SRS request domain value is non-all-zero, the TDRA domain indicates an invalid value, and the FDRA domain indicates an valid value. And when the terminal receives the DCI instruction, not detecting the PDSCH scheduled by the DCI, and ignoring invalid PDSCH scheduling.

When LBT succeeds, the terminal only transmits SRS and does not transmit PUCCH. If the terminal does not successfully transmit the SRS, the UE does not expect to receive the PDSCH and does not perform PDSCH detection.

Optionally, the terminal ignores a PUCCH Resource Indicator (PRI) and a PDSCH-to-HARQ feedback timing (PDSCH-to-HARQ _ feedback timing), where the PDSCH-to-HARQ _ feedback timing field is used to indicate how long HARQ-ACK information needs to be sent after the PDSCH completes data transmission.

In another case:

and the value of the first indication domain in the downlink allocation DCI is a third preset value, the value of the SRS request domain is the first preset value, and the value of the FDRA domain is an effective value.

Optionally, the first preset value is not all zero.

Optionally, a first indication field may be added to DCI format 1 or DCI format 1_2, or an original field may be multiplexed, and a certain field existing in the DCI is used as the first indication field, where the length of the first indication field is at least one bit; or at least one bit may be added to the original field to indicate whether to detect the DCI scheduled PDSCH.

Specifically, when the first indication field is 1 bit and takes a value as a third preset value, for example, 1, the value of the srs request field is non-all-zero, and the FDRA field indicates an effective value, the terminal does not detect the PDSCH scheduled by the DCI, and does not perform PUCCH transmission, that is, ignores the scheduling of the PDSCH and the PUCCH. And the terminal only transmits the SRS when the LBT is successful according to the DCI indication. If the terminal does not successfully transmit the SRS, the terminal does not expect to receive the PDSCH.

Optionally, the terminal ignores the PRI and the PDSCH-to-HARQ _ feedback timing, where the PDSCH-to-HARQ _ feedback timing field is used to indicate how long the PDSCH needs to transmit HARQ-ACK information after completing data transmission.

In the above embodiment, the terminal sends the SRS as the receiving side auxiliary information according to the instruction of the network side device, and after receiving the receiving side auxiliary information, the network side device may determine that there is no hidden node around the terminal, and at this time, the terminal sends the downlink information to the terminal without being affected by the hidden node.

Optionally, the method further comprises:

and the value of the first indication domain is a fourth preset value, the value of the SRS request domain is the first preset value, the value of the FDRA domain is an effective value, and the terminal receives the Physical Downlink Shared Channel (PDSCH) scheduled by the network side equipment.

Optionally, the first preset value is not all zero.

Specifically, when the first indication field is 1 bit and takes a value as a fourth preset value, for example, 0, the SRS request field takes a value of non-all-zero and the FDRA field indicates an effective value, the terminal receives the PDSCH according to the scheduling and transmits the SRS and the PUCCH after the LBT succeeds.

In the above embodiment, the terminal receives the PDSCH normally scheduled by the network side device according to the instruction of the network side device, and transmits the SRS and the PUCCH.

In an embodiment, when the receiving side auxiliary information includes a PUCCH, the following situations exist as the indication manner of the first information:

one of the situations is:

the value of the TDRA domain in the downlink allocation DCI is an invalid value, and the value of the FDRA domain is an effective value.

Specifically, the network side device configures an invalid value in the TDRA table through RRC. The invalid value indicates that the scheduling is invalid, and the time domain resource length indicated by the invalid value may be zero or the SLIV is an invalid value.

Optionally, the network side device triggers the terminal to transmit the PUCCH through DCI format 1_1 or DCI format 1 _u2.

Optionally, a value of the SRS request field in the downlink assignment DCI is different from a value of the SRS request field in the case that the receiving end auxiliary information includes the SRS, and the value of the SRS request field in the downlink assignment DCI may be all zero at this time.

For example, the SRS request field takes all values of zero, the TDRA field indicates invalid entry, and the FDRA field indicates a valid value. And when the terminal receives the DCI indication, ignoring invalid PDSCH scheduling, and when the LBT is successful, the UE sends PUCCH. If the UE does not successfully transmit the PUCCH, the UE does not expect to receive the PDSCH, i.e., does not detect the PDSCH.

In another case:

and the value of the second indication domain in the downlink allocation DCI is a third preset value, and the value of the FDRA domain is an effective value.

Optionally, a second indication field may be added to DCI format 1 or DCI format 1_2, or an original field may be multiplexed, where a certain field existing in the DCI is used as the second indication field, and the length of the second indication field is at least one bit; or at least one bit may be added to the original field to indicate whether to detect the DCI scheduled PDSCH.

Optionally, the SRS request field takes a value of all zeros.

Specifically, when the second indication field is 1 bit and takes a value of a third preset value, for example, 1, the srs request field takes a value of all zeros, and the FDRA indicates a valid value, the terminal ignores the PDSCH scheduling. And the UE transmits the PUCCH when the LBT is successful according to the DCI indication. If the terminal does not successfully transmit the PUCCH, the terminal does not expect to receive the PDSCH.

In the above embodiment, the terminal sends the PUCCH as the receiving-end auxiliary information according to the instruction of the network-side device, and after receiving the receiving-end auxiliary information, the network-side device may determine that there is no hidden node around the terminal, and at this time, sends the downlink information to the terminal without being affected by the hidden node.

Optionally, the method further comprises:

and the value of the second indication domain is a fourth preset value, the value of the FDRA domain is an effective value, and the terminal receives the Physical Downlink Shared Channel (PDSCH) scheduled by the network side equipment.

Optionally, the SRS request field takes all values of zero.

Specifically, the second indication field is 1 bit and takes a value of a fourth preset value, for example, the fourth preset value is 0, the srs request field takes a value of all zero, and the FDRA field indicates an effective value, and then the terminal receives the PDSCH according to the scheduling and transmits the PUCCH after the LBT is successful.

In the above embodiment, the terminal receives the PDSCH normally scheduled by the network device and transmits the PUCCH according to the instruction from the network device.

In an 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 receiving end auxiliary information is the PUSCH.

Specifically, if the terminal receives the DCI indicating the preset type LBT and the PUSCH with the preset length, the terminal performs LBT according to the indication, and if LBT is successful, the terminal transmits the PUSCH. If the terminal has no data to transmit, the terminal generates a Buffer Status Report (BSR) for transmission. If the terminal does not successfully transmit the PUSCH of a certain length, the UE does not expect to receive the PDSCH.

Optionally, the preset length is 1 symbol length or 2 symbol lengths.

Optionally, the preset type is LBT type 2, LBT type 3, or LBT type 4, wherein the size of the contention window of LBT type 3 and LBT type 4 is a target value; the value range of the target value is an integer of 0 or more and 3 or less.

In the above embodiment, the terminal sends the PUSCH as the receiving side auxiliary information according to the instruction of the network side device, and after receiving the receiving side auxiliary information, the network side device may determine that there is no hidden node around the terminal, and at this time, the downlink information is sent to the terminal, and will not be affected by the hidden node.

In an embodiment, the method further comprises:

the terminal receives second information sent by the network side equipment, wherein the second information is sent by the network side equipment after the network side equipment does not receive the auxiliary information of the receiving terminal; the second information is used for triggering the terminal to send receiving end auxiliary information, and the receiving end auxiliary information is sent after the terminal successfully executes LBT. The second information may be the first information that is continuously sent when the network side device does not receive the receiving end auxiliary information.

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

Specifically, the network side device does not receive the receiving end auxiliary information within the preset time length, and sends second information to the terminal, where the second information is used to trigger the terminal to send the receiving end auxiliary information, and the terminal sends the receiving end auxiliary information after the LBT is successfully executed.

The network side device does not receive the receiving end auxiliary information, which may be that the terminal does not transmit the auxiliary information, or the network side device does not receive the auxiliary information after the terminal transmits the auxiliary information due to signal interference or the like.

In the foregoing embodiment, the network side device sends the second information after not receiving the receiving-end auxiliary information, which is used to trigger the terminal to send the receiving-end auxiliary information, and after receiving the receiving-end auxiliary information, the network side device determines that there is no hidden node around the terminal, and at this time, sends the downlink information to the terminal, which will not be affected by the hidden node.

As shown in fig. 4, the method for transmitting auxiliary information at a receiving end according to this embodiment includes:

step 100a, a network side device sends first information to a terminal; the first information is used for triggering the terminal to send the auxiliary information of the receiving end;

step 100b, the terminal executes listen before talk LBT;

102, after the terminal successfully executes listen before talk LBT, sending auxiliary information of a receiving end according to first information;

103a, the network side equipment sends a downlink channel or signal to the terminal after receiving the receiving end auxiliary information;

or, in step 103b, the network side device sends the second information after not receiving the receiving end auxiliary information, so as to trigger the terminal to send the receiving end auxiliary information.

The specific implementation process and technical effects of the method of this embodiment are similar to those of the terminal side method embodiment, and specific reference may be made to the detailed description of the method embodiment, which is not described herein again.

Fig. 5 is a second flowchart illustrating a transmission method of auxiliary information at a receiving end according to an embodiment of the present application. As shown in fig. 5, the method for transmitting auxiliary information at a receiving end provided in this embodiment includes:

step 201, a network side device sends first information to a terminal; the first information includes at least one of: the method comprises the following steps of (1) LBT type, sounding reference signal SRS triggering information, physical uplink control channel PUCCH triggering information and physical uplink shared channel PUSCH scheduling information;

step 202, a network side device receives receiving end auxiliary information sent by a terminal, where the receiving end auxiliary information is sent by the terminal according to a first message after the terminal successfully executes LBT.

Optionally, the receiving side auxiliary information includes at least one of: SRS, PUCCH, or PUSCH;

under the condition that the receiving end auxiliary information comprises the SRS, the triggering information of the SRS indicates at least one item of a sounding reference signal SRS request domain, a time domain resource allocation TDRA, a frequency domain resource allocation FDRA domain, an uplink shared channel UL-SCH indication domain and a first indication domain in downlink control information DCI;

in a case that the receive side auxiliary information includes the PUSCH, scheduling information of the PUSCH includes at least one of: LBT type, time domain length of PUSCH;

wherein the first indication field or the second indication field is used for indicating whether to detect the Physical Downlink Shared Channel (PDSCH) scheduled by the DCI.

Optionally, in case that the terminating assistance information includes the SRS,

the value of an SRS request domain in the uplink allocation DCI is a first preset value, and the value of an uplink shared channel UL-SCH indication domain is a second preset value; or the like, or, alternatively,

the value of an SRS request domain in downlink allocation DCI is a first preset value, the value of a time domain resource allocation TDRA domain is an invalid value, and the value of a frequency domain resource allocation FDRA domain is an effective value; or the like, or a combination thereof,

Optionally, the method further comprises:

and the value of the first indication domain is a fourth preset value, the value of the SRS request domain is the first preset value, the value of the FDRA domain is an effective value, and the terminal receives a Physical Downlink Shared Channel (PDSCH) scheduled by network side equipment.

Optionally, in case that the receiving side assistance information includes the PUCCH,

the value of the TDRA domain in the downlink allocation DCI is an invalid value, and the value of the FDRA domain is an effective value; or the like, or a combination thereof,

Optionally, the method further comprises:

and the value of the second indication domain is a fourth preset value, the value of the FDRA domain is an effective value, and the terminal receives a Physical Downlink Shared Channel (PDSCH) scheduled by the network side equipment.

Optionally, values of the SRS request field in the downlink assignment DCI are all zero.

Optionally, the LBT type indicated in the DCI is a preset type, the time domain length of the PUSCH is a preset length, and the receiving end auxiliary information is the PUSCH.

Optionally, the preset length is 1 symbol length or 2 symbol lengths.

Optionally, the preset type is LBT type 2, LBT type 3, or LBT type 4, where the size of the contention window of LBT type 3 and LBT type 4 is a target value; the value range of the target value is an integer greater than or equal to 0 and less than or equal to 3.

Optionally, the method further comprises:

under the condition that the network side equipment does not receive the receiving end auxiliary information, the network side equipment sends second information to the terminal; the second information is used for triggering the terminal to send receiving end auxiliary information, and the receiving end auxiliary information is sent after the terminal successfully executes LBT.

Optionally, after the network side device receives the terminal side auxiliary information sent by the terminal, the method further includes:

and the network side equipment sends a downlink channel or signal to the terminal.

Optionally, when the first information does not include an LBT type, the LBT type is sent through radio resource control RRC signaling or agreed by a protocol.

Optionally, when the second information does not include an LBT type, the LBT type is sent through radio resource control RRC signaling or agreed by a protocol.

The specific implementation process and technical effects of the method of this embodiment are similar to those of the terminal side method embodiment, and specific reference may be made to detailed descriptions in the terminal side method embodiment, which are not described herein again.

It should be noted that, in the transmission method of the receiving side auxiliary information provided in the embodiment of the present application, the execution main body may be a transmission device of the receiving side auxiliary information, or a processing module in the transmission device of the receiving side auxiliary information, configured to execute the transmission method of the receiving side auxiliary information. In the embodiment of the present application, a method for executing transmission of auxiliary receiving information by a transmission device of auxiliary receiving information is taken as an example, and a transmission device of auxiliary receiving information provided in the embodiment of the present application is described.

Fig. 6 is a schematic structural diagram of a transmission apparatus for auxiliary information at a receiving end according to the present application. As shown in fig. 6, the apparatus 600 for transmitting auxiliary information at a receiving end provided in this embodiment includes:

a receiving module 601, configured to receive first information sent by a network side device; the first information includes at least one of: listen Before Talk (LBT) type, sounding Reference Signal (SRS) triggering information, physical Uplink Control Channel (PUCCH) triggering information and Physical Uplink Shared Channel (PUSCH) scheduling information;

a sending module 602, configured to send, to the network side device, receiving end auxiliary information according to the first information after the terminal successfully performs LBT; wherein the receiving side auxiliary information includes at least one of: SRS, PUCCH or PUSCH.

In the device of the embodiment, a receiving module receives first information sent by network side equipment; the first information is used for triggering the terminal to send the receiving terminal auxiliary information, and the first information comprises at least one of the following items: the method comprises the steps of determining the LBT type, the triggering information of a Sounding Reference Signal (SRS), the triggering information of a Physical Uplink Control Channel (PUCCH) and the scheduling information of a Physical Uplink Shared Channel (PUSCH); further, after the terminal successfully performs listen before talk LBT, the sending module sends receiving-end auxiliary information to the network-side device according to the indication of the first information of the network-side device, where the receiving-end auxiliary information includes at least one of the following: after receiving the receiving end auxiliary information, the network side equipment can determine that no hidden node exists around the terminal, and at the moment, downlink information is sent to the terminal and cannot be influenced by the hidden node.

Optionally, when the receiving-end auxiliary information includes the SRS, the SRS trigger information indicates at least one of a sounding reference signal SRS request field, a time domain resource allocation TDRA, a frequency domain resource allocation FDRA field, an uplink shared channel UL-SCH indication field, and a first indication field in a downlink control information DCI;

optionally, when the receiving end auxiliary information includes the PUCCH, the trigger information of the PUCCH is indicated by at least one of a sounding reference signal SRS request field, a time domain resource allocation TDRA, a frequency domain resource allocation FDRA field, and a second indication field in downlink control information DCI;

in a case that the receiving side assistance information includes the PUSCH, the scheduling information of the PUSCH includes at least one of: LBT type, time domain length of PUSCH;

the value of an SRS request domain in downlink allocation DCI is a first preset value, the value of a time domain resource allocation TDRA domain is an invalid value, and the value of a frequency domain resource allocation FDRA domain is an effective value; or the like, or, alternatively,

Optionally, the receiving module 601 is further configured to:

and the value of the first indication domain is a fourth preset value, the value of the SRS request domain is a first preset value, the value of the FDRA domain is an effective value, and a Physical Downlink Shared Channel (PDSCH) scheduled by the network side equipment is received.

Optionally, in case that the terminating assistance information includes the PUCCH,

Optionally, the receiving module 601 is further configured to:

and the value of the second indication domain is a fourth preset value, and the value of the FDRA domain is an effective value, and the Physical Downlink Shared Channel (PDSCH) scheduled by the network side equipment is received.

Optionally, values of the SRS request field in the downlink allocation DCI are all zero.

Optionally, the preset length is 1 symbol length or 2 symbol lengths.

Optionally, the preset type is LBT type 2, LBT type 3, or LBT type 4, where the contention window size of LBT type 3 and LBT type 4 is a target value; the value range of the target value is an integer greater than or equal to 0 and less than or equal to 3.

Optionally, the LBT type comprises at least one of: LBT type 2, LBT type 3, LBT type 4, wherein the contention window size of LBT type 3 and LBT type 4 is a target value; the value range of the target value is an integer which is greater than or equal to 0 and less than or equal to 3.

Optionally, the receiving module 601 is further configured to:

receiving second information sent by the network side equipment, wherein the second information is sent by the network side equipment after the network side equipment does not receive the receiving end auxiliary information; the second information is used for triggering the terminal to send receiving end auxiliary information, and the receiving end auxiliary information is sent after the terminal successfully executes LBT.

Optionally, the method further comprises:

and the processing module is used for not detecting the PDSCH under the condition that the receiving end auxiliary information is not successfully transmitted.

Optionally, the receiving module 601 is further configured to:

and receiving a downlink channel or signal sent by the network side.

Optionally, when the first information does not include an LBT type, the LBT type is sent through radio resource control, RRC, signaling or agreed by a protocol.

The apparatus of this embodiment may be configured to execute the method of any one of the foregoing terminal side method embodiments, and the specific implementation process and technical effects thereof are similar to those in the terminal side method embodiment, which may specifically refer to the detailed description in the terminal side method embodiment, and are not described herein again.

Fig. 7 is a second schematic structural diagram of a transmission apparatus for auxiliary receiving information according to the present application. As shown in fig. 7, the apparatus 700 for transmitting auxiliary information at a receiving end according to this embodiment includes:

a sending module 701, configured to send first information to a terminal; the first information includes at least one of: listen Before Talk (LBT) type, sounding Reference Signal (SRS) triggering information, physical Uplink Control Channel (PUCCH) triggering information and Physical Uplink Shared Channel (PUSCH) scheduling information;

a receiving module 702, configured to receive receiving-end auxiliary information sent by the terminal, where the receiving-end auxiliary information is sent by the terminal according to the first information after the terminal successfully performs LBT; wherein the receiving end auxiliary information comprises at least one of: SRS, PUCCH, or PUSCH.

Optionally, when the receiving end auxiliary information includes the SRS, the SRS trigger information indicates at least one of a sounding reference signal SRS request field, a time domain resource allocation TDRA, a frequency domain resource allocation FDRA field, an uplink shared channel UL-SCH indication field, and a first indication field in a downlink control information DCI;

the value of an SRS request domain in the uplink allocation DCI is a first preset value, and the value of an uplink shared channel UL-SCH indication domain is a second preset value; or the like, or a combination thereof,

Optionally, the sending module 701 is further configured to:

and the value of the first indication domain is a fourth preset value, the value of the SRS request domain is the first preset value, and the value of the FDRA domain is an effective value, and a Physical Downlink Shared Channel (PDSCH) is sent to the terminal.

the value of the TDRA domain in the downlink allocation DCI is an invalid value, and the value of the FDRA domain is an effective value; or the like, or, alternatively,

Optionally, the sending module 701 is further configured to:

and the value of the second indication domain is a fourth preset value, and the value of the FDRA domain is an effective value, and the PDSCH (physical downlink shared channel) is sent to the terminal.

Optionally, the preset length is 1 symbol length or 2 symbol lengths.

Optionally, the LBT type comprises at least one of: LBT type 2, LBT type 3 and LBT type 4, wherein the size of the contention window of the LBT type 3 and the LBT type 4 is a target value; the value range of the target value is an integer greater than or equal to 0 and less than or equal to 3.

Optionally, the sending module 701 is further configured to:

under the condition that the network side equipment does not receive the receiving end auxiliary information, second information is sent to the terminal; the second information is used for triggering the terminal to send receiving end auxiliary information, and the receiving end auxiliary information is sent after the terminal successfully executes LBT.

Optionally, the sending module 701 is further configured to:

The apparatus of this embodiment may be configured to perform the method of any of the foregoing embodiments of the network-side method, and the specific implementation process and technical effects thereof are similar to those in the embodiments of the network-side method.

The transmission device of the receiving side auxiliary information in the embodiment of the present application may be a device, a device with an operating system, or an electronic device, and may also be a component, an integrated circuit, or a chip in a terminal. The device or the electronic equipment can be a mobile terminal or a non-mobile terminal. For example, the mobile terminal may include, but is not limited to, the above-listed type of terminal 11, and the non-mobile terminal may be a server, a Network Attached Storage (NAS), a Personal Computer (PC), a Television (TV), a teller machine, a kiosk, or the like, and the embodiments of the present application are not limited in particular.

The transmission device for auxiliary information at the receiving end provided in the embodiment of the present application can implement each process implemented in the method embodiments of fig. 3 to fig. 5, and achieve the same technical effect, and is not described here again to avoid repetition.

Optionally, as shown in fig. 8, an embodiment of the present application further provides a communication device 800, which includes a processor 801, a memory 802, and a program or an instruction stored on the memory 802 and executable on the processor 801, for example, when the communication device 800 is a terminal, the program or the instruction is executed by the processor 801 to implement each process of the above-mentioned transmission method for receiving end auxiliary information, and can achieve the same technical effect. When the communication device 800 is a network-side device, the program or the instructions are executed by the processor 801 to implement the processes of the above-mentioned transmission method for the receiving-side auxiliary information, and can achieve the same technical effect, and in order to avoid repetition, the details are not described here again.

The embodiment of the application also provides a terminal, which comprises a processor and a communication interface, wherein the communication interface is used for receiving the first information sent by the network side equipment; the first information includes at least one of: the method comprises the following steps of (1) LBT type, sounding reference signal SRS triggering information, physical uplink control channel PUCCH triggering information and physical uplink shared channel PUSCH scheduling information; after the listen before talk LBT is successfully executed, the terminal sends the receiving end auxiliary information to the network side equipment according to the first information, and the processor is used for executing the listen before talk LBT. The terminal embodiment corresponds to the terminal-side method embodiment, and all implementation processes and implementation manners of the method embodiment can be applied to the terminal embodiment and can achieve the same technical effect. Specifically, fig. 9 is a schematic diagram of a hardware structure of a terminal for implementing the embodiment of the present application.

The terminal 1000 includes, but is not limited to: a radio frequency unit 1001, a network module 1002, an audio output unit 1003, an input unit 1004, a sensor 1005, a display unit 1006, a user input unit 1007, an interface unit 1008, a memory 1009, a processor 1010, and the like.

Those skilled in the art will appreciate that terminal 1000 can further include a power supply (e.g., a battery) for powering the various components, and the power supply can be logically coupled to processor 1010 via a power management system, such that functions of managing charging, discharging, and power consumption are performed via the power management system. The terminal structure shown in fig. 9 does not constitute a limitation of the terminal, and the terminal may include more or less components than those shown, or combine some components, or have a different arrangement of components, and thus will not be described again.

It should be understood that in the embodiment of the present application, the input Unit 1004 may include a Graphics Processing Unit (GPU) 10041 and a microphone 10042, and the Graphics Processing Unit 10041 processes image data of still pictures or videos obtained by an image capturing device (such as a camera) in a video capturing mode or an image capturing mode. The display unit 1006 may include a display panel 10061, and the display panel 10061 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 referred to as a touch screen. The touch panel 10071 may include two parts, a touch detection device and a touch controller. Other input devices 10072 may include, but are not limited to, a physical keyboard, function keys (e.g., volume control keys, switch keys, etc.), a trackball, a mouse, and a joystick, which are not described in detail herein.

In this embodiment of the application, the radio frequency unit 1001 receives downlink data from a network side device and then processes the downlink data to the processor 1010; in addition, the uplink data is sent to the network side equipment. In general, 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, and the like.

The memory 1009 may be used to store software programs or instructions and various data. The memory 1009 may mainly include a program or instruction storage area and a data storage area, wherein the program or instruction storage area may store an operating system, an application program or instruction (such as a sound playing function, an image playing function, etc.) required for at least one function, and the like. Further, the Memory 1009 may include a high-speed random access Memory, and may further include a nonvolatile Memory, which may be a Read-Only Memory (ROM), a Programmable Read-Only Memory (PROM), an Erasable Programmable Read-Only Memory (erasab PROM, EPROM), an Electrically Erasable Programmable Read-Only Memory (EEPROM), or a flash Memory. Such as at least one magnetic disk storage device, flash memory device, or other non-volatile solid state storage device.

Processor 1010 may include one or more processing units; alternatively, the processor 1010 may integrate an application processor, which primarily handles operating system, user interface, and applications or instructions, etc., and a modem processor, which primarily handles wireless communications, such as a baseband processor. It will be appreciated that the modem processor described above may not be integrated into processor 1010.

The radio frequency unit 1001 is configured to receive first information sent by a network side device; the first information includes at least one of: LBT type, sounding reference signal SRS trigger information, physical uplink control channel PUCCH trigger information, physical uplink shared channel PUSCH scheduling information

The radio frequency unit 1001 is further configured to send, to the network side device, receiving end auxiliary information according to the first information after the terminal successfully performs LBT; wherein the receiving end auxiliary information comprises at least one of: SRS, PUCCH or PUSCH.

In the device of the embodiment, a radio frequency unit receives first information sent by network side equipment; the first information is used for triggering the terminal to send the receiving terminal auxiliary information, and the first information comprises at least one of the following items: the method comprises the following steps of (1) LBT type, sounding reference signal SRS triggering information, physical uplink control channel PUCCH triggering information and physical uplink shared channel PUSCH scheduling information; further, after the terminal successfully performs listen before talk LBT, the radio frequency unit sends, according to the indication of the first information of the network side device, receiving side auxiliary information to the network side device, where the receiving side auxiliary information includes at least one of the following: after receiving the receiving end auxiliary information, the network side equipment can determine that no hidden node exists around the terminal, and at this time, downlink information is sent to the terminal and will not be affected by the hidden node.

Optionally, the radio frequency unit 1001 is further configured to:

and the value of the first indication domain is a fourth preset value, the value of the SRS request domain is the first preset value, the value of the FDRA domain is an effective value, and the Physical Downlink Shared Channel (PDSCH) scheduled by the network side equipment is received.

In the above embodiment, the terminal sends the PUCCH as the receiving side auxiliary information according to the instruction of the network side device, and after receiving the receiving side auxiliary information, the network side device may determine that there is no hidden node around the terminal, and at this time, sends the downlink information to the terminal, which will not be affected by the hidden node.

Optionally, the radio frequency unit 1001 is further configured to:

Optionally, the preset length is 1 symbol length or 2 symbol lengths.

In the above embodiment, the terminal sends the PUSCH as the receiving side auxiliary information according to the instruction of the network side device, and after receiving the receiving side auxiliary information, the network side device may determine that there is no hidden node around the terminal, and at this time, sends the downlink information to the terminal, and is not affected by the hidden node.

Optionally, the radio frequency unit 1001 is further configured to:

Optionally, the processor 1010 is configured to not perform PDSCH detection when the receiving side assistance information is not successfully transmitted.

Optionally, the radio frequency unit 1001 is further configured to:

and receiving a downlink channel or signal sent by the network side.

In the above embodiment, after receiving the receiving-end auxiliary information, the network-side device may determine that there is no hidden node around the terminal, and at this time, send the downlink information to the terminal without being affected by the hidden node.

The embodiment of the application also provides a network side device, which comprises a processor and a communication interface, wherein the communication interface is used for sending the first information to the terminal; the first information includes at least one of: the method comprises the following steps of (1) LBT type, sounding reference signal SRS triggering information, physical uplink control channel PUCCH triggering information and physical uplink shared channel PUSCH scheduling information; the communication interface is further configured to receive terminating auxiliary information sent by the terminal, where the terminating auxiliary information is sent by the terminal according to the first information after the terminal successfully performs listen before talk LBT; wherein the receiving end auxiliary information comprises at least one of: SRS, PUCCH or PUSCH. The embodiment of the network side device corresponds to the embodiment of the method of the network side device, and all implementation processes and implementation manners of the embodiment of the method can be applied to the embodiment of the network side device and can achieve the same technical effect.

Specifically, the embodiment of the application further provides a network side device. As shown in fig. 10, the network device 170 includes: an antenna 71, a radio frequency device 72, a baseband device 73. The antenna 71 is connected to a radio frequency device 72. In the uplink direction, the rf device 72 receives information via the antenna 71 and sends the received information to the baseband device 73 for processing. In the downlink direction, the baseband device 73 processes information to be transmitted and transmits the information to the rf device 72, and the rf device 72 processes the received information and transmits the processed information through the antenna 71.

The above-mentioned band processing means may be located in the baseband means 73, and the method performed by the network device in the above embodiment may be implemented in the baseband means 73, where the baseband means 73 includes a processor 74 and a memory 75.

The baseband device 73 may include, for example, at least one baseband board, on which a plurality of chips are disposed, as shown in fig. 10, where one of the chips, for example, the processor 74, is connected to the memory 75 to call up a program in the memory 75 to execute the network device operation shown in the above method embodiment.

The baseband device 73 may further include a network interface 76 for exchanging information with the radio frequency device 72, for example, a Common Public Radio Interface (CPRI).

Specifically, the network device of the embodiment of the present application further includes: the instructions or programs stored in the memory 75 and capable of being executed on the processor 74, and the processor 74 calls the instructions or programs in the memory 75 to execute the method executed by each module shown in fig. 7, and achieve the same technical effect, and are not described herein in detail to avoid repetition.

The embodiment of the present application further provides a readable storage medium, where a program or an instruction is stored on the readable storage medium, and when the program or the instruction is executed by a processor, the program or the instruction implements each process of the above-mentioned transmission method for receiving end auxiliary information, and can achieve the same technical effect, and in order to avoid repetition, details are not repeated here.

Wherein, the processor is the processor in the terminal described in the above embodiment. The readable storage medium includes a computer readable storage medium, such as a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk or an optical disk, and so on.

The embodiment of the present application further provides a chip, where the chip includes a processor and a communication interface, the communication interface is coupled to the processor, and the processor is configured to run a program or an instruction to implement each process of the above-mentioned transmission method embodiment of the receive-side auxiliary information, and can achieve the same technical effect, and in order to avoid repetition, the details are not repeated here.

It should be understood that the chips mentioned in the embodiments of the present application may also be referred to as a system-on-chip, a system-on-chip or a system-on-chip.

The embodiment of the present application further provides a computer program/program product, where the computer program/program product is stored in a non-transitory storage medium, and the program/program product is executed by at least one processor to implement each process of the foregoing transmission method for receiving end auxiliary information, and can achieve the same technical effect, and in order to avoid repetition, details are not repeated here.

It should be noted that, in this document, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising one of 8230, and" comprising 8230does not exclude the presence of additional like elements in a process, method, article, or apparatus comprising the element. Further, it should be noted that the scope of the methods and apparatus of the embodiments of the present application is not limited to performing the functions in the order illustrated or discussed, but may include performing the functions in a substantially simultaneous manner or in a reverse order based on the functions involved, e.g., the methods described may be performed in an order different than that described, and various steps may be added, omitted, or combined. In addition, features described with reference to certain examples may be combined in other examples.

Through the above description of the embodiments, those skilled in the art will clearly understand that the method of the above embodiments can be implemented by software plus a necessary general hardware platform, and certainly can also be implemented by hardware, but in many cases, the former is a better implementation manner. Based on such understanding, the technical solutions of the present application may be embodied in the form of a computer software product, which is stored in a storage medium (such as ROM/RAM, magnetic disk, optical disk) and includes instructions for enabling a terminal (such as a mobile phone, a computer, a server, or a network device) to execute the method according to the embodiments of the present application.

While the present embodiments have been described with reference to the accompanying drawings, it is to be understood that the present embodiments are not limited to those precise embodiments, which are intended to be illustrative rather than restrictive, and that various changes and modifications may be effected therein by one skilled in the art without departing from the scope of the appended claims.

Claims

1. A method for transmitting auxiliary information at a receiving end is characterized by comprising the following steps:

2. The method for transmitting auxiliary information at a receiving end according to claim 1,

3. The method according to claim 2, wherein in the case that the receiving side assistance information includes the SRS,

4. The method for transmitting auxiliary information at a receiving end according to claim 3, further comprising:

5. The transmission method of terminating auxiliary information according to claim 3 or 4,

the first preset value is not all zero, and the second preset value is zero.

6. The method according to claim 2, wherein in case that the terminating side information includes the PUCCH,

7. The method for transmitting peer-to-peer auxiliary information according to claim 6, further comprising:

8. The method for transmitting auxiliary information at receiving end according to claim 6 or 7,

and the value of the SRS request domain in the downlink allocation DCI is all zero.

9. The method for transmitting auxiliary information at a receiving end according to claim 2,

the LBT type indicated in the DCI is a preset type, the time domain length of the PUSCH is a preset length, and the receiving end auxiliary information is the PUSCH.

10. The method for transmitting auxiliary information at a receiving end according to claim 9,

the preset length is 1 symbol length or 2 symbol lengths.

11. The method for transmitting auxiliary information at a receiving end as claimed in claim 10,

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

12. The method for transmitting terminal side assistance information according to any one of claims 1 to 4, 6 to 7, or 9 to 11,

the LBT type includes at least one of: LBT type 2, LBT type 3 and LBT type 4, wherein the size of the contention window of the LBT type 3 and the LBT type 4 is a target value; the value range of the target value is an integer which is greater than or equal to 0 and less than or equal to 3.

13. The method for transmitting peer-to-peer auxiliary information according to any of claims 1-4, 6-7, or 9-11, wherein the method further comprises:

the terminal receives second information sent by the network side equipment, wherein the second information is sent by the network side equipment after the network side equipment does not receive the receiving end auxiliary information; the second information is used for triggering the terminal to send receiving end auxiliary information, and the receiving end auxiliary information is sent after the terminal successfully executes LBT.

14. The method for transmitting auxiliary information at a receiving end according to any one of claims 1 to 4, 6 to 7 or 9 to 11, further comprising:

and the terminal does not perform PDSCH detection under the condition that the receiving end auxiliary information is not successfully transmitted.

15. The method for transmitting terminal-side assistance information according to any one of claims 1 to 4, 6 to 7, or 9 to 11, wherein after the terminal sends the terminal-side assistance information according to the first information, the method further includes:

and the terminal receives a downlink channel or a signal sent by the network side.

16. The method for transmitting terminal-side auxiliary information according to any one of claims 1 to 4, 6 to 7, or 9 to 11,

when the first information does not contain an LBT type, the LBT type is sent through Radio Resource Control (RRC) signaling or agreed by a protocol.

17. A method for transmitting auxiliary information at a receiving end is characterized by comprising the following steps:

the network side equipment receives receiving end auxiliary information sent by the terminal, wherein the receiving end auxiliary information is sent by the terminal according to the first information after the terminal successfully executes LBT; wherein the receiving end auxiliary information comprises at least one of: SRS, PUCCH, or PUSCH.

18. The method for transmitting auxiliary information at a receiving end as claimed in claim 17,

19. The method of claim 18, wherein if the receiving side assistance information includes the SRS,

20. The method for transmitting peer-to-peer auxiliary information according to claim 19, wherein the method further comprises:

and the value of the first indication domain is a fourth preset value, the value of the SRS request domain is the first preset value, the value of the FDRA domain is an effective value, and the network side equipment sends a Physical Downlink Shared Channel (PDSCH) to the terminal.

21. The transmission method of terminating auxiliary information according to claim 19 or 20,

the first preset value is not all zero, and the second preset value is zero.

22. The method of claim 18, wherein if the receiving side assistance information comprises the PUCCH,

23. The method for transmitting auxiliary information of a receiving end as claimed in claim 22, wherein the method further comprises:

and the value of the second indication domain is a fourth preset value, the value of the FDRA domain is an effective value, and the network side equipment sends a Physical Downlink Shared Channel (PDSCH) to the terminal.

24. The method for transmitting auxiliary information at receiving end as claimed in claim 22 or 23,

25. The method for transmitting auxiliary information at a receiving end as claimed in claim 18,

26. The method as claimed in claim 25, wherein the step of transmitting the auxiliary information at the receiving end comprises,

the preset length is 1 symbol length or 2 symbol lengths.

27. The method as claimed in claim 26, wherein the step of transmitting the auxiliary information at the receiving end,

the preset type is LBT type 2, LBT type 3 or LBT type 4, wherein the size of the contention window of the LBT type 3 and the LBT type 4 is a target value; the value range of the target value is an integer which is greater than or equal to 0 and less than or equal to 3.

28. The method for transmitting terminal side assistance information according to any one of claims 17 to 20, 22 to 23, or 25 to 27,

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

29. The method for transmitting terminating auxiliary information according to any of claims 17-20, 22-23 or 25-27, wherein the method further comprises:

30. The method for transmitting terminal side assistance information according to any one of claims 17 to 20, 22 to 23, or 25 to 27, wherein after the network side device receives the terminal side assistance information sent by the terminal, the method further includes:

31. The method for transmitting terminal side assistance information according to any one of claims 17 to 20, 22 to 23, or 25 to 27,

when the first information does not include an LBT type, the LBT type is transmitted through radio resource control, RRC, signaling or agreed by a protocol.

32. A transmission apparatus for receiving side auxiliary information, comprising:

33. A transmission apparatus for receiving side auxiliary information, comprising:

34. A terminal comprising a processor, a memory, and a program or instructions stored on the memory and executable on the processor, the program or instructions when executed by the processor implementing the steps of the method for transmitting terminating auxiliary information according to any one of claims 1 to 16.

35. A network-side device, comprising 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 terminating auxiliary information according to any one of claims 17 to 31.

36. A readable storage medium, on which a program or instructions are stored, which when executed by a processor, implement the method for transmitting terminating auxiliary information according to any one of claims 1 to 16, or implement the steps of the method for transmitting terminating auxiliary information according to any one of claims 17 to 31.