Method for sending demodulation reference signal, chip and electronic device

Abstract

Provided in the embodiments of the present application are a method for sending a demodulation reference signal (DMRS), a chip, and an electronic device. The method is applied to a first network device. The method comprises: receiving a DMRS sent by a second network device; and sending a DMRS, wherein the DMRS sent by the first network device does not collide with the received DMRS. According to the method provided by the embodiments of the present application, an uplink DMRS and a downlink DMRS transmitted between network devices do not collide with each other, so as to avoid the occurrence of self-interference between the uplink DMRS and the downlink DMRS, thereby protecting the receiving performance of the uplink and downlink DMRSs, and reducing signal transmission interferences under co-frequency co-time full duplex scenarios while achieving co-frequency co-time full duplex at the same time.

Description

Method, chip and electronic device for transmitting demodulation reference signal

[0001] This application claims priority to the Chinese patent application filed with the China Patent Office on December 27, 2023, with application number 202311828835.1 and invention name “A method, chip and electronic device for sending a demodulation reference signal”, the entire contents of which are incorporated by reference into this application. Technical Field

[0002] The present application relates to the field of communication technology, and in particular to a method, device, chip, and electronic device for sending a demodulation reference signal. Background Art

[0003] In wireless communication application scenarios, in order to achieve higher spectrum efficiency, a simultaneous co-frequency full-duplex (CCFD) communication solution is proposed, which uses CCFD to send and receive uplink and downlink signals.

[0004] CCFD means wireless communication devices use the same time and frequency to transmit and receive wireless signals simultaneously, doubling the spectrum efficiency of wireless communication links. In CCFD applications, because uplink and downlink signals are transmitted simultaneously and on the same frequency, they interfere with each other.

[0005] Therefore, a communication solution is needed to reduce signal transmission interference in CCFD scenarios. Summary of the Invention

[0006] In response to the problem of how to reduce signal transmission interference in CCFD scenarios under the existing technology, the present application provides a method, chip and electronic device for sending a demodulation reference signal. The present application also provides a computer-readable storage medium.

[0007] The embodiments of this application adopt the following technical solutions:

[0008] In a first aspect, the present application provides a method for sending a demodulation reference signal (DMRS), the method being applied to a first network device, the method comprising:

[0009] receiving a DMRS sent by a second network device;

[0010] Sending a DMRS, wherein the DMRS sent by the first network device does not collide with the received DMRS.

[0011] In an implementation manner of the first aspect, the first network device is one of a terminal device and a base station device, and the second network device is the other of the terminal device and the base station device.

[0012] In an implementation manner of the first aspect, a timing advance of communication between the first network device and the second network device is within a range of a cyclic prefix.

[0013] In an implementation of the first aspect, the first network device plans to send a first DMRS in a first time window, and the second network device plans to send a second DMRS in a second time window, and the first time window and the second time window collide;

[0014] The sending the DMRS to the second network device includes:

[0015] The sending of the first DMRS is scheduled to avoid collision between the first DMRS and the second DMRS.

[0016] In an implementation of the first aspect, the second network device plans to send the second DMRS based on a first part of subcarriers;

[0017] The scheduling the sending of the first DMRS includes:

[0018] In the first time window, the first DMRS is sent based on a second part of the subcarriers, and the second part does not overlap with the first part.

[0019] In an implementation of the first aspect, the scheduling the sending of the first DMRS includes:

[0020] The sending of the first DMRS is canceled.

[0021] In an implementation of the first aspect, the scheduling the sending of the first DMRS includes:

[0022] The first DMRS is sent in a third time window, wherein there is no collision between the third time window and the second time window.

[0023] In an implementation of the first aspect, the method further includes:

[0024] sending a data signal to the second network device during the first time window;

[0025] Alternatively, no signal is sent to the second network device during the first time window.

[0026] In an implementation manner of the first aspect, the device type of the first network device is a pre-specified device type that performs a DMRS scheduling operation to avoid DMRS collision.

[0027] In an implementation manner of the first aspect, the first network device is a base station device.

[0028] In an implementation of the first aspect, the first network device further plans to send a third DMRS in a third time window, and the second network device further plans to send a fourth DMRS in a fourth time window, wherein: the third time window and the fourth time window are time windows after the first time window and the second time window; and the third time window and the fourth time window collide;

[0029] The method further comprises:

[0030] The third DMRS is sent in the third time window, wherein the second network device cancels sending of the fourth DMRS.

[0031] In an implementation manner of the first aspect, the priority of the first DMRS is lower than the priority of the second DMRS.

[0032] In an implementation of the first aspect, the first number is greater than the second number, wherein:

[0033] The first number is the total number of DMRSs that the first network device plans to send and / or has sent in a first time period, wherein the first time period is a time period including the first time window;

[0034] The second number is the total number of DMRSs planned to be sent and / or DMRSs sent by the second network device in the second time period, wherein the second time period is a time period including the second time window, and the second time period corresponds to the first time period.

[0035] In an implementation of the first aspect, the time-frequency resources of the first network device and the second network device are consistent, the third number is less than the fourth number, and:

[0036] The third number is the total number of DMRSs that the first network device plans to send and / or has sent in a third time period, wherein the third time period is a time period including the first time window;

[0037] The fourth number is the total number of DMRSs that the second network device plans to send and / or has sent in a fourth time period, wherein the fourth time period is a time period including the second time window, and the fourth time period corresponds to the third time period.

[0038] In an implementation manner of the first aspect, the time-frequency resources of the first network device are higher than the time-frequency resources of the second network device.

[0039] In an implementation manner of the first aspect, a timing advance for communication between the first network device and the second network device is outside a range of a cyclic prefix.

[0040] In an implementation of the first aspect, the method further includes:

[0041] The DMRS transmission mode is selected according to the arrival of uplink and downlink services, wherein the DMRS transmission modes include simultaneous same-frequency full-duplex, unidirectional downlink, and unidirectional uplink.

[0042] In an implementation manner of the first aspect, the first network device is a base station device.

[0043] In an implementation manner of the first aspect, the DMRS configurations of the uplink physical channel and the downlink physical channel adopt semi-static independent configuration, and when the uplink physical channel and the downlink physical channel are scheduled simultaneously, a predefined criterion is adopted.

[0044] In an implementation manner of the first aspect, the pattern of the DMRS may be modified by downlink control information (DCI).

[0045] In an implementation manner of the first aspect, in one DMRS configuration, an uplink DMRS and a downlink DMRS are configured simultaneously.

[0046] In an implementation of the first aspect, the sending of the DMRS includes:

[0047] The DMRS is transmitted based on the second part of the subcarriers, where:

[0048] The second portion does not overlap with the first portion of the subcarriers;

[0049] The first part is the subcarrier part used by the second network device to send DMRS.

[0050] In an implementation of the first aspect:

[0051] The first part is odd-numbered subcarriers, and the second part is even-numbered subcarriers;

[0052] or,

[0053] The first part is even-numbered subcarriers, and the second part is odd-numbered subcarriers.

[0054] In an implementation of the first aspect, the sending of the DMRS includes:

[0055] A DMRS is sent based on a first code division multiplexing group (CDM group), wherein:

[0056] The first code division multiplexing group and the second code division multiplexing group are different code division multiplexing groups;

[0057] The second code division multiplexing group is a code division multiplexing group used by the second network device to send DMRS.

[0058] In an implementation of the first aspect, the sending of the DMRS includes:

[0059] The DMRS is transmitted based on the first subcarrier portion in the code division multiplexing group (CDM group), where:

[0060] The first subcarrier portion and the second subcarrier portion are different subcarrier portions in the code division multiplexing group (CDM group);

[0061] The second subcarrier part is a subcarrier part used by the second network device to send DMRS.

[0062] In an implementation of the first aspect, the sending of the DMRS includes:

[0063] In the first time window of a time slot, DMRS is sent, where:

[0064] The one time slot includes at least the first time window and the second time window, and there is no collision between the first time window and the second time window;

[0065] The first time window is a pre-specified time window in the one time slot for sending DMRS;

[0066] The second time window is a pre-specified time window in the one time slot for receiving DMRS.

[0067] In an implementation of the first aspect:

[0068] The one time slot includes 14 consecutive time windows, the 14 consecutive time windows include 7 time window groups, and each time window group includes two consecutive time windows;

[0069] The first time window is the first time window or the second time window in the first time window group, and the second time window is the second time window or the first time window in the first time window group;

[0070] The first time window group is a pre-specified time window group among the seven time window groups.

[0071] In an implementation of the first aspect:

[0072] Each of the seven time window groups corresponds to a bit in a bit map, and the bit map includes seven bits;

[0073] The bit map is used to specify the first time window group from the seven time window groups.

[0074] In an implementation of the first aspect:

[0075] The first time window is a time window specified by a first pattern among the multiple time windows in the one time slot;

[0076] The second time window is another time window specified by the first pattern among the multiple time windows in the one time slot;

[0077] The first mode is a mode specified from a plurality of predefined modes through radio resource control (RRC).

[0078] In an implementation of the first aspect:

[0079] The first time window is a time window corresponding to a preloaded DMRS area in the one time slot, and the second time window is another time window corresponding to the preloaded DMRS area in the one time slot;

[0080] or,

[0081] The first time window is a time window corresponding to an additional DMRS area in the one time slot, and the second time window is another time window corresponding to the additional DMRS area in the one time slot;

[0082] or,

[0083] The first time window is a time window corresponding to the preloaded DMRS area in the one time slot, and the second time window is a time window corresponding to the additional DMRS area in the one time slot;

[0084] or,

[0085] The first time window is a time window corresponding to the additional DMRS area in the one time slot, and the second time window is a time window corresponding to the preloaded DMRS area in the one time slot.

[0086] In an implementation of the first aspect:

[0087] The first network device is a base station device, and the second network device and the third network device are terminal devices; the second network device sends a DMRS to the first network device based on a first part of subcarriers in a second time window;

[0088] The sending of the DMRS includes: sending the DMRS to the third network device based on the second part of the subcarrier in a first time window, the second part does not overlap with the first part, and the first time window and the second time window collide.

[0089] In an implementation of the first aspect:

[0090] The first network device and the third network device are terminal devices, and the second network device is a base station device; the second network device sends a DMRS to the third network device based on the first part of the subcarrier in the second time window;

[0091] The sending of the DMRS includes: sending the DMRS to the second network device based on the second part of the subcarrier in a first time window, the second part does not overlap with the first part, and the first time window and the second time window collide.

[0092] In an implementation of the first aspect:

[0093] The first network device is a base station device, and the second network device, the third network device, and the fourth network device are terminal devices; the third network device sends a DMRS to the first network device based on a first part of a subcarrier in a first time window; and the fourth network device sends a DMRS to the first network device based on a second part of the subcarrier in a second time window.

[0094] The sending of DMRS includes:

[0095] In the first time window, DMRS is sent to the second network device based on the third part of the subcarrier, the third part does not overlap with the first part and the second part, and the first time window collides with the second time window.

[0096] In an implementation of the first aspect:

[0097] The first network device, the third network device, and the fourth network device are terminal devices, and the second network device is a base station device; the third network device sends a DMRS to the second network device based on the first part of the subcarrier in a third time window; and the second network device sends a DMRS to the fourth network device based on the second part of the subcarrier in a second time window;

[0098] The sending of DMRS includes:

[0099] In the first time window, DMRS is sent to the second network device based on the third part of the subcarrier, the third part does not overlap with the first part and the second part, and there is a collision between the first time window, the second time window, and the third time window.

[0100] In an implementation of the first aspect, the first network device is a base station device, and the second network device and the third network device are terminal devices; the third network device sends a DMRS to the first network device in a second time window;

[0101] The sending of DMRS includes:

[0102] The DMRS is sent to the second network device in a first time window, and there is no collision between the first time window and the second time window.

[0103] In an implementation of the first aspect, the first network device and the third network device are terminal devices, and the second network device is a base station device; the second network device sends a DMRS to the third network device in a second time window;

[0104] The sending of DMRS includes:

[0105] The DMRS is sent to the second network device in a first time window, and there is no collision between the first time window and the second time window.

[0106] In a second aspect, the present application provides an electronic chip, comprising:

[0107] A processor is configured to execute computer program instructions stored in a memory, wherein when the computer program instructions are executed by the processor, the electronic chip is triggered to execute the method described in the first aspect.

[0108] In a third aspect, the present application provides an electronic device, comprising a memory for storing computer program instructions, a processor for executing computer program instructions, and a communication device, wherein when the computer program instructions are executed by the processor, the electronic device is triggered to execute the method described in the first aspect.

[0109] In a fourth aspect, the present application provides a computer-readable storage medium, characterized in that a computer program is stored in the computer-readable storage medium, which, when executed on a computer, enables the computer to execute the method described in the first aspect or the second aspect.

[0110] According to the above technical solutions proposed in the embodiments of the present application, at least the following technical effects can be achieved:

[0111] According to the method of the embodiment of the present application, there will be no collision between the uplink DMRS and the downlink DMRS transmitted between network devices, thereby avoiding self-interference between the uplink DMRS and the downlink DMRS, protecting the reception performance of the uplink and downlink DMRS, and reducing signal transmission interference in the CCFD scenario while realizing CCFD. BRIEF DESCRIPTION OF THE DRAWINGS

[0112] FIG1 is a schematic diagram of a communication scenario according to an embodiment of the present application;

[0113] FIG2 shows a flow chart of DMRS transmission according to an embodiment of the present application;

[0114] FIG3 is a schematic diagram showing a time window for sending and receiving symbols according to an embodiment of the present application;

[0115] FIG4 is a schematic diagram of an uplink and downlink DMRS transmission time window according to an embodiment of the present application;

[0116] FIG5 is a schematic diagram of an uplink and downlink DMRS transmission time window according to an embodiment of the present application;

[0117] FIG6 is a schematic diagram showing a planned transmission time window of uplink and downlink DMRS according to an embodiment of the present application;

[0118] FIG7 is a schematic diagram of an uplink and downlink DMRS transmission time window according to an embodiment of the present application;

[0119] FIG8 is a schematic diagram of an uplink and downlink DMRS transmission time window according to an embodiment of the present application;

[0120] FIG9 is a schematic diagram showing a time window for uplink and downlink DMRS planned transmission according to an embodiment of the present application;

[0121] FIG10 is a schematic diagram of an uplink and downlink DMRS transmission time window according to an embodiment of the present application;

[0122] FIG11 is a schematic diagram of a planned transmission time window of uplink and downlink DMRS according to an embodiment of the present application;

[0123] FIG12 is a schematic diagram of an uplink and downlink DMRS transmission time window according to an embodiment of the present application;

[0124] FIG13 is a schematic diagram showing a time window for uplink and downlink DMRS planned transmission according to an embodiment of the present application;

[0125] FIG14 is a schematic diagram of an uplink and downlink DMRS transmission time window according to an embodiment of the present application;

[0126] FIG15 is a schematic diagram showing a planned transmission time window of uplink and downlink DMRS according to an embodiment of the present application;

[0127] FIG16 is a schematic diagram of an uplink and downlink DMRS transmission time window according to an embodiment of the present application;

[0128] FIG17 is a schematic diagram showing a time window for sending and receiving symbols according to an embodiment of the present application;

[0129] FIG18 is a schematic diagram of subcarriers according to an embodiment of the present application;

[0130] FIG19 is a schematic diagram of subcarriers according to an embodiment of the present application;

[0131] FIG20 is a schematic diagram showing a slot sending and receiving a symbol according to an embodiment of the present application;

[0132] FIG21 is a schematic diagram showing a slot sending and receiving a symbol according to an embodiment of the present application;

[0133] FIG22 is a schematic diagram showing a slot sending and receiving a symbol according to an embodiment of the present application;

[0134] FIG23 is a schematic diagram showing communication interactions among multiple network devices according to an embodiment of the present application;

[0135] FIG24 is a schematic diagram showing communication interactions among multiple network devices according to an embodiment of the present application;

[0136] FIG25 is a schematic diagram showing communication interactions among multiple network devices according to an embodiment of the present application;

[0137] FIG26 is a schematic diagram showing the structure of an electronic device according to an embodiment of the present application. DETAILED DESCRIPTION

[0138] To make the purpose, technical solutions, and advantages of this application more clear, the technical solutions of this application will be clearly and completely described below in conjunction with the specific embodiments of this application and the corresponding drawings. Obviously, the embodiments described are only part of the embodiments of this application, not all of them. Based on the embodiments in this application, all other embodiments obtained by ordinary technicians in this field without making creative efforts are within the scope of protection of this application.

[0139] The terms used in the implementation section of this application are only used to explain the specific embodiments of this application and are not intended to limit this application.

[0140] FIG1 is a schematic diagram of a communication scenario according to an embodiment of the present application.

[0141] As shown in FIG1 , CCFD communication is performed between network device 100 and network device 110 .

[0142] In one embodiment, the network device 100 may be a terminal device, and the network device 110 may be a base station device. Alternatively, in another embodiment, the network device 100 may be a base station device, and the network device 110 may be a terminal device.

[0143] In the embodiments of the present application, a terminal device is a device that includes wireless communication capabilities. The terminal device may be user equipment (UE), mobile station (MS), mobile terminal (MT), customer premise equipment (CPE), etc. The terminal can be widely used in various scenarios, such as device-to-device (D2D), vehicle-to-everything (V2X) communication, machine-type communication (MTC), Internet of Things (IoT), virtual reality, augmented reality, industrial control, autonomous driving, telemedicine, smart grid, smart furniture, smart office, smart wearable, smart transportation, smart city, etc.

[0144] For example, a terminal device can be a handheld device with wireless connectivity, an in-vehicle device, a machine type communication (MTC) terminal, etc. A terminal device can be a mobile phone, tablet computer, laptop computer, PDA, mobile internet device (MID), wearable device, virtual reality (VR) device, augmented reality (AR) device, wireless terminal in industrial control, wireless terminal in self-driving, wireless terminal in remote medical surgery, wireless terminal in smart grid, wireless terminal in transportation safety, wireless terminal in smart city, or wireless terminal in smart home. For example, a wireless terminal in self-driving can be a drone, helicopter, or airplane. For example, a wireless terminal in the Internet of Vehicles can be an in-vehicle device, complete vehicle equipment, in-vehicle module, vehicle, or ship. A wireless terminal in industrial control can be a camera, robot, or robotic arm. Wireless terminals in a smart home can be TVs, air conditioners, vacuum cleaners, speakers, or set-top boxes.

[0145] It should be noted that in the embodiments of the present application, the terminal device may be a device or apparatus with a chip, or a device or apparatus with integrated circuits, or a chip, module or control unit in the device or apparatus shown above, and this application does not limit this specifically.

[0146] In the embodiments of the present application, a base station device is a device deployed in a radio access network (RAN) to provide wireless communication functions for terminal devices. The base station device can be called an access network device, a RAN entity, or an access node.

[0147] Specifically, the RAN may be a cellular system related to the third generation partnership project (3GPP), such as a 4G, 5G mobile communication system, or a future-oriented evolution system (such as a 6G mobile communication system). For example, the fourth generation communication system may include a long term evolution (LTE) communication system. The fifth generation communication system may include a new radio (NR) communication system. The technical solution of the present application may also be applied to wireless fidelity (WiFi) systems, communication systems that support the integration of multiple wireless technologies, device-to-device (D2D) systems, vehicle to everything (V2X) communication systems, or satellite communication systems, or narrowband Internet of Things (NB-IoT) systems, etc.

[0148] The RAN can also be an open access network (O-RAN or ORAN), a cloud radio access network (CRAN), or a wireless fidelity (WiFi) system. The RAN can also be a communication system that integrates two or more of the above systems.

[0149] Specifically, the base station device may be an access network device of a cellular system related to the 3rd Generation Partnership Project (3GPP). For example, a fourth-generation (4G) mobile communication system or a 5G mobile communication system. The base station device may also be an access network device in an open access network (O-RAN or ORAN) or a cloud radio access network (CRAN). Alternatively, the base station device may also be an access network device in a communication system obtained by integrating two or more of the above communication systems.

[0150] Base station equipment includes, but is not limited to: evolved Node B (eNB), radio network controller (RNC), Node B (NB), base station controller (BSC), base transceiver station (BTS), home base station (e.g., home evolved NodeB, or home Node B, HNB), baseband unit (BBU), access point (AP) in wireless fidelity (WIFI) system, macro base station, micro base station, wireless relay node, donor node, wireless controller in CRAN scenario, wireless backhaul node, transmission point (TP) or transmission and receiving point (TRP). Base station equipment can also be access network equipment in 5G mobile communication system. For example, the next generation NodeB (gNB) in the new radio (NR) system, TRP, TP, or one or a group of antenna panels (including multiple antenna panels) of a base station in a 5G mobile communication system. Alternatively, the base station device may also be a network node constituting a gNB or a transmission point. For example, a centralized unit (CU), a distributed unit (DU), a CU-control plane (CP), a CU-user plane (UP), or a radio unit (RU). The CU and DU may be configured separately or included in the same network element. For example, a BBU. The RU may be included in a radio frequency device or radio frequency unit. For example, in a remote radio unit (RRU), an active antenna unit (AAU), or a remote radio head (RRH). Alternatively, the base station device may also be a server, a wearable device, a vehicle, or an onboard device. For example, in V2X technology, the base station device may be a road side unit (RSU).

[0151] During the communication process between the terminal device and the base station device, the transmission from the terminal device to the base station device is called uplink, and the transmission from the base station device to the terminal device is called downlink.

[0152] In CCFD scenarios, terminal devices transmit uplink signals while receiving downlink signals (uplink and downlink signals occupy the same time domain resources). Furthermore, uplink and downlink signals are transmitted based on subcarriers in the same frequency band (uplink and downlink signals occupy the same frequency domain resources). Therefore, when a terminal device receives a downlink signal, it may experience interference from its own uplink signal. Similarly, when a base station device receives an uplink signal, it also transmits a downlink signal. Furthermore, when a base station device transmits a downlink signal, it may experience interference from its own downlink signal.

[0153] Furthermore, during the communication interaction between the terminal device and the base station device, the terminal device and the base station device will send a demodulation reference signal (DMRS) to each other. DMRS is widely present in various important physical channels, such as the downlink physical broadcast channel (PBCH), physical downlink control channel (PDCCH) and physical downlink shared channel (PDSCH), as well as the uplink physical uplink control channel (PUCCH) and physical uplink shared channel (PUSCH). Its most important function is coherence demodulation, which serves the demodulation of each physical channel.

[0154] The transmission of DMRS by a terminal device to a base station device is referred to as uplink DMRS transmission, and the reception of DMRS by a terminal device is referred to as downlink DMRS reception. The transmission of DMRS by a base station device to a terminal device is referred to as downlink DMRS transmission, and the reception of DMRS by a terminal device is referred to as uplink DMRS reception.

[0155] In CCFD scenarios, when a terminal device receives a downlink DMRS, if it also transmits an uplink DMRS, and the uplink and downlink DMRS are transmitted based on subcarriers in the same frequency band, a collision will occur between the uplink and downlink DMRS, and the terminal device's reception of the downlink DMRS will be interfered with by the uplink DMRS it itself transmits. Similarly, when a base station device receives an uplink DMRS, if it also transmits a downlink DMRS, and the uplink and downlink DMRS are transmitted based on subcarriers in the same frequency band, a collision will occur between the uplink and downlink DMRS, and the base station device's reception of the uplink DMRS will be interfered with by the downlink DMRS it itself transmits.

[0156] Since DMRS has the greatest impact on signal reception performance, and considering that the power of transmitting DMRS is higher than the power of transmitting data, one embodiment of the present application proposes a method for transmitting DMRS to avoid collisions between uplink and downlink DMRSs, protect the reception performance of uplink and downlink DMRSs, and reduce signal transmission interference in CCFD scenarios while achieving CCFD.

[0157] FIG2 is a flowchart showing a DMRS transmission process according to an embodiment of the present application.

[0158] As shown in FIG2 , during CCFD communication interaction between network device 100 and network device 110 , network device 100 sends a DMRS to network device 110 ( S201 ); and network device 110 sends a DMRS to network device 100 ( S202 ).

[0159] S201 and S202 are executed in any order. In the CCFD scenario, S201 and S202 can be executed simultaneously.

[0160] In one embodiment, the network device 100 is a terminal device, and the network device 110 is a base station device. The DMRS sent by the network device 100 is an uplink DMRS; the DMRS sent by the network device 110 is a downlink DMRS.

[0161] Alternatively, in another embodiment, the network device 100 is a base station device, and the network device 110 is a terminal device. The DMRS sent by the network device 100 is a downlink DMRS; the DMRS sent by the network device 110 is an uplink DMRS.

[0162] To protect the reception performance of uplink and downlink DMRS, in one embodiment of the present application, the DMRS sent by the network device 100 in S201 does not collide with the DMRS sent by the second network device 200 in S202. That is, the DMRS sent by the network device 100 in S201 and the DMRS sent by the second network device 200 in S202 each occupy independent time-frequency resources.

[0163] According to the method of the embodiment of the present application, there will be no collision between the uplink DMRS and the downlink DMRS transmitted between network devices, thereby avoiding self-interference between the uplink DMRS and the downlink DMRS, protecting the reception performance of the uplink and downlink DMRS, and reducing signal transmission interference in the CCFD scenario while realizing CCFD.

[0164] In an embodiment of the present application, the identification unit used when sending and receiving signals between a terminal device and a base station device is a symbol. The terminal device sends a DMRS to the base station device, that is, sends an uplink symbol carrying the DMRS. The terminal device receives the DMRS sent by the base station device, that is, receives a downlink symbol carrying the DMRS. The base station device sends a DMRS to the terminal device, that is, sends a downlink symbol carrying the DMRS. The base station device receives the DMRS sent by the terminal device, that is, receives an uplink symbol carrying the DMRS.

[0165] In the embodiments of the present application, the time period during which a terminal device and a base station device transmit or receive a symbol is referred to as a time window. A time window refers to the time period during which a symbol is transmitted or received. If a terminal device transmits a symbol within a time window, the base station device is considered to have received the symbol within that time window. Similarly, if a base station device transmits a symbol within a time window, the terminal device is considered to have received the symbol within that time window.

[0166] For example, if a terminal device sends a symbol (uplink symbol) to a base station device in a certain time window, the base station device receives the uplink symbol in the time window. If a base station device sends a symbol (downlink symbol) to a terminal device in a certain time window, the terminal device receives the downlink symbol in the time window.

[0167] In the CCFD scenario, a network device sends a symbol while receiving it, and the duration of a time window in which the network device receives a symbol is consistent with the duration of a time window in which the network device sends a symbol.

[0168] The base station's symbol transmission time window (downlink time window) is aligned with the symbol reception time window (uplink time window). However, the terminal's symbol transmission time window and symbol reception time window may not be aligned. In other words, a terminal device may receive a single symbol and receive it while interfering with two transmitted symbols.

[0169] For example, FIG3 is a schematic diagram showing a time window for sending and receiving symbols according to an embodiment of the present application.

[0170] In one embodiment, 301 and 302 are two consecutive uplink symbols sent by the terminal device to the base station device. The sending time windows (uplink time windows) occupied by 301 and 302 are 311 and 312 respectively.

[0171] 303 and 304 represent the terminal device receiving two consecutive downlink symbols sent by the base station device. The receiving time windows (downlink time windows) occupied by 303 and 304 are 313 and 314 respectively.

[0172] As shown in Figure 3, the sending time windows 311 and 312 are not aligned with the receiving time windows 313 and 314. There is a timing advance (TA) between the sending time window and the receiving time window.

[0173] In some application scenarios, a symbol consists of a cyclic prefix (CP) and a payload. When the TA is within the CP range (as shown in Figure 3), the CP can be removed so that the terminal device can only receive interference from a single transmitted symbol within a received symbol. In other words, within the terminal device's receive window for downlink symbols, it will only receive interference from a single transmitted symbol.

[0174] At this time, the interference patterns on the base station side and the terminal side can be considered to be the same. In the case of a small cell radius, it can be considered a common situation that the TA is within the CP range.

[0175] Specifically, when a TA is within the CP range, if one time window collides with another time window, the colliding time windows can be considered the same time window. Avoiding uplink and downlink DMRS collision means preventing uplink DMRS and downlink DMRS from colliding in the same time window (within one symbol).

[0176] In one embodiment, before a network device transmits a DMRS, it must first plan a time window for transmitting the DMRS. In this embodiment of the present application, the fact that a network device plans to transmit a DMRS in a certain time window does not necessarily mean that the DMRS has already been transmitted. The network device may schedule DMRS transmission at any time before the time window to change the plan, such that the network device does not transmit the DMRS in that time window, or transmits the DMRS in that time window using a different transmission method than planned.

[0177] For example, assume that network device 100 plans to transmit DMRS (DA) in time window TA, and network device 110 plans to transmit DMRS (DB) in time window TB, and time window TA and time window TB collide. If DMRS transmission is performed as planned, DMRS (DA) and DMRS (DB) will collide in the time domain.

[0178] However, this does not mean that in actual communication, DMRS (DA) and DMRS (DB) will definitely collide in the time domain. If network device 100 and / or network device 110 does not send DMRS as planned, there may be no DMRS collision.

[0179] In one embodiment, in order to avoid collision between DMRS (DA) and DMRS (DB), the transmission of DMRS (DA) and / or DMRS (DB) is scheduled.

[0180] Optionally, in one embodiment, both the network device 100 and the network device 110 schedule the transmission of their own DMRSs to avoid collision between uplink and downlink DMRSs.

[0181] Optionally, in another embodiment, one of network device 100 and network device 110 schedules the transmission of its own DMRS to avoid a collision between uplink and downlink DMRSs. That is, if the planned transmission of DMRSs by network device 100 and network device 110 would cause a collision between uplink and downlink DMRSs, one of the network devices is instructed to transmit the DMRS as planned, while the other device schedules the transmission of the DMRS to change the plan so that the actual DMRS transmission does not cause a collision between uplink and downlink DMRSs.

[0182] Specifically, the network device that performs the scheduling of DMRS transmission can be referred to as the first network device, and the network device that sends DMRS according to the plan can be referred to as the second network device. Correspondingly, the DMRS that the first network device plans to send can be referred to as the first DMRS, and the DMRS that the second network device plans to send can be referred to as the second DMRS.

[0183] For example, in S201, the network device 100 schedules the transmission of the DMRS (DA) so that the DMRS (DA) does not collide with the DMRS (DB). Specifically, the network device 100 that schedules the transmission of the DMRS (DA) in S201 can be referred to as the first network device; the network device 110 that does not need to schedule the transmission of the DMRS (DB) in S202 can be referred to as the second network device; the DMRS (DA) can be referred to as the first DMRS; the DMRS (DB) can be referred to as the second DMRS; the time window TA can be referred to as the first time window; and the time window TB can be referred to as the second time window.

[0184] For another example, in S202, the network device 110 schedules the transmission of DMRS (DB) so that DMRS (DB) does not collide with DMRS (DA). Specifically, the network device 110 that schedules the transmission of DMRS (DB) in S202 can be referred to as a first network device; the network device 100 that does not need to schedule the transmission of DMRS (DA) in S201 can be referred to as a second network device; DMRS (DB) can be referred to as a first DMRS; DMRS (DA) can be referred to as a second DMRS; time window TB can be referred to as a first time window; and time window TA can be referred to as a second time window.

[0185] The following uses implementations 1-3 as examples to illustrate various implementations of scheduling DMRS when the TA is within the CP range. It should be noted that the implementation of scheduling DMRS includes but is not limited to the implementations illustrated below.

[0186] Implementation 1

[0187] In one embodiment, for the same terminal device, if, as planned, the uplink and downlink DMRS appear in the same time window, or appear in two time windows where there is a collision (there is a collision in the time domain between the uplink and downlink DMRS), and both the uplink and downlink DMRS do not use up all subcarriers, then the uplink and downlink DMRS are multiplexed using frequency division multiplexing (FDM) so that the uplink and downlink DMRS actually sent do not collide in the frequency domain.

[0188] For example, in one embodiment, network device 100 plans to transmit DMRS (DA) in time window TA, and network device 110 plans to transmit DMRS (DB) in time window TB, and time window TA and time window TB collide. Furthermore, network device 110 plans to transmit DMRS (DB) based on the first portion of subcarriers in time window TB.

[0189] In S201 , the network device 100 schedules the sending of DMRS (DA), including: sending DMRS (DA) in a time window TA, wherein the DMRS (DA) is sent based on a second part of the subcarriers, and the second part of the subcarriers does not overlap with the first part.

[0190] In S202 , the network device 110 sends a DMRS (DB) based on a first part of subcarriers in a time window TB as planned.

[0191] For another example, in another embodiment, network device 100 plans to send DMRS (DA) in time window TA, and network device 110 plans to send DMRS (DB) in time window TB. Time window TA and time window TB collide. Furthermore, network device 100 plans to send DMRS (DA) based on the second part of the subcarriers in time window TA.

[0192] In S201, the network device 100 sends DMRS (DA) based on the second part of the subcarrier in the time window TA as planned.

[0193] In S202 , the network device 110 schedules the sending of DMRS (DB), including sending DMRS (DB) in a time window TB, wherein the DMRS (DB) is sent based on a first part of the subcarriers, and a second part of the subcarriers does not overlap with the first part.

[0194] In this way, although the time windows for network device 100 and network device 110 to send DMRS collide, since the carriers carrying the uplink and downlink DMRS are different parts of the subcarriers, the uplink and downlink DMRS will not collide in the frequency domain, which effectively avoids mutual interference between the uplink and downlink DMRS.

[0195] It should be noted that in the embodiment of the present application, the subcarrier is divided into multiple parts in the frequency domain, and the divided subcarrier parts are also subcarriers. For example, subcarrier Z1 can be divided into four subcarriers Z11-Z14, the first part of the subcarrier can include subcarriers Z11 and Z13, and the second part of the subcarrier can include subcarriers Z12 and Z14.

[0196] Optionally, in one embodiment, a device type of a network device for executing the scheduling of DMRS transmission is pre-specified, so that when the transmission of DMRS needs to be scheduled, a device is selected from network device 100 and network device 110 according to the pre-specified device type to schedule its own DMRS transmission.

[0197] For example, network device 100 is a terminal device, and network device 110 is a base station device. It is pre-specified that the terminal device schedules the transmission of its own DMRS. When network device 100 plans to transmit DMRS (DA) in time window TA, and network device 110 plans to transmit DMRS (DB) in time window TB, and when time window TA and time window TB collide, network device 100 is selected from network device 100 and network device 110, and network device 100 schedules the transmission of DMRS (DA) so that the subcarrier portion used by DMRS (DA) does not overlap with the subcarrier portion used by DMRS (DB).

[0198] For another example, network device 100 is a terminal device and network device 110 is a base station device. The base station device is pre-specified to schedule the transmission of its own DMRS. When network device 100 plans to transmit DMRS (DA) in time window TA, and network device 110 plans to transmit DMRS (DB) in time window TB, and time window TA and time window TB collide, network device 110 is selected from network device 100 and network device 110, and network device 110 schedules the transmission of DMRS (DB) so that the subcarrier portion used by DMRS (DB) does not overlap with the subcarrier portion used by DMRS (DA).

[0199] Optionally, in another embodiment, to ensure that there is no collision between uplink and downlink DMRS in the frequency domain, the base station device ensures the implementation of FDM of the uplink and downlink DMRS, that is, the base station device schedules the transmission of DMRS.

[0200] Optionally, in one embodiment, a communication protocol specifies a rule such that, when scheduling DMRS to implement DMRS FDM, DMRS in one direction (uplink or downlink) fills in the remaining space in the subcarriers occupied by DMRS in the other direction (downlink or uplink). For example, the subcarriers are divided into a first portion and a second portion, with the uplink DMRS occupying the first portion and the downlink DMRS filling in the remaining space in the subcarriers occupied by the uplink DMRS. That is, the downlink DMRS occupies the second portion, and both the uplink and downlink DMRSs fully utilize the subcarriers.

[0201] Optionally, in another embodiment, there is no restriction on the uplink and downlink DMRS to fully occupy the subcarriers. Instead, the uplink and downlink DMRS occupancy of subcarriers is configured according to actual conditions, and it is only necessary to ensure that the subcarrier frequency bands occupied by the uplink and downlink DMRS do not collide.

[0202] FIG4 is a schematic diagram of uplink and downlink DMRS transmission time windows according to an embodiment of the present application.

[0203] As shown in FIG4 , 410 is a downlink signal (eg, PDSCH) that the base station device plans to send to the terminal device, and 420 is an uplink signal (eg, PUSCH) that the terminal device plans to send to the base station device.

[0204] The time domain is divided horizontally. In 410 and 420 shown in FIG4 , different line segments in the horizontal direction correspond to different time windows (each time window corresponds to a symbol).

[0205] As shown in Figure 4, 410 contains eight symbols (S411-S418), each corresponding to eight time windows (T411-T418). 420 contains eight symbols (S421-S428), each corresponding to eight time windows (T421-T428). T411 collides with T421, T412 collides with T422, T413 collides with T423, T414 collides with T424, T415 collides with T425, T416 collides with T426, T417 collides with T427, and T418 collides with T428. It can be considered that after the CP removal operation, T411-T418 are aligned with T421-T428.

[0206] The frequency domain is divided vertically. In 410 and 420 shown in Figure 4, different vertical line segments correspond to different subcarrier frequency bands. As shown in Figure 4, 410 and 420 are aligned vertically (corresponding to the same subcarrier), and the subcarriers of 410 and 420 contain 12 frequency bands (D41-D412).

[0207] It should be noted here that the time window division and subcarrier frequency band division shown in FIG. 4 and subsequent embodiments are merely brief examples and do not represent actual application scenarios.

[0208] The base station device plans to send data signals to the terminal device at T411, T413, T415, T417, and T418. That is, S411, S413, S415, S417, and S418 are data signals. In this embodiment of the present application, the data signal is a signal that does not carry DMRS. In this embodiment of the present application, the specific format of the data signal is not further limited.

[0209] The base station plans to carry DMRS (downlink DMRS) in S412, S414, and S416. Furthermore, when sending DMRS, the base station does not use all subcarrier frequency bands (only the first portion of the subcarriers is used). As shown in Figure 4, in S412, S414, and S416, DMRS is sent using frequency bands D41, D43, D45, D47, D49, and D411 (marking the portion occupied by downlink DMRS).

[0210] The terminal device plans to send data signals to the terminal device at T421, T423, T425, T427, and T428. That is, S421, S423, S425, S427, and S428 are data signals.

[0211] The terminal device plans to carry DMRS (uplink DMRS) in S422, S424, and S426. In addition, when the terminal device plans to send DMRS, it does not use all subcarrier frequency bands (only the first part of the subcarrier is used). As shown in Figure 4, in S422, S424, and S426, DMRS is sent using frequency bands D41, D43, D45, D47, D49, and D411 (marking the uplink DMRS occupied portion).

[0212] If the terminal device and the base station device send uplink and downlink signals according to the plan shown in FIG4 , there will be collisions between the uplink and downlink DMRS in both the time domain and the frequency domain.

[0213] To avoid uplink and downlink DMRS collisions, the base station schedules the transmission of downlink DMRS so that the time window for transmitting the downlink DMRS follows the time window shown in the plan 410 (the uplink DMRS is carried in S412, S414, and S416, and the uplink DMRS does not occupy the subcarrier frequency band occupied by the downlink DMRS).

[0214] FIG5 is a schematic diagram of uplink and downlink DMRS transmission time windows according to an embodiment of the present application.

[0215] As shown in Figure 5, 510 is a downlink signal (e.g., PDSCH) sent by the base station to the terminal based on the plan shown in Figure 4. 520 is an uplink signal (e.g., PUSCH) sent by the terminal to the base station based on the plan shown in Figure 4.

[0216] Referring to the time domain and frequency domain division in Figure 4 , the time domain is divided horizontally. In 510 and 520 shown in Figure 5 , different line segments in the horizontal direction correspond to different time windows (each time window corresponds to a symbol).

[0217] The frequency domain is divided vertically. In 510 and 520 shown in Figure 5 , different vertical line segments correspond to different subcarrier frequency bands. As shown in Figure 5 , 510 and 520 are vertically aligned (corresponding to the same subcarrier). The subcarriers of 510 and 520 contain 12 frequency bands (D51-D512), which are consistent with D41-D412 shown in Figure 4 .

[0218] The terminal device transmits uplink signal 520 as planned in Figure 4. The signal structure of signal 520 is identical to that of signal 420. Signal 520 contains eight symbols (S521-S528), each corresponding to eight time windows (T521-T528). S521, S523, S525, S527, and S528 correspond to the planned S421, S423, S425, S427, and S428, while T521-T528 correspond to the planned T421-T428. S521, S523, S525, S527, and S528 are data signals.

[0219] The uplink DMRS is carried in S522, S524, and S526 sent by the terminal device. The uplink DMRS does not use all subcarrier frequency bands (only the second part of the subcarrier is used, and the second part of the subcarrier does not collide with the first part). In S522, S524, and S526, the uplink DMRS occupies frequency bands D51, D53, D55, D57, D59, and D511 (marking the part occupied by the uplink DMRS).

[0220] Based on the plan shown in Figure 4, the base station schedules the transmission of uplink DMRS. The downlink signal transmitted by the base station is shown in 510. 510 includes eight symbols (S511-S518), each corresponding to eight time windows (T511-T518). S511-S518 correspond to the planned S411-S418, and T511-T518 correspond to the planned T411-T418. S512, S514, and S516 carry the downlink DMRS. S511, S513, S515, S517, and S518 are data signals.

[0221] The base station transmits S512, S514, and S516 with downlink DMRS. Downlink DMRS does not use all subcarrier frequency bands (only the first portion of subcarriers is used). In S512, S514, and S516, downlink DMRS occupies frequency bands D52, D54, D56, D58, D510, and D512 (marking the portion occupied by downlink DMRS).

[0222] As shown in FIG5 , the base station device and the terminal device transmit uplink and downlink signals. Although the uplink and downlink DMRSs collide in the time domain, they do not collide in the frequency domain, thereby avoiding mutual interference between the uplink and downlink DMRSs.

[0223] Implementation 2

[0224] In one embodiment, for the same terminal device, if uplink and downlink DMRSs are scheduled to appear in the same time window, or appear in two time windows that collide, the transmission of the uplink DMRS or downlink DMRS is scheduled, and the transmission of the uplink DMRS or downlink DMRS in the collided uplink and downlink DMRS is canceled, so that there is no collision in the time domain between the uplink and downlink DMRSs.

[0225] For example, the network device 100 plans to send DMRS (DA) in the time window TA, and the network device 110 plans to send DMRS (DB) in the time window TB. The time window TA collides with the time window TB.

[0226] Optionally, in one embodiment, in S201, the network device 100 schedules the transmission of the DMRS (DA), including canceling the transmission of the DMRS (DA). In S202, the network device 110 transmits the DMRS (DB) in the time window TB.

[0227] Optionally, in another embodiment, in S202, the network device 110 schedules the transmission of DMRS (DA), including canceling the transmission of DMRS (DB). In S201, the network device 100 transmits DMRS (DA) in the time window TA.

[0228] Implementation 2.1

[0229] Optionally, in one embodiment, a device type of a network device for canceling DMRS transmission is pre-specified, so that when DMRS transmission needs to be canceled, a device is selected from network device 100 and network device 110 according to the pre-specified device type to cancel its own DMRS transmission.

[0230] For example, the network device 100 is a terminal device, and the network device 110 is a base station device. It is pre-specified that the terminal device cancels the transmission of its own DMRS.

[0231] When network device 100 plans to send DMRS (DA) in time window TA, and network device 110 plans to send DMRS (DB) in time window TB, and there is a collision between time window TA and time window TB, network device 100 is selected from network device 100 and network device 110, and network device 100 cancels the sending of DMRS (DA).

[0232] For another example, the network device 100 is a terminal device, and the network device 110 is a base station device. It is pre-specified that the base station device cancels the transmission of its own DMRS.

[0233] When network device 100 plans to send DMRS (DA) in time window TA, and network device 110 plans to send DMRS (DB) in time window TB, and there is a collision between time window TA and time window TB, network device 110 is selected from network device 100 and network device 110, and network device 110 cancels the sending of DMRS (DB).

[0234] Implementation 2.2

[0235] Optionally, in one embodiment, if the uplink and downlink DMRSs collide multiple times in the time domain as planned, the two network devices participating in the communication cancel the transmission of the DMRSs in turn.

[0236] Implementation 2.2.1

[0237] FIG6 is a schematic diagram showing a planned transmission time window of uplink and downlink DMRS according to an embodiment of the present application.

[0238] As shown in FIG6 , 610 is a downlink signal (eg, PDSCH) that the base station device plans to send to the terminal device, and 620 is an uplink signal (eg, PUSCH) that the terminal device plans to send to the base station device.

[0239] Referring to the time domain and frequency domain division shown in Figure 4 , the time domain is divided horizontally. In 610 and 620 shown in Figure 6 , different line segments in the horizontal direction correspond to different time windows (each time window corresponds to a symbol).

[0240] As shown in Figure 6, 610 contains eight symbols (S611-S618), each corresponding to eight time windows (T611-T618). 620 contains eight symbols (S621-S628), each corresponding to eight time windows (T621-T628). T611 collides with T621, T612 collides with T622, T613 collides with T623, T614 collides with T624, T615 collides with T625, T616 collides with T626, T617 collides with T627, and T618 collides with T628. It can be considered that after the CP removal operation, T611-T618 are aligned with T621-T628.

[0241] The base station device plans to send data signals to the terminal device at T611, T613, T615, T617, and T618. That is, S611, S613, S615, S617, and S618 are data signals.

[0242] The base station device plans to carry downlink DMRS 602 in S612 , downlink DMRS 604 in S614 , and downlink DMRS 606 in S616 .

[0243] The terminal device plans to send data signals to the terminal device at T621, T623, T625, T627, and T628. That is, S621, S623, S625, S627, and S628 are data signals.

[0244] The terminal device plans to carry downlink DMRS601 in S622, downlink DMRS603 in S624, and downlink DMRS605 in S626.

[0245] If the terminal device and the base station device send uplink and downlink signals according to the plan shown in FIG6 , there will be a collision between the uplink and downlink DMRS in the time domain.

[0246] To avoid uplink and downlink DMRS collisions, the terminal device and the base station device take turns scheduling the transmission of uplink DMRS. The transmission of uplink DMRS or downlink DMRS is canceled, so that the terminal device does not transmit uplink DMRS during the time window when the base station device transmits downlink DMRS; or the base station does not transmit downlink DMRS during the time window when the terminal device transmits uplink DMRS.

[0247] FIG7 is a schematic diagram of uplink and downlink DMRS transmission time windows according to an embodiment of the present application.

[0248] As shown in Figure 7, 710 is a downlink signal (eg, PDSCH) sent by the base station to the terminal based on the plan shown in Figure 6. 720 is an uplink signal (eg, PUSCH) sent by the terminal to the base station based on the plan shown in Figure 6.

[0249] Referring to the time domain division in Figure 4 , the time domain is divided horizontally. In 710 and 720 shown in Figure 7 , different line segments in the horizontal direction correspond to different time windows (each time window corresponds to a symbol).

[0250] Since S611, S621, S613, S623, S615, S625, S617, S627, S618, and S628 are data signals, the base station sends downlink signals S711, S713, S715, S717, and S718 to the terminal device during time windows T711, T713, T715, T717, and T718 according to the plan shown in Figure 6. T711, T713, T715, T717, and T718 are the planned T611, T613, T615, T617, and T618, and S711, S713, S715, S717, and S718 are the planned S611, S613, S615, S617, and S618.

[0251] In time windows T721, T723, T725, T727, and T728, the terminal device sends uplink signals S721, S723, S725, S727, and S728 to the terminal device according to the plan shown in Figure 6. T721, T723, T725, T727, and T728 are the planned T621, T623, T625, T627, and T628, and S721, S723, S725, S727, and S728 are the planned S621, S623, S625, S627, and S628.

[0252] According to the plan shown in Figure 6, when the base station device sends a downlink signal S612 to the terminal device in the time window T612, and when the terminal device sends an uplink signal S622 to the terminal device in the time window T622, the downlink DMRS602 (DMRS (DB)) carried by the downlink signal S612 collides with the uplink DMRS601 (DMRS (DA)) carried by the uplink signal S622 in the time domain.

[0253] Therefore, the terminal device cancels the transmission of uplink DMRS601 (DMRS (DA)).

[0254] As shown in FIG7 , in time window T712, the base station sends a downlink signal S712 to the terminal device according to the plan shown in FIG6 . T712 is the planned T612, and S712 is the planned S612. S712 carries DMRS602.

[0255] In the time window T722, the terminal device does not send an uplink signal to the base station device. T722 is the planned T622.

[0256] According to the plan shown in Figure 6, when the base station device sends a downlink signal S614 to the terminal device in the time window T614, and when the terminal device sends an uplink signal S624 to the terminal device in the time window T624, the downlink DMRS604 carried by the downlink signal S614 collides with the uplink DMRS603 carried by the uplink signal S624 in the time domain.

[0257] Furthermore, the last cancellation of DMRS transmission was performed by the terminal device.

[0258] Therefore, the base station device cancels the transmission of the downlink DMRS 604 .

[0259] As shown in FIG7 , in time window T724, the terminal device sends an uplink signal S724 to the base station device according to the plan shown in FIG6 . T724 is the planned T624, and S724 is the planned S624. S724 carries DMRS603.

[0260] The base station device does not send a downlink signal to the terminal device in the time window T714, and T714 is the planned T614.

[0261] According to the plan shown in Figure 6, when the base station device sends a downlink signal S616 to the terminal device in the time window T616, and when the terminal device sends an uplink signal S626 to the terminal device in the time window T626, the downlink DMRS606 carried by the downlink signal S616 collides with the uplink DMRS605 carried by the uplink signal S626 in the time domain.

[0262] Furthermore, the last cancellation of DMRS transmission was performed by the base station device.

[0263] Therefore, the terminal device cancels the transmission of uplink DMRS605.

[0264] As shown in FIG7 , in time window T716, the base station sends a downlink signal S716 to the terminal device according to the plan shown in FIG6 . T716 is the planned T616, and S716 is the planned S616. S716 carries DMRS606.

[0265] In the time window T726, the terminal device does not send an uplink signal to the base station device. T726 is the planned T626.

[0266] As shown in FIG7 , the base station device and the terminal device transmit uplink and downlink signals, and there is no collision between the uplink and downlink DMRSs in the time domain, thereby avoiding mutual interference between the uplink and downlink DMRSs.

[0267] Implementation 2.2.2

[0268] According to the embodiment shown in FIG7 , when a terminal device cancels transmission of an uplink DMRS or a base station device cancels transmission of a downlink DMRS, no signal is transmitted during the time window in which DMRS transmission is canceled. For example, if the terminal device cancels transmission of uplink DMRS 601 (DMRS (DA)), then during time window T722 (T622) in which uplink DMRS 601 (DMRS (DA)) is scheduled to be transmitted, the terminal device does not transmit an uplink signal.

[0269] Optionally, in another embodiment, when the terminal device cancels sending the uplink DMRS or the base station device cancels sending the downlink DMRS, the data signal is sent during the time window in which the DMRS is canceled. Since the transmission power of the DMRS is higher than the transmission power of the data signal, the transmission of the data signal has a relatively small impact on the reception quality of the DMRS.

[0270] According to the method of the embodiment of the present application, sending data signals in the time window where DMRS is planned to be sent can not only avoid uplink and downlink DMRS collisions, but also increase the signal transmission amount and improve signal transmission efficiency while ensuring the reception quality of DMRS.

[0271] FIG8 is a schematic diagram of uplink and downlink DMRS transmission time windows according to an embodiment of the present application.

[0272] As shown in Figure 8, 810 is a downlink signal (e.g., PDSCH) sent by the base station to the terminal based on the plan shown in Figure 6. 820 is an uplink signal (e.g., PUSCH) sent by the terminal to the base station based on the plan shown in Figure 6.

[0273] Referring to the time domain division in Figure 4 , the time domain is divided horizontally. In 810 and 820 shown in Figure 8 , different line segments in the horizontal direction correspond to different time windows (each time window corresponds to a symbol).

[0274] The time window T811-T818 is the planned T611-T618. The time window T821-T828 is the planned T621-T628.

[0275] In time windows T811, T813, T815, T817, and T818, the base station sends downlink signals S811, S813, S815, S817, and S818 to the terminal device according to the plan shown in Figure 6. In time windows T821, T823, T825, T827, and T828, the terminal device sends uplink signals S821, S823, S825, S827, and S828 to the terminal device according to the plan shown in Figure 6.

[0276] In time window T812, the base station sends a downlink signal S812 to the terminal. T812 is the planned T612, and S812 is the planned S612. S812 carries DMRS602.

[0277] In time window T822, the terminal device cancels the transmission of uplink DMRS601 (DMRS (DA)). In time window T822, the terminal device sends an uplink signal S822 to the base station device. T822 is the planned T622. S822 is a data signal and does not carry DMRS.

[0278] In time window T814, the base station cancels the transmission of downlink DMRS 604. In time window T814, the base station transmits downlink signal S814 to the base station. T814 is the planned T614, S814 is a data signal, and S814 does not carry DMRS.

[0279] In time window T824, the terminal device sends an uplink signal S824 to the base station device. T824 is the planned T624, and S824 is the planned S624. T824 carries DMRS603.

[0280] In time window T816, the base station device sends a downlink signal S816 to the terminal device. T816 is the planned T616, and S816 is the planned S616. T816 carries DMRS606.

[0281] In time window T826, the terminal device cancels the transmission of uplink DMRS 605. In time window T826, the terminal device sends an uplink signal S826 to the base station device. T826 is the planned T626. S826 is a data signal and does not carry DMRS.

[0282] Implementation 2.2.2.1

[0283] Optionally, in one embodiment, when the terminal device cancels sending uplink DMRS or the base station device cancels sending downlink DMRS, the data signal planned to be sent after the canceled DMRS is sent in advance in the time window for canceling sending of the DMRS.

[0284] For example, the base station device sends S811 in the time window T811, and S811 is the planned S611 (data signal).

[0285] The base station device sends S812 in the time window T812, where S812 is the planned S612 (carrying DMRS602).

[0286] The base station device sends S813 in the time window T813, and S813 is the planned S613 (data signal).

[0287] In time window T814, the base station cancels the transmission of downlink DMRS 604. In time window T814, the base station sends S615 in advance, which was scheduled to be sent at T615. That is, the base station sends S814 in time window T814, and S814 is the planned S615 (data signal).

[0288] Since S615 is sent in advance at T814, the subsequently sent data signals are also sent in advance.

[0289] The base station device sends S815 in the time window T815, and S815 is the planned S617 (data signal).

[0290] The base station device sends S816 in the time window T816, and S816 is the planned S616 (carrying DMRS606).

[0291] The base station device sends S817 in the time window T817, and S817 is the planned S618 (data signal).

[0292] The base station device sends S818 in the time window T818. S818 is the data signal planned to be sent after S618.

[0293] The terminal device sends S821 in the time window T821, and S821 is the planned S621 (data signal).

[0294] In time window T822, the terminal device cancels the transmission of uplink DMRS601 (DMRS (DA)). In time window T822, the terminal device sends S623 in advance, which was scheduled to be sent at T623. That is, the terminal device sends S822 in time window T822, and S822 is the planned S623 (data signal).

[0295] Since S623 is sent in advance at T822, the subsequently sent data signals are also sent in advance.

[0296] The terminal device sends S823 in the time window T823, and S823 is the planned S625 (data signal).

[0297] The terminal device sends S824 in the time window T824, and S824 is the planned S624 (carrying DMRS603).

[0298] The terminal device sends S825 in the time window T825, and S825 is the planned S627 (data signal).

[0299] The terminal device sends S826 in the time window T826, and S826 is the planned S628 (data signal).

[0300] The terminal device sends S827 and S828 in time windows T827 and T828. S827 and S828 are the data signals planned to be sent after S628.

[0301] Implementation 2.2.2.2

[0302] Optionally, in one embodiment, when the terminal device cancels sending the uplink DMRS or the base station device cancels sending the downlink DMRS, other data signals other than the data signals that were scheduled to be sent are sent during the time window in which the DMRS transmission is canceled. For example, data signals that implement additional functions; for example, backup signals for the data signals that were scheduled to be sent; and for example, verification signals for the data signals that were scheduled to be sent.

[0303] For example, the base station device sends S811 in the time window T811, and S811 is the planned S611 (data signal).

[0304] The base station device sends S812 in the time window T812, where S812 is the planned S612 (carrying DMRS602).

[0305] The base station device sends S813 in the time window T813, and S813 is the planned S613 (data signal).

[0306] In time window T814, the base station cancels the transmission of downlink DMRS 604. In time window T814, the base station transmits S814, which is a data signal other than planned S611, S613, S615, S617, and S618.

[0307] The base station device sends S815 in the time window T815, and S815 is the planned S615 (data signal).

[0308] The base station device sends S816 in the time window T816, and S816 is the planned S616 (carrying DMRS606).

[0309] The base station device sends S817 in the time window T817, and S817 is the planned S617 (data signal).

[0310] The base station device sends S818 in the time window T818, and S818 is the planned S618 (data signal).

[0311] The terminal device sends S821 in the time window T821, and S821 is the planned S621 (data signal).

[0312] In time window T822, the terminal device cancels the transmission of uplink DMRS601 (DMRS (DA)). In time window T822, the terminal device transmits S822, which is a data signal other than the planned S621, S623, S625, S627, and S628.

[0313] The terminal device sends S823 in the time window T823, and S823 is the planned S623 (data signal).

[0314] The terminal device sends S824 in the time window T824, and S824 is the planned S624 (carrying DMRS603).

[0315] The terminal device sends S825 in the time window T825, and S825 is the planned S625 (data signal).

[0316] The terminal device sends S826 in the time window T826. S826 is a data signal other than the planned S621, S623, S625, S627, and S628.

[0317] The terminal device sends S827 and S828 in time windows T827 and T828. S827 and S828 are the planned S627 and S628 (data signals).

[0318] Implementation 2.3

[0319] Optionally, in one embodiment, if the uplink and downlink DMRSs collide in the time domain as planned, the transmission of the DMRS with a lower priority is canceled according to the priority of the uplink and downlink DMRSs.

[0320] Specifically, the network device 100 plans to send DMRS (DA) in the time window TA, and the network device 110 plans to send DMRS (DB) in the time window TB. The time window TA collides with the time window TB.

[0321] Optionally, in one embodiment, if the priority of DMRS (DA) is lower than that of DMRS (DB), then in S201 , the network device 100 cancels sending DMRS (DA).

[0322] Optionally, in another embodiment, if the priority of DMRS (DA) is higher than that of DMRS (DB), then in S202 , the network device 110 cancels sending DMRS (DB).

[0323] FIG9 is a schematic diagram showing a planned transmission time window of uplink and downlink DMRS according to an embodiment of the present application.

[0324] As shown in Figure 9, 910 is a downlink signal (eg, PDSCH) that the base station device plans to send to the terminal device, and 920 is an uplink signal (eg, PUSCH) that the terminal device plans to send to the base station device.

[0325] 910 is used for enhanced mobile broadband (eMBB), and 920 is used for ultra-reliable and low-latency communications (uRLLC).

[0326] The eMBB scenario is designed for high-capacity, high-speed broadband data services, aiming to provide users with a faster and more stable wireless broadband connection experience. The key feature of eMBB is its high-speed data transmission, making it suitable for large-capacity data transmission such as high-definition video, virtual reality, cloud gaming, and downloads. The uRLLC scenario is designed to meet the demand for low-latency and high-reliability communications in applications such as real-time control, medical care, and autonomous driving. uRLLC's key features are extremely low latency and high reliability, ensuring the reliability and stability of real-time and critical applications.

[0327] In the embodiment shown in FIG9 , the uRLLC scenario has a higher priority than the eMBB scenario.

[0328] Referring to the time domain and frequency domain division shown in Figure 4 , the time domain is divided horizontally. In 910 and 920 shown in Figure 9 , different line segments in the horizontal direction correspond to different time windows (each time window corresponds to a symbol).

[0329] As shown in Figure 9, 910 contains eight symbols (S911-S918), each corresponding to eight time windows (T911-T918). 920 contains eight symbols (S921-S928), each corresponding to eight time windows (T921-T928). T911 collides with T921, T912 collides with T922, T913 collides with T923, T914 collides with T924, T915 collides with T925, T916 collides with T926, T917 collides with T927, and T918 collides with T928. This means that after the CP removal operation, T911-T918 are aligned with T921-T928.

[0330] The base station device plans to send data signals to the terminal device at T911, T913, T914, T916, T917, and T818. That is, S911, S913, S914, S916, S917, and S918 are data signals.

[0331] The base station device plans to carry downlink DMRS 902 in S912 and carry downlink DMRS 904 in S915.

[0332] The terminal device plans to send data signals to the terminal device at T921, T923, T924, T925, T927, and T928. That is, S921, S923, S924, S925, S927, and S928 are data signals.

[0333] The terminal device plans to carry downlink DMRS901 in S922 and downlink DMRS903 in S926.

[0334] If the terminal device and the base station device send uplink and downlink signals according to the plan shown in FIG9 , the uplink and downlink DMRS (DMRS901 and DMRS902) will collide in the time domain.

[0335] To avoid uplink and downlink DMRS collision, the terminal device or base station device schedules the transmission of uplink DMRS or downlink DMRS and cancels the transmission of the DMRS with lower priority among the uplink DMRS and downlink DMRS.

[0336] Specifically, in the embodiment shown in FIG9 , the uRLLC scenario (use scenario 920 ) has a higher priority than the eMBB scenario (use scenario 910 ), so the base station device cancels the transmission of DMRS 902 (DMRS (DB)).

[0337] FIG10 is a schematic diagram of uplink and downlink DMRS transmission time windows according to an embodiment of the present application.

[0338] As shown in Figure 10, 1010 is a downlink signal (e.g., PDSCH) sent by the base station to the terminal device based on the plan shown in Figure 9. 1020 is an uplink signal (e.g., PUSCH) sent by the terminal device to the base station based on the plan shown in Figure 9.

[0339] 1010a is another implementation method of the downlink signal sent by the base station device to the terminal device based on the plan shown in Figure 9.

[0340] 1010 is used for enhanced mobile broadband (eMBB), and 1020 is used for ultra-reliable and low-latency communications (uRLLC).

[0341] The time window T1011-T1018 is the planned T911-T918. The time window T1021-T1028 is the planned T921-T928.

[0342] The base station sends S1011, S1013, S1014, S1016, S1017, and S1018 in time windows T1011, T1013, T1014, T1016, T1017, and T1018. S1011, S1013, S1014, S1016, S1017, and S1018 are data signals.

[0343] The base station device sends S1015 in the time window T1015. S1015 is S915, which carries the downlink DMRS904.

[0344] The terminal device sends S1021, S1023, S1024, S1025, S1027, and S1028 in time windows T1021, T1023, T1024, T1025, T1027, and T1028. S1021, S1023, S1024, S1025, S1027, and S1028 are data signals.

[0345] The terminal device sends S1026 in the time window T1026. S1026 is S926, which carries uplink DMRS903.

[0346] In the embodiment shown in FIG9 , the uRLLC scenario (use scenario 920) has a higher priority than the eMBB scenario (use scenario 910). Therefore, at T1012, the base station device cancels the transmission of DMRS 902 (DMRS (DB)). At T1022, the terminal device transmits S1022 according to the plan shown in FIG9 . S1022 is S922, which carries uplink DMRS 901. S1021, S1023, S1024, S1025, S1027, and S1028 are S921, S923, S924, S925, S927, and S928.

[0347] Implementation 2.3.1

[0348] Referring to the embodiment shown in Figure 7, optionally, as shown in 1010 in Figure 10, the base station device does not send a downlink signal in the time window T1012, and S1011, S1013, S1014, S1016, S1017, and S1018 are S911, S913, S914, S916, S917, and S918.

[0349] Implementation 2.3.2

[0350] Referring to the embodiment shown in FIG8 , optionally, as shown in 1010a in FIG10 , the base station device sends a downlink data signal S1012 in a time window T1012 .

[0351] Implementation 2.3.2.1

[0352] Optionally, S1012 is the planned early transmission of the data signal, S1011, S1012, S1013, S1014, S1016, S1017 are S911, S913, S914, S916, S917, S918; S1018 is the downlink data signal planned to be sent after S918.

[0353] Implementation 2.3.2.2

[0354] Optionally, S1012 is a data signal other than the data signal planned to be sent, S1011, S1013, S1014, S1016, S1017, and S1018 are S911, S913, S914, S916, S917, and S918; S1012 is a data signal other than S911, S913, S914, S916, S917, and S918.

[0355] Implementation 2.4

[0356] Optionally, in one embodiment, if the uplink and downlink DMRS collide in the time domain as planned, the total number of uplink DMRS and downlink DMRS sent in the first time period and the second time period are compared, and the sending of a type of DMRS with a higher total number planned to be sent among the uplink and downlink DMRS that collide in the time domain is canceled.

[0357] Specifically, the network device 100 plans to send DMRS (DA) in the time window TA, and the network device 110 plans to send DMRS (DB) in the time window TB. The time window TA collides with the time window TB.

[0358] The total number of DMRSs sent and planned to be sent by the network device 100 in the first time period (first number) is calculated, and the total number of DMRSs sent and planned to be sent by the network device 110 in the second time period (second number) is calculated.

[0359] If the first number is greater than the second number, then in S201, the network device 100 cancels sending the DMRS (DA). If the second number is greater than the first number, then in S202, the network device 110 cancels sending the DMRS (DB).

[0360] In the embodiment of the present application, the first time period includes a time window TA, and the second time period includes a time window TB.

[0361] The embodiment of the present application does not impose any specific restrictions on the specific durations of the first time period and the second time period. Those skilled in the art can define the durations of the first time period and the second time period according to actual needs.

[0362] Optionally, in one embodiment, the first time period and the second time period have the same duration, and the position of the time window TA in the first time period is consistent with the position of the time window TB in the second time period.

[0363] Optionally, in another embodiment, the durations of the first time period and the second time period are inconsistent, and / or the position of the time window TA in the first time period is inconsistent with the position of the time window TB in the second time period.

[0364] Optionally, in one embodiment, the first time period (or the second time period) further includes a time period that has already passed before the time window TA (or the time window TB). The DMRS sent by the network device 100 (or the network device 110) in the first time period (or the second time period) includes the DMRS planned to be sent in the time window TA (or the time window TB) and the DMRS sent in the time period that has already passed included in the first time period (or the second time period).

[0365] Optionally, in one embodiment, the first time period (or the second time period) further includes an unexpired time period after the time window TA (or the time window TB). The DMRS sent by the network device 100 (or the network device 110) in the first time period (or the second time period) includes the DMRS planned to be sent in the time window TA (or the time window TB), and the DMRS planned to be sent in the unexpired time period included in the current time period after the time window TA (or the time window TB).

[0366] Optionally, in one embodiment, the first time period (or the second time period) further includes a time period that has already passed before the time window TA (or the time window TB), and a time period that has not yet passed after the time window TA (or the time window TB). The DMRS sent by the network device 100 (or the network device 110) in the first time period (or the second time period) includes the DMRS sent in the time period that has already passed included in the first time period (or the second time period), the DMRS planned to be sent in the time window TA (or the time window TB), and the DMRS planned to be sent in the time period that has not yet passed included in the first time period (or the second time period) after the time window TA (or the time window TB).

[0367] Optionally, in one embodiment, the start time of the first time period (or the second time period) is a time node of a first preset duration before the time window TA (or the time window TB). The end time of the first time period (or the second time period) is the end time of the time window TA (or the time window TB).

[0368] Optionally, in one embodiment, the start time of the first time period (or the second time period) is the start time of the time window TA (or the time window TB). The end time of the first time period (or the second time period) is a time node of a second preset duration after the time window TA (or the time window TB).

[0369] Optionally, in one embodiment, the start time of the first time period (or the second time period) is a time node of a first preset duration before the time window TA (or the time window TB). The end time of the first time period (or the second time period) is a time node of a second preset duration after the time window TA (or the time window TB).

[0370] Optionally, in one embodiment, the first time period (or the second time period) includes a time window TA (or a time window TB), and a first preset number of time windows before the time window TA (or the time window TB).

[0371] Optionally, in one embodiment, the first time period (or the second time period) includes a time window TA (or a time window TB), and a second preset number of time windows after the time window TA (or the time window TB).

[0372] Optionally, in one embodiment, the first time period (or the second time period) includes a time window TA (or a time window TB), a first preset number of time windows before the time window TA (or the time window TB), and a second preset number of time windows after the time window TA (or the time window TB).

[0373] Optionally, in one embodiment, the time window TA (or time window TB) is a plurality of time windows corresponding to a complete control signaling or a complete data segment currently transmitted by the network device 100 (or network device 110).

[0374] The time period corresponding to the complete control signaling or data segment currently transmitted by network device 100 to network device 110 includes at least time window TA. The time period corresponding to the complete control signaling or data segment currently transmitted by network device 110 to network device 100 includes at least time window TB.

[0375] For example, assume that a complete control signaling needs to be transmitted using 8 time windows.

[0376] If, during the process of network device 100 sending a control signaling, time window TA is the second time window for sending the control signaling, then the first time period includes one time window before time window TA, time window TA, and six time windows after time window TA (the first time period includes a total of eight time windows).

[0377] If, during the process of network device 110 sending a control signaling, time window TB is the fourth time window for sending the control signaling, then the second time period includes the three time windows before time window TB, time window TB, and the four time windows after time window TA (the first time period includes a total of eight time windows).

[0378] FIG11 is a schematic diagram of a planned transmission time window of uplink and downlink DMRS according to an embodiment of the present application.

[0379] As shown in FIG11 , 1110 is a downlink signal (eg, PDSCH) that the base station device plans to send to the terminal device, and 1120 is an uplink signal (eg, PUSCH) that the terminal device plans to send to the base station device.

[0380] Referring to the time domain and frequency domain division shown in Figure 4 , the time domain is divided horizontally. In 1110 and 1120 shown in Figure 11 , different line segments in the horizontal direction correspond to different time windows (each time window corresponds to a symbol).

[0381] As shown in Figure 11, 1110 contains eight symbols (S1111-S1118), each corresponding to eight time windows (T1111-T1118). 1120 contains eight symbols (S1121-S1128), each corresponding to eight time windows (T1121-T1128). T1111 collides with T1121, T1112 collides with T1122, T1113 collides with T1123, T1114 collides with T1124, T1115 collides with T1125, T1116 collides with T1126, T1117 collides with T1127, and T1118 collides with T1128. It can be considered that after the CP removal operation, T1111-T1118 are aligned with T1121-T1128.

[0382] The base station plans to send S1111 to S1118 to the terminal device from T1111 to T1118. S1111, S1114, S1116, and S1118 are data signals. S1112 carries downlink DMRS 1102, S1113 carries downlink DMRS 1104, S1115 carries downlink DMRS 1105, and S1117 carries downlink DMRS 1106.

[0383] The terminal device plans to send data signals to the terminal device at T1121, T1123, T1124, T1125, T1127, and T1128. That is, S1121, S1123, S1124, S1125, S1127, and S1128 are data signals.

[0384] The terminal device plans to carry uplink DMRS1101 in S1122 and uplink DMRS1103 in S1126.

[0385] If the terminal device and the base station device send uplink and downlink signals according to the plan shown in FIG11 , the uplink and downlink DMRS (DMRS1101 and DMRS1102) will collide in the time domain.

[0386] In order to avoid uplink and downlink DMRS collision, the terminal device or the base station device schedules the transmission of the uplink DMRS or the downlink DMRS.

[0387] Specifically, the first time period and the second time period correspond to the time windows corresponding to 1110 and 1120 respectively (or the second time period and the first time period correspond to the time windows corresponding to 1110 and 1120 respectively).

[0388] In the time window corresponding to calculation 1110 , the total number of downlink DMRSs that the base station device plans to send is 4.

[0389] Calculate that in the time window corresponding to 1120, the total number of uplink DMRSs that the terminal device plans to send is 2.

[0390] Therefore, the base station device cancels the transmission of DMRS 1102 .

[0391] FIG12 is a schematic diagram of uplink and downlink DMRS transmission time windows according to an embodiment of the present application.

[0392] As shown in Figure 12, 1210 is a downlink signal (e.g., PDSCH) sent by the base station to the terminal device based on the plan shown in Figure 11. 1220 is an uplink signal (e.g., PUSCH) sent by the terminal device to the base station based on the plan shown in Figure 11.

[0393] 1210a is another implementation method of the downlink signal sent by the base station device to the terminal device based on the plan shown in Figure 11.

[0394] The time window T1211-T1218 is the planned T1111-T1118. The time window T1221-T1228 is the planned T1121-T1128.

[0395] The base station sends S1211, S1213, S1214, S1215, S1216, S1217, and S1218 to the terminal device at T1211, T1213, T1214, T1215, T1216, T1217, and T1218. S1211, S1214, S1216, and S1218 are data signals. S1213 carries downlink DMRS 1104, S1215 carries downlink DMRS 1105, and S1217 carries downlink DMRS 1106.

[0396] The terminal device sends S1221 to S1228 in the time window T1221 to T1228. S1221, S1223, S1224, S1225, S1227, and S1228 are S1121, S1123, S1124, S1125, S1127, and S1128.

[0397] The terminal device sends S1226 in the time window T1226. S1226 is S1126, which carries the uplink DMRS1103.

[0398] Because in the embodiment shown in Figure 11, the total number of downlink DMRSs planned to be sent by the base station device in the time window corresponding to 1110 is higher than the total number of uplink DMRSs planned to be sent by the terminal device in the time window corresponding to 1120.

[0399] Therefore, in T1212, the base station device cancels the transmission of DMRS 1202. In T1222, the terminal device transmits S1222 according to the plan shown in FIG11. S1222 is S1122, which carries uplink DMRS 1101.

[0400] Implementation 2.4.1

[0401] Referring to the embodiment shown in FIG7 , optionally, as shown in 1210 of FIG12 , the base station device does not send a downlink signal in the time window T1212 , and S1211 , S1214 , S1216 , and S1218 are S1111 , S1114 , S1116 , and S1118 .

[0402] Implementation 2.4.2

[0403] Referring to the embodiment shown in FIG8 , optionally, as shown in 1210 a of FIG12 , the base station device sends a downlink data signal S1212 in a time window T1212 .

[0404] Implementation 2.4.2.1

[0405] Optionally, S1212 is the planned early transmission of the data signal, S1211, S1212, S1214, S1216 are S1111, S1114, S1116, S1118; S1218 is the downlink data signal sent after the planned S1118.

[0406] Implementation 2.4.2.2

[0407] Optionally, S1212 is a data signal other than the data signal planned to be sent, S1211, S1214, S1216, and S1218 are S1111, S1114, S1116, and S1118; S1212 is a data signal other than S1111, S1114, S1116, and S1118.

[0408] Implementation 3

[0409] In one embodiment, for the same terminal device, if uplink and downlink DMRSs are scheduled to appear in two time windows where there is a collision, the transmission of the uplink DMRS or downlink DMRS is scheduled, and the time window for transmitting the uplink DMRS or downlink DMRS is changed. This allows only the uplink DMRS or downlink DMRS to be transmitted in the two time windows where there is a collision; and the downlink DMRS or uplink DMRS is transmitted in a time window other than the two time windows where there is a collision, so that there is no collision in the time domain between the uplink and downlink DMRSs.

[0410] Specifically, the network device 100 plans to send DMRS (DA) in the time window TA, and the network device 110 plans to send DMRS (DB) in the time window TB. The time window TA collides with the time window TB.

[0411] Optionally, in one embodiment, in S202, the network device 110 sends DMRS (DB) in time window TB. In S201, the network device 100 schedules the sending of DMRS (DA) and changes the time window for sending DMRS (DA), including: not sending DMRS (DA) in time window TA, sending DMRS (DA) in time window TC, and there is no collision between time window TA and time window TB.

[0412] Optionally, in another embodiment, in S201, the network device 100 sends DMRS (DA) in time window TA. In S202, the network device 110 schedules the sending of DMRS (DB) and changes the time window for sending DMRS (DB), including: not sending DMRS (DB) in time window TB, sending DMRS (DB) in time window TC, and there is no collision between time window TC and time window TB.

[0413] Implementation 3.1

[0414] Optionally, in one embodiment, a device type of a network device for executing the scheduled DMRS transmission is pre-specified, so that when the time window for transmitting the DMRS needs to be changed, a device is selected from network device 100 and network device 110 according to the pre-specified device type to change its own time window for transmitting the DMRS.

[0415] For example, the network device 100 is a terminal device, and the network device 110 is a base station device. It is pre-specified that the terminal device schedules the DMRS.

[0416] When network device 100 plans to send DMRS (DA) in time window TA, and network device 110 plans to send DMRS (DB) in time window TB, and there is a collision between time window TA and time window TB, network device 100 is selected from network device 100 and network device 110, and network device 100 changes the time window for sending DMRS (DA).

[0417] For another example, the network device 100 is a terminal device, and the network device 110 is a base station device. It is pre-specified that the base station device schedules the transmission of the DMRS.

[0418] When network device 100 plans to send DMRS (DA) in time window TA, and network device 110 plans to send DMRS (DB) in time window TB, and there is a collision between time window TA and time window TB, network device 110 is selected from network device 100 and network device 110, and network device 110 changes the time window for sending DMRS (DB).

[0419] FIG13 is a schematic diagram showing a planned transmission time window of uplink and downlink DMRS according to an embodiment of the present application.

[0420] As shown in FIG13 , 1310 is a downlink signal (eg, PDSCH) that the base station device plans to send to the terminal device, and 1320 is an uplink signal (eg, PUSCH) that the terminal device plans to send to the base station device.

[0421] Referring to the time domain and frequency domain division shown in Figure 4 , the time domain is divided horizontally. In 1310 and 1320 shown in Figure 13 , different line segments in the horizontal direction correspond to different time windows (each time window corresponds to a symbol).

[0422] As shown in Figure 13, 1310 contains eight symbols (S1311-S1318), each corresponding to eight time windows (T1311-T1318). 1320 contains eight symbols (S1321-S1328), each corresponding to eight time windows (T1321-T1328). T1311 collides with T1321, T1312 collides with T1322, T1313 collides with T1323, T1314 collides with T1324, T1315 collides with T1325, T1316 collides with T1326, T1317 collides with T1327, and T1318 collides with T1328. It can be considered that after the CP removal operation, T1311-T1318 are aligned with T1321-T1328.

[0423] The base station plans to send S1311 to S1318 to the terminal device at T1311 to T1318. S1311, S1313, S1315, S1317, and S1318 are data signals. S1312 carries downlink DMRS 1302, S1314 carries downlink DMRS 1304, and S1316 carries downlink DMRS 1306.

[0424] The terminal device plans to send S1321 to S1328 to the terminal device at T1321 to T1328. S1321, S1323, S1325, S1327, and S1328 are data signals. S1322 carries downlink DMRS 1301, S1324 carries downlink DMRS 1303, and S1326 carries downlink DMRS 1305.

[0425] If the terminal device and the base station device send uplink and downlink signals according to the plan shown in FIG13 , the uplink and downlink DMRS (DMRS1301 and DMRS1302, DMRS1303 and DMRS1304, DMRS1305 and DMRS1306) will collide in the time domain.

[0426] The device type of the network device that executes DMRS scheduling is pre-specified as a terminal device.

[0427] In order to avoid collision of uplink and downlink DMRS, the terminal device schedules the transmission of uplink DMRS and changes the transmission time windows of DMRS1301, DMRS1303, and DMRS1305.

[0428] FIG14 is a schematic diagram of uplink and downlink DMRS transmission time windows according to an embodiment of the present application.

[0429] As shown in Figure 14, 1410 is a downlink signal (e.g., PDSCH) sent by the base station to the terminal device based on the plan shown in Figure 13. 1420 is an uplink signal (e.g., PUSCH) sent by the terminal device to the base station based on the plan shown in Figure 13.

[0430] 1420a is another implementation of the uplink signal sent by the terminal device to the base station device based on the plan shown in Figure 13.

[0431] The time window T1411-T1418 is the planned T1311-T1318. The time window T1421-T1428 is the planned T1321-T1328.

[0432] The base station sends S1411-S1418 to the terminal device at T1411-T1418. S1411-S1418 are the planned S1311-S1318.

[0433] Because the device type of the network device that executes DMRS scheduling is pre-specified as a terminal device.

[0434] The terminal device sends S1421 and S1428 in time windows T1421 and T1428. S1421 and S1428 are data signals.

[0435] The terminal device sends S1423, S1425, and S1427 in time windows T1423, T1425, and T1427. S1423 is S1322, which carries uplink DMRS1301; S1425 is S1324, which carries uplink DMRS1303; and S1427 is S1326, which carries uplink DMRS1305.

[0436] Implementation 3.1.1

[0437] Optionally, as shown in 1420 of Figure 14, the terminal device does not send an uplink signal in time windows T1422, T1424, and T1426, S1421 is S1321, and S1428 is one of S1323, S1325, S1327, and S1328.

[0438] Implementation 3.1.2

[0439] Optionally, as shown in 1420a of FIG14 , the terminal device sends uplink data signals S1422 , S1424 , and S1426 in time windows T1422 , T1424 , and T1426 .

[0440] In one embodiment, S1422, S1424, and S1426 are the planned S1323, S1325, and S1327.

[0441] In implementation 3.1, when changing the DMRS transmission time window, a backward offset is used to postpone the DMRS transmission time window. Alternatively, in another embodiment, when changing the DMRS transmission time window, a forward offset is used to advance the DMRS transmission time window. For example, the terminal device transmits DMRS 1301, DMRS 1303, and DMRS 1305 in time windows T1421, T1423, and T1425.

[0442] Optionally, in another embodiment, when changing the DMRS transmission time window, a mixed method of forward offset and backward offset is adopted to advance the transmission time window of a part of the DMRS and postpone the transmission time window of another part of the DMRS.

[0443] Implementation 3.2

[0444] Optionally, in one embodiment, when the uplink and downlink time-frequency resources are consistent, if the uplink and downlink DMRS collide in the time domain as planned, the total number of uplink DMRS and downlink DMRS is compared, and the sending time window of the type of DMRS with a higher total number planned to be sent among the uplink and downlink DMRS that collide in the time domain is changed.

[0445] Specifically, the network device 100 plans to send DMRS (DA) in the time window TA, and the network device 110 plans to send DMRS (DB) in the time window TB. The time window TA collides with the time window TB.

[0446] The total number of DMRSs sent and planned to be sent by network device 100 in the third time period (third number) is calculated, and the total number of DMRSs sent and planned to be sent by network device 110 in the fourth time period (fourth number) is calculated.

[0447] If the fourth number is greater than the third number, then in S202, the network device 110 sends DMRS (DB) in time window TB. In S201, the network device 100 schedules the sending of DMRS (DA), changes the time window for sending DMRS (DA), does not send DMRS (DA) in time window TA, sends DMRS (DA) in time window TC, and does not collide with time window TA and time window TB.

[0448] If the third number is greater than the fourth number, then in S201, the network device 100 sends DMRS (DA) in the time window TA. In S202, the network device 110 schedules the sending of DMRS (DB) and changes the time window for sending DMRS (DB), including: not sending DMRS (DB) in the time window TB, sending DMRS (DB) in the time window TC, and there is no collision between the time window TC and the time window TB.

[0449] In the embodiment of the present application, the third time period includes a time window TA, and the fourth time period includes a time window TB.

[0450] The embodiments of the present application do not impose any specific restrictions on the specific durations of the third and fourth time periods. Those skilled in the art can define the durations of the third and fourth time periods according to actual needs. The setting of the third time period can refer to the first time period, and the setting of the fourth time period can refer to the second time period.

[0451] FIG15 is a schematic diagram of a planned transmission time window of uplink and downlink DMRS according to an embodiment of the present application.

[0452] As shown in FIG15 , 1510 is a downlink signal (eg, PDSCH) that the base station device plans to send to the terminal device, and 1120 is an uplink signal (eg, PUSCH) that the terminal device plans to send to the base station device.

[0453] Referring to the time domain and frequency domain division shown in Figure 4 , the time domain is divided horizontally. In 1510 and 1520 shown in Figure 15 , different line segments in the horizontal direction correspond to different time windows (each time window corresponds to a symbol).

[0454] As shown in Figure 15 , 1510 contains eight symbols (S1511-S1518), each corresponding to eight time windows (T1511-T1518). 1520 contains eight symbols (S1521-S1528), each corresponding to eight time windows (T1521-T1528). T1511 collides with T1521, T1512 collides with T1522, T1513 collides with T1523, T1514 collides with T1524, T1515 collides with T1525, T1516 collides with T1526, T1517 collides with T1527, and T1518 collides with T1528. It can be considered that after the CP removal operation, T1511-T1518 are aligned with T1521-T1528.

[0455] The base station plans to send S1511 to S1518 to the terminal device at T1511 to T1518. S1511, S1514, S1515, S1116, S1117, and S1118 are data signals. S1512 carries downlink DMRS 1502, and S1513 carries downlink DMRS 1503.

[0456] The terminal device plans to send S1521 to S1528 to the terminal device at T1521 to T1528. S1521, S1523, S1524, S1525, S1526, S1527, and S1528 are data signals. S1522 carries uplink DMRS 1501.

[0457] If the terminal device and the base station device send uplink and downlink signals according to the plan shown in FIG15 , the uplink and downlink DMRS (DMRS1501 and DMRS1502) will collide in the time domain.

[0458] The third time period and the fourth time period correspond to the time windows corresponding to 1510 and 1520 respectively (or the third time period and the fourth time period correspond to the time windows corresponding to 1510 and 1520 respectively).

[0459] In the time window corresponding to calculation 1510 , the total number of downlink DMRSs that the base station device plans to send is 2.

[0460] Calculate that in the time window corresponding to 1520, the total number of uplink DMRSs that the terminal device plans to send is 1.

[0461] Therefore, the time window for sending DMRS 1501 is changed by the terminal device.

[0462] FIG16 is a schematic diagram of uplink and downlink DMRS transmission time windows according to an embodiment of the present application.

[0463] As shown in Figure 16, 1610 is a downlink signal (e.g., PDSCH) sent by the base station to the terminal device based on the plan shown in Figure 15. 1620 is an uplink signal (e.g., PUSCH) sent by the terminal device to the base station based on the plan shown in Figure 15.

[0464] 1620a is another implementation method of the uplink signal sent by the terminal device to the base station device based on the plan shown in Figure 15.

[0465] The time window T1611-T1618 is the planned T1611-T1618. The time window T1621-T1628 is the planned T1621-T1628.

[0466] Since the total number of downlink DMRSs that the base station device plans to send in the time window corresponding to 1510 is greater than the total number of uplink DMRSs that the terminal device plans to send in the time window corresponding to 1520, the terminal device changes the time window for sending DMRS 1501.

[0467] The base station sends S1611-S1618 to the terminal device at T1611-T1618. S1611-S1618 are the planned S1511-S1518.

[0468] The terminal device sends S1621, S1623, S1624, S1625, S1626, S1627, and S1628 in time windows T1621, T1623, T1624, T1625, T1626, T1627, and T1628. S1621 and S1623 are data signals.

[0469] The terminal device sends DMRS 1501 in a time window among T1624, T1625, T1626, T1627, and T1628. For example, S1624 carries DMRS 1501, and S1625, S1626, S1627, and S1628 are data signals.

[0470] Implementation 3.2.1

[0471] Optionally, in one embodiment, as shown in 1620 of FIG16 , the terminal device does not send an uplink signal in the time window T1622.

[0472] For example, S1624 carries DMRS1501, and S1625, S1626, S1627, and S1628 are S1524, S1525, S1526, and S1527.

[0473] Implementation 3.2.2

[0474] Optionally, in one embodiment, as shown in 1620a of FIG16 , the terminal device sends an uplink data signal S1622 in the time window T1622 .

[0475] In one embodiment, S1624 carries DMRS1501, and S1621, S1622, S1623, S1625, S1626, S1627, and S1628 are S1521, S1523, S1524, S1525, S1526, S1527, and S1528.

[0476] In implementation 3.2, when changing the DMRS transmission time window, a backward offset is used to postpone the DMRS transmission time window. Alternatively, in another embodiment, when changing the DMRS transmission time window, a forward offset is used to advance the DMRS transmission time window. For example, the terminal device transmits DMRS 1501 in time window T1621.

[0477] Optionally, in another embodiment, when changing the DMRS transmission time window, a mixed method of forward offset and backward offset is adopted to advance the transmission time window of a part of the DMRS and postpone the transmission time window of another part of the DMRS.

[0478] Implementation 3.3

[0479] Optionally, in one embodiment, when the uplink and downlink time-frequency resources are inconsistent, if the uplink and downlink DMRS collide in the time domain as planned, the time-frequency resources of the terminal device and the base station device are compared, and the sending time window of the DMRS with higher time-frequency resources among the uplink and downlink DMRS that collide in the time domain is changed.

[0480] Specifically, the network device 100 plans to send DMRS (DA) in the time window TA, and the network device 110 plans to send DMRS (DB) in the time window TB. The time window TA collides with the time window TB.

[0481] If the time-frequency resources of network device 100 are higher than those of network device 110, then in S202, network device 110 transmits DMRS (DB) in time window TB. In S201, network device 100 schedules the transmission of DMRS (DA) and changes the time window for transmitting DMRS (DA), so that DMRS (DA) is not transmitted in time window TA and DMRS (DA) is transmitted in time window TC, and there is no collision between time window TA and time window TB.

[0482] Optionally, in one embodiment, when DMRS (DA) is sent in the time window TC, the symbol used to carry DMRS (DA) is a symbol of a non-simultaneous and non-co-frequency area of ​​the network device 100 and the network device 110 .

[0483] If the time-frequency resources of network device 100 are lower than those of network device 110, then in S201, network device 100 transmits DMRS (DA) in time window TA. In S202, network device 110 schedules the transmission of DMRS (DB) and changes the time window for transmitting DMRS (DB), including: not transmitting DMRS (DB) in time window TB, transmitting DMRS (DB) in time window TC, and there is no collision between time window TC and time window TB.

[0484] Optionally, in one embodiment, the time-frequency resources are determined by the number of symbols sent in a corresponding time period. Specifically, in a corresponding time period, the higher the number of symbols sent, the higher the time-frequency resources.

[0485] Specifically, the network device 100 plans to send DMRS (DA) in the time window TA, and the network device 110 plans to send DMRS (DB) in the time window TB. The time window TA collides with the time window TB.

[0486] The total number of symbols sent and planned to be sent by the network device 100 in the fifth time period (fifth number) is calculated, and the total number of symbols sent and planned to be sent by the network device 110 in the sixth time period (sixth number) is calculated.

[0487] If the fifth number is greater than the sixth number, then in S202, the network device 110 sends DMRS (DB) in time window TB. In S201, the network device 100 schedules the sending of DMRS (DA), changes the time window for sending DMRS (DA), does not send DMRS (DA) in time window TA, sends DMRS (DA) in time window TC, and does not collide with time window TA and time window TB.

[0488] Optionally, in one embodiment, when DMRS (DA) is sent in the time window TC, the symbol used to carry DMRS (DA) is a symbol of a non-simultaneous and non-co-frequency area of ​​the network device 100 and the network device 110 .

[0489] If the sixth number is greater than the fifth number, then in S201, the network device 100 sends DMRS (DA) in the time window TA. In S202, the network device 110 schedules the sending of DMRS (DB) and changes the time window for sending DMRS (DB), including: not sending DMRS (DB) in the time window TB, sending DMRS (DB) in the time window TC, and there is no collision between the time window TC and the time window TB.

[0490] Optionally, in one embodiment, when DMRS (DB) is sent in the time window TC, the symbol used to carry DMRS (DA) is the symbol of the non-simultaneous and non-co-frequency areas of the network device 100 and the network device 110 .

[0491] In the embodiment of the present application, the fifth time period includes a time window TA, and the sixth time period includes a time window TB. Optionally, in one embodiment, the first time period and the second time period have the same duration, and the position of the time window TA in the first time period is consistent with the position of the time window TB in the second time period.

[0492] The embodiments of the present application do not impose any specific restrictions on the specific durations of the first and second time periods. Those skilled in the art can define the durations of the fifth and sixth time periods based on actual needs. The setting of the fifth time period can refer to the first time period, and the setting of the sixth time period can refer to the second time period.

[0493] In communication application scenarios, there may be situations where the TA is outside the CP range.

[0494] For example, FIG17 is a schematic diagram showing a time window for sending and receiving symbols according to an embodiment of the present application.

[0495] In one embodiment, 1701 and 1702 are two consecutive uplink symbols sent by the terminal device to the base station device. The sending time windows (uplink time windows) occupied by 1701 and 1702 are 1711 and 1712 respectively.

[0496] 1703 and 1704 are two consecutive downlink symbols received by the terminal device from the base station device. The receiving time windows (downlink time windows) occupied by 1703 and 1704 are 1713 and 1714 respectively.

[0497] As shown in Figure 17, the sending time windows 1711 and 1712 are not aligned with the receiving time windows 1713 and 1714. There is a timing advance (TA) between the sending time window and the receiving time window.

[0498] As shown in Figure 17, a symbol (1701, 1702, 1703, 1704) includes a cyclic prefix (CP) and a payload, and the TA is outside the CP range. The situation where the TA is outside the CP range is more likely to occur when the cell radius is large.

[0499] When the TA is outside the CP range, even through the CP removal operation, the terminal device side cannot achieve that one receiving symbol is interfered by only one transmitting symbol.

[0500] At this point, the receiving window of the terminal device, which is receiving the payload of one symbol, will be interfered with by the transmission of two symbols. The interference patterns on the base station and the terminal device are different. This can result in no interference between the uplink and downlink DMRS on the terminal device, but interference between the uplink and downlink DMRS on the base station; or vice versa.

[0501] In the case where the TA is outside the CP range, in one embodiment, the DMRS transmission mode is dynamically selected according to the actual arrival of downlink services. The DMRS transmission modes include simultaneous and same-frequency full-duplex, unidirectional downlink, and unidirectional uplink.

[0502] Optionally, in one embodiment, the base station device dynamically selects a DMRS transmission mode according to actual arrival of downlink services.

[0503] Optionally, in one embodiment, the DMRS configurations of the uplink physical channel and the downlink physical channel adopt semi-static independent configuration, and when the uplink physical channel and the downlink physical channel are scheduled simultaneously, a predefined criterion is adopted.

[0504] Optionally, in one embodiment, the DMRS pattern may be modified by downlink control information (DCI), for example, based on a shift of a certain type of pattern.

[0505] Optionally, in one embodiment, uplink DMRS and downlink DMRS are configured simultaneously in one DMRS configuration, that is, DMRS pattern {DL DMRS+UL DMRS}.

[0506] In the above-described implementations 1-3, DMRS transmission is scheduled based on the planned DMRS transmission to avoid uplink and downlink DMRS collisions. Optionally, in one embodiment, the uplink and downlink DMRS transmission method is pre-configured so that the uplink and downlink DMRS transmitted in this manner do not collide. In other words, the method for the terminal device to transmit uplink DMRS and receive downlink DMRS is pre-configured. In other words, the method for the base station device to receive uplink DMRS and transmit downlink DMRS is pre-configured.

[0507] Optionally, in one embodiment, the subcarrier portions used by the uplink DMRS and the subcarrier portions used by the downlink DMRS are preconfigured so that there is no overlap between the subcarrier portions used by the uplink DMRS and the subcarrier portions used by the downlink DMRS. In this way, uplink and downlink DMRS can be multiplexed within a symbol.

[0508] Specifically, as shown in Figure 2, in one embodiment, in S201, DMRS is transmitted based on the first portion of subcarriers; in S202, DMRS is transmitted based on the second portion of subcarriers. There is no overlap between the first portion of subcarriers and the second portion of subcarriers. This ensures that the DMRS transmitted in S201 and the DMRS transmitted in S202 do not collide in the frequency domain, ensuring that uplink and downlink DMRS do not collide.

[0509] Optionally, in one embodiment, the first part of the subcarriers are odd subcarriers, and the second part of the subcarriers are even subcarriers; or, the first part of the subcarriers are even subcarriers, and the second part of the subcarriers are odd subcarriers.

[0510] For example, FIG18 shows a schematic diagram of subcarriers according to an embodiment of the present application.

[0511] As shown in Figure 18, the subcarrier is divided into 12 parts (Z20-Z211) in the frequency domain, Z21, Z23, Z25, Z27, Z29, and Z211 are odd-numbered subcarriers of the subcarrier, and Z20, Z22, Z24, Z26, Z28, and Z210 are even-numbered subcarriers of the subcarrier; alternatively, Z21, Z23, Z25, Z27, Z29, and Z211 are even-numbered subcarriers of the subcarrier, and Z20, Z22, Z24, Z26, Z28, and Z210 are odd-numbered subcarriers of the subcarrier.

[0512] Optionally, in one embodiment, different code division multiplexing groups (CDM groups) are used to pre-configure the subcarriers used by the uplink DMRS and the subcarriers used by the downlink DMRS to be the same, so that the uplink DMRS and the downlink DMRS use different subcarrier parts respectively.

[0513] Specifically, as shown in FIG2 , in one embodiment, in S201, a DMRS is transmitted based on a first code division multiplexing group (CDM group), that is, based on a subcarrier portion (first portion) corresponding to the first code division multiplexing group (CDM group) DMRS is transmitted; in S202, a DMRS is transmitted based on a second code division multiplexing group (CDM group), that is, based on a subcarrier portion (second portion) corresponding to the second code division multiplexing group (CDM group) DMRS is transmitted. The first code division multiplexing group and the second code division multiplexing group are different code division multiplexing groups (CDM groups).

[0514] For example, FIG19 shows a schematic diagram of subcarriers according to an embodiment of the present application.

[0515] As shown in Figure 19, the subcarriers are divided into 12 parts (Z30-Z311) in the frequency domain. CDM groups include three categories: CDM group 0, CDM group 1, and CDM group 1. Each category includes two CDM groups, and each CDM group corresponds to two subcarrier parts.

[0516] Configure CDM group 0 and CDM group 2 for downlink DMRS; configure CDM group 1 for uplink DMRS.

[0517] Optionally, in one embodiment, a subcarrier portion corresponding to uplink and downlink DMRS is allocated in one CDM group.

[0518] Specifically, as shown in Figure 2, in one embodiment, in S201, DMRS is transmitted based on the first subcarrier portion of the code division multiplexing group (CDM group); in S202, DMRS is transmitted based on the second subcarrier portion of the code division multiplexing group (CDM group). The first subcarrier portion and the second subcarrier portion are different subcarrier portions within the code division multiplexing group (CDM group). In this way, the DMRS transmitted in S201 and the DMRS transmitted in S202 will not collide in the frequency domain, ensuring that the uplink and downlink DMRS do not collide.

[0519] Optionally, in one embodiment, a time window for a terminal device to transmit an uplink DMRS and a time window for a base station device to transmit a downlink DMRS are preconfigured so that there is no collision between the time window for transmitting the uplink DMRS and the time window for transmitting the downlink DMRS. That is, a time window for a terminal device to transmit an uplink DMRS and a time window for the terminal device to receive a downlink DMRS are preconfigured. That is, a time window for a base station device to receive an uplink DMRS and a time window for the base station device to transmit a downlink DMRS are preconfigured.

[0520] Specifically, based on FIG2 , in one embodiment, the time window for sending uplink DMRS is configured as time window TAn, and the time window for sending downlink DMRS is configured as time window TBn. There is no collision between time window TAn and time window TBn.

[0521] In S201, an uplink DMRS is sent in time window TAn (or a downlink DMRS is sent in time window TBn); in S202, a downlink DMRS is sent in time window TBn (or an uplink DMRS is sent in time window TAn). Since there is no collision between time window TAn and time window TBn, the DMRS sent in S201 and the DMRS sent in S202 will not collide in the time domain, ensuring that the uplink and downlink DMRS do not collide.

[0522] Optionally, in one embodiment, a time window for a terminal device to transmit an uplink DMRS and a time window for a base station device to transmit a downlink DMRS are pre-configured in units of a time slot. That is, a time window for a terminal device to transmit an uplink DMRS and a time window for a terminal device to receive a downlink DMRS are pre-configured in a time slot. That is, a time window for a base station device to receive an uplink DMRS and a time window for a base station device to transmit a downlink DMRS are pre-configured in a time slot.

[0523] For example, a time slot includes at least a first time window and a second time window, and there is no collision between the first time window and the second time window; the first time window is a pre-designated time window in a time slot for sending DMRS; the second time window is a pre-designated time window in a time slot for receiving DMRS.

[0524] Optionally, in one embodiment, an uplink symbol and a downlink symbol form a whole. A slot includes 14 symbols, and the 14 symbols are divided into 7 groups, each group including 1 uplink symbol and 1 downlink symbol.

[0525] That is, one time slot contains 14 consecutive time windows, the 14 consecutive time windows contain 7 time window groups, and each time window group contains two consecutive time windows.

[0526] It is pre-specified that one of the seven time window groups is the first time window group; and it is pre-specified that the first time window of the first time window group is the first time window, and the second time window of the first time window group is the second time window; or, it is pre-specified that the first time window of the first time window group is the second time window, and the second time window of the first time window group is the first time window.

[0527] The pre-designated first time window is a time window for sending a DMRS; the pre-designated second time window is a time window for receiving a DMRS.

[0528] Optionally, in one embodiment, a time window group for sending / receiving DMRS in a time slot is indicated by a bit map (eg, a downlink bit map (DL bitmap)).

[0529] Specifically, the bitmap is used to specify a first time window group from among the seven time window groups. The bitmap includes seven bits, and each of the seven time window groups corresponds to one bit in the bitmap, and the bitmap includes seven bits. The bitmap is also used to specify one or more time window groups other than the first time window group from among the seven time window groups as time window groups for sending / receiving DMRS.

[0530] For example, FIG20 shows a schematic diagram of a slot sending and receiving a symbol according to an embodiment of the present application.

[0531] As shown in Figure 20, a slot contains 14 time windows, corresponding to the sending and receiving of 14 symbols (symbol 181-symbol 1814). The 14 time windows are divided into 7 time window groups (Z1-Z7).

[0532] The DL bitmap is a 7-bit binary string. Each bit in the DL bitmap corresponds to a time window group. When the bit value in the DL bitmap corresponding to a time window group is 0, it indicates that the time window group is not used for sending or receiving DMRS. When the bit value in the DL bitmap corresponding to a time window group is 1, it indicates that the time window group is used for sending or receiving DMRS.

[0533] For example, when the value of the DL bitmap is 0101000, it indicates that the second and fourth time window groups among the seven time window groups are used for transmitting and receiving DMRS.

[0534] As shown in Figure 20, time window group Z2 (symbol 183, symbol 184) and time window group Z4 (symbol 187, symbol 188) are used for sending and receiving DMRS. Among them, the first time window in time window group Z2 and time window group Z4 is used for receiving downlink DMRS (or sending downlink DMRS), and the second time window in time window group Z2 and time window group Z4 is used for sending uplink DMRS (or receiving downlink DMRS).

[0535] Optionally, in one embodiment, multiple different modes are preconfigured, and different modes correspond to different combinations of time windows for sending and receiving DMRS in a time slot. For example, a first mode corresponds to a time slot in which the first time window is used to receive a downlink DMRS (or send a downlink DMRS), and the third time window is used to send an uplink DMRS (or receive a downlink DMRS); a second mode corresponds to a time slot in which the first time window is used to receive a downlink DMRS (or send a downlink DMRS), and the fourth time window is used to send an uplink DMRS (or receive a downlink DMRS).

[0536] In this way, it is only necessary to specify a mode, and then a time window for transmitting and receiving a DMRS in a time slot can be determined according to the specified mode.

[0537] Optionally, in one embodiment, the current mode for transmitting and receiving DMRS is specified from a plurality of predefined modes through radio resource control (RRC).

[0538] For example, in one embodiment, a first mode is specified from a plurality of predefined modes via radio resource control (RRC). The first mode specifies a first time window and a second time window from a plurality of time windows in a time slot. The pre-specified first time window is a time window for transmitting a DMRS, and the pre-specified second time window is a time window for receiving a DMRS.

[0539] Optionally, in one embodiment, a symbol transmitted and received in a timeslot is divided into a front-loaded DMRS region and / or an additional DMRS region. A time window for transmitting and receiving DMRS in a timeslot is pre-set based on the front-loaded DMRS region and / or the additional DMRS region.

[0540] Optionally, in one embodiment, the first time window is a time window corresponding to a preloaded DMRS region in a time slot, and the second time window is another time window corresponding to the preloaded DMRS region in a time slot. The pre-designated first time window is a time window for sending DMRS; the pre-designated second time window is a time window for receiving DMRS.

[0541] Optionally, in one embodiment, the first time window is a time window corresponding to an additional DMRS region in a time slot, and the second time window is another time window corresponding to an additional DMRS region in a time slot. The pre-designated first time window is a time window for sending DMRS; the pre-designated second time window is a time window for receiving DMRS.

[0542] Optionally, in one embodiment, the first time window is a time window corresponding to a preloaded DMRS area in a time slot, and the second time window is a time window corresponding to an additional DMRS area in a time slot;

[0543] Optionally, in one embodiment, the first time window is a time window corresponding to the additional DMRS area in a time slot, and the second time window is a time window corresponding to the preloaded DMRS area in a time slot.

[0544] Optionally, in one embodiment, in the front-loaded DMRS region, time division multiplexing (TDM) is used to multiplex downlink (DL) only DMRS and uplink (UL) only DMRS, and in the additional DMRS region, shared DMRS is used.

[0545] Specifically, shared DMRS means that uplink DMRS and downlink DMRS are simultaneously superimposed on the same time-frequency resources, or uplink DMRS and downlink DMRS are multiplexed in an FDM manner.

[0546] For example, FIG21 shows a schematic diagram of a slot sending and receiving a symbol according to an embodiment of the present application.

[0547] As shown in Figure 21, a slot contains 14 time windows, and the 14 time windows correspond to the sending and receiving of 14 symbols (symbol 191-symbol 1914).

[0548] Symbols 193 and 194 correspond to the preloaded DMRS area, with symbol 193 being set to downlink (DL only) DMRS and symbol 194 being set to uplink (UL only) DMRS.

[0549] Symbol 197 and symbol 1910 correspond to additional DMRS areas, and symbol 197 and symbol 1910 are configured to adopt a shared DMRS approach.

[0550] Optionally, in one embodiment, in the front-loaded DMRS region, time division multiplexing (TDM) is used to multiplex downlink (DL) only DMRS and uplink (UL) only DMRS. In the additional DMRS region, a shared DMRS approach is used, and a combination of downlink (DL) only DMRS and uplink (UL) only DMRS is used.

[0551] Optionally, in one embodiment, an independent indication is used to indicate whether the additional candidate position of the additional DMRS area adopts a shared DMRS method, an uplink only DMRS method, or a downlink only DMRS method.

[0552] Optionally, in one embodiment, a plurality of different modes are pre-configured, and different modes correspond to different DMRS transmission configurations of additional candidate positions of the additional DMRS area.

[0553] For example, the first time window of the additional DMRS area corresponding to the first mode adopts a shared DMRS method, the second time window adopts a downlink only DMRS method, the fourth time window adopts a shared DMRS method, and the fifth time window adopts an uplink only DMRS.

[0554] The second mode corresponds to an additional DMRS area in which the first time window uses downlink (DL only) DMRS, the second time window uses uplink (UL only) DMRS, and the fourth time window uses shared DMRS.

[0555] For example, FIG22 shows a schematic diagram of a slot sending and receiving a symbol according to an embodiment of the present application.

[0556] As shown in FIG22 , a slot includes 14 time windows, and the 14 time windows correspond to the sending and receiving of 14 symbols (symbol 201-symbol 2014).

[0557] Symbol 203 and symbol 204 correspond to the preloaded DMRS area, symbol 203 is set to downlink (DL only) DMRS, and symbol 204 is set to uplink (UL only) DMRS.

[0558] Symbol 207, symbol 208, symbol 2010, and symbol 2011 correspond to additional DMRS areas. Symbol 207 adopts a shared DMRS approach, symbol 208 adopts a downlink only DMRS approach, symbol 2010 adopts a shared DMRS approach, and symbol 2011 adopts an uplink only DMRS approach.

[0559] In communication application scenarios, there are application scenarios where more than two network devices perform mixed communication with each other, for example, multiple terminal devices communicate with one base station device.

[0560] The following describes, through specific application scenarios, an example of how to avoid uplink and downlink DMRS collisions when multiple network devices communicate with each other.

[0561] FIG23 is a schematic diagram showing communication interaction among multiple network devices according to an embodiment of the present application.

[0562] Optionally, as shown in FIG23 , in one embodiment, the base station device 2301 sends a downlink DMRS to the terminal device 2302 , and the terminal device 2302 receives the downlink DMRS sent by the base station device 2301 .

[0563] The base station device 2301 is configured to send a downlink DMRS based on a first part of subcarriers.

[0564] Specifically, in the first time window, base station device 2301 transmits a downlink DMRS based on the first portion of subcarriers to terminal device 2302. The signal received by terminal device 2302 in the first time window is shown in 2310. 2310 represents the time domain (the first time window) horizontally and the frequency domain vertically. The downlink DMRS occupies only a portion of the subcarriers (the first portion).

[0565] The terminal device 2303 sends an uplink DMRS to the base station device 2301 , and the base station device 2301 receives the uplink DMRS sent by the terminal device 2303 .

[0566] The terminal device 2303 is configured to send an uplink DMRS based on the second part of the subcarriers. The first part of the subcarriers and the second part of the subcarriers do not overlap.

[0567] Specifically, in the second time window, terminal device 2303 transmits an uplink DMRS based on the second portion of the subcarriers to base station device 2301. The signal transmitted by terminal device 2303 in the second time window is shown in 2320. 2320 represents the time domain (the second time window) horizontally and the frequency domain vertically. The uplink DMRS occupies only a portion of the subcarriers (the second portion).

[0568] When the first time window and the second time window collide, the first time window and the second time window are aligned on the base station device side. The time-frequency domain occupancy of base station device 2301 transmitting downlink DMRS and receiving uplink DMRS is shown in 2330. 2330 horizontally represents the time domain (aligned first and second time windows). The vertical direction represents the frequency domain. The downlink DMRS transmitted by base station device 2301 occupies the first part of the subcarriers, and the uplink DMRS received by base station device 2301 occupies the second part of the subcarriers. Because the first part of the subcarriers does not overlap with the second part of the subcarriers, there is no collision between the downlink DMRS transmitted and the uplink DMRS received by base station device 2301.

[0569] FIG24 is a schematic diagram showing communication interaction among multiple network devices according to an embodiment of the present application.

[0570] Optionally, as shown in FIG. 24 , in one embodiment, the base station device 2401 sends a downlink DMRS to the terminal device 2402 , and the terminal device 2402 receives the downlink DMRS sent by the base station device 2401 .

[0571] The base station device 2401 is configured to send a downlink DMRS based on a first part of subcarriers.

[0572] Specifically, in the first time window, base station device 2401 transmits a downlink DMRS based on the first portion of subcarriers to terminal device 2402. The signal received by terminal device 2402 in the first time window is shown in 2410. 2410 horizontally represents the time domain (the first time window) and vertically represents the frequency domain. The downlink DMRS occupies only a portion of the subcarriers (the first portion).

[0573] The terminal device 2403 sends an uplink DMRS to the base station device 2401 , and the base station device 2401 receives the uplink DMRS sent by the terminal device 2403 .

[0574] The terminal device 2403 is configured to send an uplink DMRS based on the second part of the subcarriers. The first part of the subcarriers and the second part of the subcarriers do not overlap.

[0575] Specifically, in the second time window, terminal device 2403 transmits a first uplink DMRS based on the second portion of the subcarriers to base station device 2401. The signal transmitted by terminal device 2403 in the second time window is shown in 2420. 2420 horizontally represents the time domain (the second time window) and vertically represents the frequency domain. The first uplink DMRS occupies only a portion of the subcarriers (the second portion).

[0576] The terminal device 2404 sends an uplink DMRS to the base station device 2401 , and the base station device 2401 receives the uplink DMRS sent by the terminal device 2404 .

[0577] The terminal device 2404 is configured to send an uplink DMRS based on the third portion of the subcarriers. The third portion of the subcarriers does not overlap with the first portion and the second portion of the subcarriers.

[0578] Specifically, in the third time window, terminal device 2404 transmits a second uplink DMRS based on the third portion of the subcarriers to base station device 2401. The signal transmitted by terminal device 2404 in the third time window is shown in 2430. 2430 horizontally represents the time domain (the third time window) and vertically represents the frequency domain. The second uplink DMRS occupies only a portion of the subcarriers (the third portion).

[0579] When the first, second, and third time windows collide, the first, second, and third time windows are aligned on the base station device side. The time-frequency domain occupancy of base station device 2401 transmitting downlink DMRS and receiving uplink DMRS is shown in 2440. 2440 horizontally represents the time domain (aligned first and second time windows). Vertically represents the frequency domain. The downlink DMRS transmitted by base station device 2401 occupies the first portion of subcarriers, the first uplink DMRS received by base station device 2401 occupies the second portion of subcarriers, and the second uplink DMRS received by base station device 2401 occupies the third portion of subcarriers. Because the first, second, and third portions of subcarriers do not overlap, there is no collision between base station device 2301 transmitting downlink DMRS and receiving uplink DMRS.

[0580] FIG25 is a schematic diagram showing communication interaction among multiple network devices according to an embodiment of the present application.

[0581] Optionally, as shown in FIG. 25 , in one embodiment, the base station device 2501 sends a downlink DMRS to the terminal device 2502 , and the terminal device 2502 receives the downlink DMRS sent by the base station device 2501 .

[0582] The base station device 2301 is configured to send a downlink DMRS in a first time window (corresponding to symbol 252 ).

[0583] Specifically, in the first time window, base station device 2501 sends a downlink DMRS to terminal device 2502. The signal received by terminal device 2502 is shown as 2510. 2510 horizontally represents the time domain, and the downlink DMRS occupies the first time window (symbol 252).

[0584] The terminal device 2503 sends an uplink DMRS to the base station device 2501 , and the base station device 2501 receives the uplink DMRS sent by the terminal device 2503 .

[0585] The terminal device 2503 is configured to send an uplink DMRS in a second time window (corresponding to symbol 253). The second time window does not collide with the first time window.

[0586] Specifically, in the second time window, terminal device 2503 sends an uplink DMRS to base station device 2501. The signal sent by terminal device 2503 is shown as 2520. 2520 horizontally represents the time domain, and the uplink DMRS occupies the second time window (symbol 253).

[0587] On the base station side, the time windows are aligned. The time domain occupied by base station 2501 for transmitting downlink DMRS and receiving uplink DMRS is shown in 2530. Horizontal 2530 represents the time domain. The downlink DMRS transmitted by base station 2501 occupies the first time window (symbol 252), and the uplink DMRS received by base station 2501 occupies the second time window (symbol 253). There is no collision between downlink DMRS transmission and uplink DMRS reception by base station 2501.

[0588] Optionally, in one embodiment, in order to ensure better reception of uplink DMRS in the second time window (symbol253), symbol253 is left blank.

[0589] Optionally, in one embodiment, the blank space above symbol 253 is made blank through explicit indication.

[0590] Optionally, in another embodiment, the downlink symbol of the second time window is configured in a rate matching resource.

[0591] In the description of the embodiments of the present application, the individual process steps of the method can be divided into various modules according to their functions and implemented separately. The division of each module is merely a division of logical functions. When implementing the embodiments of the present application, the functions of each module can be implemented in the same or multiple software and / or hardware.

[0592] Specifically, the device proposed in the embodiment of the present application can be fully or partially integrated into a physical entity during actual implementation, or it can be physically separated. And these modules can all be implemented in the form of software calling through processing elements; or they can all be implemented in the form of hardware; or some modules can be implemented in the form of software calling through processing elements, and some modules can be implemented in the form of hardware. For example, the determination module can be a separately established processing element, or it can be integrated in a chip of an electronic device. The implementation of other modules is similar. In addition, these modules can be fully or partially integrated together, or they can be implemented independently. During the implementation process, each step of the above method or each of the above modules can be completed by the hardware integrated logic circuit in the processor element or the instructions in the form of software.

[0593] For example, the above modules may be one or more integrated circuits configured to implement the above methods, such as one or more application-specific integrated circuits (ASICs), one or more digital signal processors (DSPs), or one or more field programmable gate arrays (FPGAs). For another example, these modules may be integrated together and implemented in the form of a system-on-a-chip (SOC).

[0594] Furthermore, based on the method proposed in this application, an embodiment of this application also proposes an electronic device, which may be the network device 101 or the network device 102 in the embodiment of this application.

[0595] The electronic device includes a memory for storing computer program instructions, a processor for executing the program instructions, and a communication device, wherein, when the computer program instructions are executed by the processor, the electronic device is triggered to execute the actions performed by network device 101 or network device 102 in the method shown in the embodiment of the present application.

[0596] FIG26 is a schematic diagram showing the structure of an electronic device according to an embodiment of the present application.

[0597] The electronic device (network device) of the embodiment of the present application may adopt the component structure shown in Figure 26. As shown in Figure 26, the electronic device 2600 includes a processor 2610, a memory 2620, and a communication device 2630.

[0598] The memory 2620 can be used to store computer program instructions for executing the methods shown in the above embodiments. When the processor 2610 executes the computer program instructions stored in the memory 2620, the processor 2610 controls the communication device 2630 to execute the methods shown in the above embodiments.

[0599] The processor 2610 of the electronic device 2600 may be a device-on-chip (SOC), which may include a central processing unit (CPU) and may further include other types of processors.

[0600] Specifically, the processor 2610 may include, for example, a CPU, a DSP, a microcontroller, or a digital signal processor, and may also include a GPU, an embedded neural network processor (NPU), and an image signal processor (ISP). The processor 2610 may also include necessary hardware accelerators or logic processing hardware circuits, such as ASICs, or one or more integrated circuits for controlling the execution of the program of the technical solution of the present application. In addition, the processor 2610 may have the function of operating one or more software programs, and the software programs may be stored in a storage medium.

[0601] The memory 2620 of the electronic device 2600 can be a read-only memory (ROM), other types of static storage devices that can store static information and instructions, random access memory (RAM) or other types of dynamic storage devices that can store information and instructions, or an electrically erasable programmable read-only memory (EEPROM), a compact disc read-only memory (CD-ROM) or other optical disc storage, optical disc storage (including compact disc, laser disc, optical disc, digital versatile disc, Blu-ray disc, etc.), a magnetic disk storage medium or other magnetic storage device, or any computer-readable medium that can be used to carry or store desired program code in the form of instructions or data structures and can be accessed by a computer.

[0602] Specifically, in one embodiment of the present application, the processor 2610 and the memory 2620 may be combined into a processing device, or more commonly, they may be independent components. In a specific implementation, the memory 2620 may also be integrated into the processor 2610 or independent of the processor 2610.

[0603] The communication device 2630 of the electronic device 2600 is used to implement wireless communication functions. The communication device 2630 includes one or more of an antenna 2631 , a communication module 2632 , a modem processor 2633 and a baseband processor 2634 .

[0604] Antenna 2631 is used to transmit and receive electromagnetic wave signals. Antenna 2631 may include one or more independent antennas, each of which can be used to cover a single or multiple communication frequency bands. Different antennas can also be reused to improve antenna utilization.

[0605] The communication module 2632 can provide solutions for wireless communications, including 2G / 3G / 4G / 5G, applied to the electronic device 2600. The communication module 2632 may include at least one filter, a switch, a power amplifier, a low noise amplifier (LNA), etc. The communication module 2632 can receive electromagnetic waves through the antenna 2631, filter, amplify, and process the received electromagnetic waves, and transmit them to the modulation and demodulation processor 2633 for demodulation. The mobile communication module 2632 can also amplify the signal modulated by the modulation and demodulation processor 2633 and convert it into electromagnetic waves for radiation through the antenna 2631. In some embodiments, at least some functional modules of the mobile communication module 2632 can be set in the processor 2610.

[0606] The modem processor 2633 may include a modulator and a demodulator. The modulator is used to modulate the low-frequency baseband signal to be transmitted into a medium- or high-frequency signal. The demodulator is used to demodulate the received electromagnetic wave signal into a low-frequency baseband signal. The demodulator then transmits the demodulated low-frequency baseband signal to the baseband processor 2634 for processing. After processing by the baseband processor 2634, the low-frequency baseband signal is transmitted to the processor 2610. In some embodiments, the modem processor 2633 may be a standalone device. In other embodiments, the modem processor 2633 may be independent of the processor 2610 and provided in the same device as the communication module 2632 or other functional modules.

[0607] In some embodiments, the antenna 2631 and the communication module 2632 of the electronic device 2600 are coupled so that the electronic device 2600 can communicate with a network and other devices via wireless communication technologies. The wireless communication technologies may include global system for mobile communications (GSM), general packet radio service (GPRS), code division multiple access (CDMA), wideband code division multiple access (WCDMA), time-division code division multiple access (TD-SCDMA), long term evolution (LTE), BT, GNSS, WLAN, NFC, FM, and / or IR technology. The GNSS may include global positioning system (GPS), global navigation satellite system (GLONASS), Beidou navigation satellite system (BDS), quasi-zenith satellite system (QZSS), and / or satellite-based augmentation system (SBAS).

[0608] Furthermore, in actual application scenarios, the method flow of the embodiments shown in this specification can be implemented by an electronic chip installed on an electronic device. Therefore, based on the method proposed in this application, one embodiment of this application also proposes an electronic chip. This electronic chip is installed in a base station device. The electronic chip includes a memory for storing computer program instructions and a processor for executing computer program instructions. When the computer program instructions are executed by the processor, the electronic chip is triggered to execute the actions performed by the base station device in the method shown in the above embodiment of this application.

[0609] Furthermore, based on the method provided in the present application, an embodiment of the present application also proposes an electronic chip. The electronic chip is installed in a terminal device. The electronic chip includes a memory for storing computer program instructions and a processor for executing computer program instructions. When the computer program instructions are executed by the processor, the electronic chip is triggered to execute the actions performed by the terminal device in the method shown in the above embodiment of the present application.

[0610] Furthermore, the devices, apparatuses, and modules described in the embodiments of the present application may be implemented by computer chips or entities, or by products having certain functions.

[0611] Those skilled in the art will appreciate that the embodiments of the present application may be provided as methods, apparatus, or computer program products. Thus, the present invention may take the form of an entirely hardware embodiment, an entirely software embodiment, or an embodiment combining software and hardware. Furthermore, the present invention may take the form of a computer program product implemented on one or more computer-usable storage media containing computer-usable program code.

[0612] In the several embodiments provided in this application, if any function is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this application, or the part that contributes to the prior art, or part of the technical solution, can be embodied in the form of a software product, which is stored in a storage medium and includes a number of instructions for enabling a computer device (which can be a personal computer, server, or network device, etc.) to perform all or part of the steps of the method described in each embodiment of this application.

[0613] Specifically, an embodiment of the present application further provides a computer-readable storage medium, which stores a computer program. When the computer-readable storage medium is run on a computer, the computer executes the method provided in the embodiment of the present application.

[0614] An embodiment of the present application further provides a computer program product, which includes a computer program. When the computer program product is run on a computer, it enables the computer to execute the method provided in the embodiment of the present application.

[0615] The embodiment description in this application is described with reference to the flow chart and / or block diagram according to the method, equipment (device) and computer program product of embodiment of the present application.It should be understood that each flow process and / or box in the flow chart and / or block diagram and the combination of the flow process and / or box in the flow chart and / or block diagram can be realized by computer program instructions.These computer program instructions can be provided to the processor of general-purpose computer, special-purpose computer, embedded processing machine or other programmable data processing equipment to produce a machine, so that the instruction executed by the processor of computer or other programmable data processing equipment produces the device for realizing the function specified in one flow chart flow chart or multiple flow charts and / or one block or multiple blocks of block diagram.

[0616] These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing device to operate in a specific manner, so that the instructions stored in the computer-readable memory produce a product including an instruction device that implements the functions specified in one or more processes in the flowchart and / or one or more boxes in the block diagram.

[0617] These computer program instructions can also be loaded onto a computer or other programmable data processing device so that a series of operating steps are executed on the computer or other programmable device to produce a computer-implemented process, so that the instructions executed on the computer or other programmable device provide steps for implementing the functions specified in one or more processes in the flowchart and / or one or more boxes in the block diagram.

[0618] It should also be noted that, in the embodiments of the present application, "at least one" refers to one or more, and "more than one" refers to two or more. "And / or" describes the association relationship of associated objects, indicating that three relationships may exist. For example, A and / or B can represent the existence of A alone, the existence of A and B at the same time, and the existence of B alone. Among them, A and B can be singular or plural. The character " / " generally indicates that the previous and subsequent associated objects are in an "or" relationship. "At least one of the following" and similar expressions refer to any combination of these items, including any combination of single or plural items. For example, at least one of a, b and c can represent: a, b, c, a and b, a and c, b and c or a and b and c, where a, b, c can be single or multiple.

[0619] In the embodiments of the present application, the terms "comprises," "includes," or any other variations thereof are intended to encompass non-exclusive inclusion, such that a process, method, commodity, or apparatus comprising a series of elements includes not only those elements but also other elements not explicitly listed, or elements inherent to such process, method, commodity, or apparatus. In the absence of further limitations, an element defined by the phrase "comprising a ..." does not preclude the presence of additional identical elements in the process, method, commodity, or apparatus comprising the element.

[0620] The present application may be described in the general context of computer-executable instructions executed by a computer, such as program modules. Generally, program modules include routines, programs, objects, components, data structures, etc. that perform specific tasks or implement specific abstract data types. The present application may also be practiced in distributed computing environments where tasks are performed by remote processing devices connected through a communications network. In a distributed computing environment, program modules may be located in local and remote computer storage media, including storage devices.

[0621] The various embodiments in this application are described in a progressive manner. Similar parts between the various embodiments can be referred to in conjunction with each other. Each embodiment focuses on the differences from other embodiments. In particular, the device embodiments are generally similar to the method embodiments, so the description is relatively simple. For relevant parts, refer to the partial description of the method embodiments.

[0622] Those skilled in the art will appreciate that the various units and algorithm steps described in the embodiments of the present application can be implemented using a combination of electronic hardware, computer software, and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professionals and technicians can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0623] Those skilled in the art will clearly understand that, for the convenience and brevity of description, the specific working processes of the above-described devices, apparatuses and units can refer to the corresponding processes in the aforementioned method embodiments and will not be repeated here.

[0624] The above description is merely a specific embodiment of the present application. Any person skilled in the art may easily conceive of variations or substitutions within the technical scope disclosed in this application, and such variations or substitutions shall be within the scope of protection of this application. The scope of protection of this application shall be subject to the scope of protection of the claims.

Claims

1. A method for transmitting demodulation reference signals (DMRS), characterized in that, The method is applied to a first network device, and the method includes: Receiving DMRS sent by a second network device; Sending DMRS, where the DMRS sent by the first network device does not collide with the received DMRS.

2. The method according to claim 1, wherein The first network device is one of a terminal device and a base station device, and the second network device is the other of the terminal device and the base station device.

3. The method according to claim 1, wherein The timing advance for communication between the first network device and the second network device is within the range of the cyclic prefix.

4. The method according to claim 3, characterized in that, The first network device plans to send a first DMRS in a first time window, and the second network device plans to send a second DMRS in a second time window, and there is a collision between the first time window and the second time window; Sending the DMRS to the second network device includes: Scheduling the transmission of the first DMRS to avoid collision between the first DMRS and the second DMRS.

5. The method according to claim 4, characterized in that, The second network device plans to send the second DMRS based on a first part of the subcarriers; Scheduling the transmission of the first DMRS includes: In the first time window, sending the first DMRS based on a second part of the subcarriers, and the second part does not overlap with the first part.

6. The method according to claim 4, characterized in that, Scheduling the transmission of the first DMRS includes: Canceling the transmission of the first DMRS.

7. The method according to claim 4, wherein Scheduling the transmission of the first DMRS includes: In a third time window, sending the first DMRS, where there is no collision between the third time window and the second time window.

8. The method according to claim 6 or 7, characterized in that, The method further includes: Sending a data signal to the second network device in the first time window; Or, not sending a signal to the second network device in the first time window.

9. The method according to any one of claims 5-7, characterized in that The device type of the first network device is a device type that is pre-specified and performs scheduling of DMRS operations to avoid DMRS collisions.

10. The method according to claim 5, wherein The first network device is a base station device.

11. The method according to claim 6, wherein The first network device also plans to send a third DMRS in a third time window, and the second network device also plans to send a fourth DMRS in a fourth time window, where: the third time window and the fourth time window are time windows after the first time window and the second time window; there is a collision between the third time window and the fourth time window; The method further includes: Sending the third DMRS in the third time window, where the second network device cancels the transmission of the fourth DMRS.

12. The method according to claim 6, wherein The priority of the first DMRS is lower than the priority of the second DMRS.

13. The method according to claim 6, characterized in that, A first quantity is greater than a second quantity, where: The first quantity is the total quantity of DMRS planned to be sent and / or already sent by the first network device in a first time period, where the first time period is a time period including the first time window; The second quantity is the total quantity of DMRS planned to be sent and / or already sent by the second network device in a second time period, where the second time period is a time period including the second time window, and the second time period corresponds to the first time period.

14. The method according to claim 7, wherein The time-frequency resources of the first network device are the same as those of the second network device, and the third quantity is less than the fourth quantity, where: The third quantity is the total quantity of DMRS planned to be sent and / or already sent by the first network device in a third time period, where the third time period is a time period including the first time window; The fourth quantity is the total quantity of DMRS planned to be sent and / or already sent by the second network device in a fourth time period, where the fourth time period is a time period including the second time window, and the fourth time period corresponds to the third time period.

15. The method according to claim 7, characterized in that The time-frequency resources of the first network device are higher than those of the second network device.

16. The method according to claim 1, wherein The timing advance for communication between the first network device and the second network device is outside the range of the cyclic prefix.

17. The method according to claim 16, wherein The method further includes: Selecting a transmission mode of the DMRS according to the arrival of uplink and downlink services, where the transmission modes of the DMRS include simultaneous co-frequency full duplex, single-direction downlink, and single-direction uplink.

18. The method according to claim 17, wherein The first network device is a base station device.

19. The method according to claim 17, characterized in that, The DMRS configurations of the uplink physical channel and the downlink physical channel adopt semi-static independent configurations, and predefined criteria are adopted when the uplink physical channel and the downlink physical channel are scheduled simultaneously.

20. The method according to claim 17, wherein The pattern of the DMRS can be modified by downlink control information (DCI).

21. The method according to claim 17, wherein In one DMRS configuration, uplink DMRS and downlink DMRS are configured simultaneously.

22. The method according to claim 1, wherein The sending of the DMRS includes: Sending the DMRS based on a second part of subcarriers, where: The second part does not overlap with the first part of the subcarriers; The first part is the part of subcarriers used by the second network device to send the DMRS.

23. According to the method of claim 1, wherein: The first part is odd subcarriers and the second part is even subcarriers; Or, The first part is even subcarriers and the second part is odd subcarriers.

24. The method according to claim 1, characterized in that, The sending of the DMRS includes: Sending the DMRS based on a first code division multiplexing group (CDM group), where: The first code division multiplexing group and the second code division multiplexing group are different code division multiplexing groups; The second code division multiplexing group is the code division multiplexing group used by the second network device to send the DMRS.

25. The method according to claim 1, wherein The sending of the DMRS includes: Sending the DMRS based on a first subcarrier part in a code division multiplexing group (CDM group), where: The first subcarrier part and the second subcarrier part are different subcarrier parts in the code division multiplexing group (CDM group); The second subcarrier part is the part of subcarriers used by the second network device to send the DMRS.

26. The method according to claim 1, characterized in that The sending of the DMRS includes: Sending the DMRS in a first time window of a time slot, where: The time slot includes at least the first time window and the second time window, and there is no collision between the first time window and the second time window; The first time window is a pre-specified time window in the one time slot for transmitting DMRS; The second time window is a pre-specified time window in the one time slot for receiving DMRS.

27. The method according to claim 26, wherein: The one time slot includes 14 consecutive time windows, and the 14 consecutive time windows include 7 time window groups, and each of the time window groups includes two consecutive time windows; The first time window is the first time window or the second time window in the first time window group, and the second time window is the second time window or the first time window in the first time window group; The first time window group is a pre-specified one of the 7 time window groups.

28. The method according to claim 27, wherein: Each of the 7 time window groups corresponds to one bit in a bit map, and the bit map includes 7 bits; The bit map is used to specify the first time window group from the 7 time window groups.

29. The method according to claim 26, wherein: The first time window is one time window specified by a first pattern among multiple time windows in the one time slot; The second time window is another time window specified by the first pattern among multiple time windows in the one time slot; The first pattern is a pattern specified from a plurality of predefined patterns through radio resource control (RRC).

30. The method according to claim 26, wherein: The first time window is one time window corresponding to a pre-loaded DMRS region in the one time slot, and the second time window is another time window corresponding to the pre-loaded DMRS region in the one time slot; or, The first time window is one time window corresponding to an additional DMRS region in the one time slot, and the second time window is another time window corresponding to the additional DMRS region in the one time slot; Or, The first time window is one time window corresponding to the pre-loaded DMRS region in the one time slot, and the second time window is one time window corresponding to the additional DMRS region in the one time slot; Or, The first time window is one time window corresponding to the additional DMRS region in the one time slot, and the second time window is one time window corresponding to the pre-loaded DMRS region in the one time slot.

31. The method according to claim 1, wherein: The first network device is a base station device, and the second and third network devices are terminal devices; the second network device sends DMRS to the first network device based on a first part of subcarriers in a second time window. The sending of DMRS includes: in a first time window, sending DMRS to the third network device based on a second part of the subcarriers, where the second part does not overlap with the first part, and the first time window collides with the second time window.

32. The method according to claim 1, wherein: The first network device and the third network device are terminal devices, and the second network device is a base station device; the second network device sends DMRS to the third network device based on a first part of subcarriers in a second time window. The sending of DMRS includes: in a first time window, sending DMRS to the second network device based on a second part of the subcarriers, where the second part does not overlap with the first part, and the first time window collides with the second time window.

33. The method according to claim 1, wherein: The first network device is a base station device, and the second, third, and fourth network devices are terminal devices; the third network device sends DMRS to the first network device based on a first part of subcarriers in a first time window. The fourth network device sends DMRS to the first network device based on a second part of the subcarriers in the second time window. The sending of DMRS includes: in the first time window, sending DMRS to the second network device based on a third part of the subcarriers, where the third part does not overlap with the first part and the second part, and the first time window collides with the second time window.

34. The method according to claim 1, wherein: The first, third, and fourth network devices are terminal devices, and the second network device is a base station device; the third network device sends DMRS to the second network device based on a first part of subcarriers in a third time window. The second network device sends DMRS to the fourth network device based on a second part of the subcarriers in a second time window. The sending of DMRS includes: in a first time window, sending DMRS to the second network device based on a third part of the subcarriers, where the third part does not overlap with the first part and the second part, and the first, second, and third time windows collide.

35. The method according to claim 1, characterized in that, The first network device is a base station device, and the second and third network devices are terminal devices; the third network device sends DMRS to the first network device in a second time window. The sending of DMRS includes: sending DMRS to the second network device in a first time window, where the first time window does not collide with the second time window.

36. The method according to claim 1, wherein The first network device and the third network device are terminal devices, and the second network device is a base station device; the second network device sends DMRS to the third network device in a second time window. The sending of the DMRS includes: Sending DMRS to the second network device in a first time window, where the first time window does not collide with the second time window.

37. An electronic chip, characterized in that, It includes: A processor for executing computer program instructions stored on a memory, wherein when the computer program instructions are executed by the processor, the electronic chip is triggered to execute the method described in any one of claims 1-36.

38. An electronic device, characterized in that, The electronic device includes a memory for storing computer program instructions, a processor for executing the computer program instructions, and a communication device, wherein when the computer program instructions are executed by the processor, the electronic device is triggered to execute the method described in any one of claims 1-36.

39. A computer-readable storage medium, characterized in that, A computer program is stored in the computer-readable storage medium, and when it runs on a computer, the computer is caused to execute the method described in any one of claims 1-36.

Images