WO2022120753A1 - Communication method and communication apparatus - Google Patents

Abstract

The present application provides a communication method and a communication apparatus. The communication method comprises: in an uplink carrier handover scenario, a distributed unit (DU) receives location information of a DC subcarrier corresponding to a bandwidth part (BWP) of a second uplink carrier sent by a centralized unit (CU), and determines a location of the DC subcarrier according to the location information of the DC subcarrier, so that the DU can obtain the location of the DC subcarrier when processing interference caused by leakage of a local oscillator signal.

Description

Communication method and communication device technical field

The present application relates to the field of communication, and, more particularly, to a communication method and a communication apparatus.

Background technique

C-Band has abundant bandwidth and is an important frequency band for building 5G Enhanced Mobile Broadband (eMBB). Therefore, most operators around the world use C-Band as the preferred frequency band for 5G. However, due to the uneven distribution of the uplink and downlink time slots of New Radio (NR) and the large downlink transmission power of the 5G base station (g Node B, gNB), the C-Band uplink and downlink coverage is unbalanced, and the uplink coverage will be limited, and the throughput of uplink transmission will decrease.

In order to solve the above problems, a new spectrum pairing method is defined to decouple the uplink and downlink, that is, in the uplink restricted area, use C-Band to transmit downlink data, and use Sub-3G to transmit uplink data. Sub-3G in this scenario is a supplementary uplink (Supplementary Uplink, SUL) carrier, and C-Band is a normal uplink (Normal Uplink, NUL) carrier. User Equipment (UE) accesses NUL cells in an area with good uplink coverage, but when the UE moves to an area with limited uplink coverage, in order to improve the uplink transmission throughput of the UE, the UE needs to switch to the SUL carrier.

At present, UEs all have the problem of local oscillator leakage. Receiving the local oscillator signal leaked to the output port or input port will generate strong noise in the baseband DC (Direct current, DC) sub-carrier, resulting in the degradation of the overall demodulation performance. Therefore, in the scenario of uplink carrier switching, how to solve the problem of demodulation performance degradation caused by local oscillator signal leakage is a hot research topic for those skilled in the art.

SUMMARY OF THE INVENTION

The present application provides a communication method and communication device, so that in the scenario of uplink carrier switching, the network device obtains the position of the DC subcarrier of the partial bandwidth BWP of the second uplink carrier when solving the local oscillator signal leakage.

A first aspect provides a communication method, the method comprising: the DU receives location information of a DC sub-carrier of a BWP of a second uplink carrier of a CU, and determines the DC sub-carrier according to the location information of the DC sub-carrier s position.

It should be understood that before the DU receives the location information of the DC subcarrier, the DU communicates with the terminal device through the first uplink carrier, and the first uplink carrier may be NUL or SUL.

Based on the above solution, the DU can know the position of the DC subcarrier of the BWP of the second uplink carrier, so that the DU can determine the position of the DC subcarrier when dealing with the interference caused by the leakage of the local oscillator signal.

With reference to the first aspect, in some implementations of the first aspect, after the DU determines the location of the DC subcarrier, at least one resource element RE corresponding to the DC subcarrier is set to zero RE.

With reference to the first aspect, in some implementations of the first aspect, before the DU receives the location information of the DC subcarrier of the BWP of the second uplink carrier from the CU, the DU needs to send the second uplink carrier configuration information to the CU and A request message, where the request message is used to request the location information of the DC subcarrier of the BWP of the second uplink carrier.

Based on the above solution, the DU can set at least one resource element RE corresponding to the DC subcarrier to zero RE by using the log-likelihood ratio, that is to say, no data is sent on at least one RE corresponding to the DC subcarrier, Therefore, the interference caused by the local oscillator signal leaking to the output port or the input port in the RE can be solved.

With reference to the first aspect, in some implementations of the first aspect, the location information of the DC subcarrier is carried in the user equipment context change confirmation message.

In a second aspect, a communication method is provided, the method comprising: a CU sending indication information, the indication information instructing a terminal device to send location information of a DC subcarrier of a BWP of a second uplink carrier; the CU receiving the first information from the terminal device The location information of the DC sub-carrier of the BWP of the second uplink carrier, and the location information of the DC sub-carrier of the BWP of the second uplink carrier is sent to the distributed unit DU.

It should be understood that before the CU sends the indication information, it communicates with the terminal device through the first uplink carrier, and similarly, the first uplink carrier may be NUL or SUL.

Based on the above solution, the CU learns the location of the DC subcarrier of the BWP of the second uplink carrier by sending the DU whose indication information may be, so that the DU can determine the location of the DC subcarrier when dealing with interference caused by local oscillator signal leakage.

With reference to the second aspect, in some implementations of the second aspect, the location information of the DC subcarrier is used to instruct the DU to set the RE corresponding to the location of the DC subcarrier to a zero RE.

With reference to the second aspect, in some implementations of the second aspect, before the CU sends the indication information, it receives the second uplink carrier configuration information and a request message from the DU, where the request message is used to request the second uplink carrier The location information of the DC subcarriers of the BWP.

Based on the above solution, the DU can set at least one resource element RE corresponding to the DC subcarrier to zero RE by using the log-likelihood ratio, that is to say, no data is sent on at least one RE corresponding to the DC subcarrier, Therefore, the interference caused by the local oscillator signal leaking to the output port or the input port in the RE can be solved.

With reference to the second aspect, in some implementations of the second aspect, the location information of the DC subcarrier is carried in the user equipment context change confirmation message.

With reference to the second aspect, in some implementations of the second aspect, the indication information is carried in a reconfiguration message or a secondary node change request message.

It should be understood that when the UE is in the independent networking mode, the indication information is carried in the reconfiguration message sent to the terminal device, and when the UE is in the non-independent networking mode, the indication information is carried in the secondary node change confirmation sent to the eNB in the message.

In a third aspect, a communication method is provided, the method comprising: a terminal device receiving indication information from the network device, the indication information instructing the terminal device to send location information of a DC sub-carrier of a partial bandwidth BWP of a second uplink carrier , and send the location information of the DC sub-carrier of the BWP of the second uplink carrier.

It should be understood that the terminal device communicates with the network device through the first uplink carrier before receiving the indication information, and the switching of the uplink carrier has been completed after the terminal device sends the location information of the DC subcarrier, and then the second uplink carrier is used. communicate with the network device.

Based on the above solution, the terminal device sends the location information of the DC sub-carrier, so that the DU knows the location of the DC sub-carrier of the BWP of the second uplink carrier, so that the DU can determine the DC sub-carrier when dealing with the interference caused by the leakage of the local oscillator signal. s position.

With reference to the third aspect, in some implementations of the third aspect, the location information of the DC subcarrier is carried in the reconfiguration complete message.

With reference to the third aspect, in some implementations of the third aspect, the indication information is carried in a reconfiguration message or a secondary node change request message.

In a fourth aspect, a communication device is provided, the device includes a transceiver unit and a processing unit, the transceiver unit is configured to receive location information of a DC sub-carrier of a partial bandwidth BWP of a second uplink carrier from a centralized unit CU; the The processing unit is configured to determine the position of the DC sub-carrier according to the position information of the DC sub-carrier.

It should be understood that, before the transceiver unit receives the location information of the DC subcarrier, the apparatus communicates with the terminal device through the first uplink carrier.

With reference to the fourth aspect, in some implementations of the fourth aspect, the processing unit is further configured to set at least one resource element RE corresponding to the DC subcarrier to a zero RE.

With reference to the fourth aspect, in some implementations of the fourth aspect, before the transceiver unit receives the location information of the DC subcarrier of the BWP of the second uplink carrier from the CU, the transceiver unit is further configured to send the second uplink carrier to the CU Carrier configuration information and a request message, where the request message is used to request location information of the DC subcarrier of the BWP of the second uplink carrier.

With reference to the fourth aspect, in some implementations of the fourth aspect, the location information of the DC subcarrier is carried in the user equipment context change confirmation message.

A fifth aspect provides a communication device, the device includes a transceiver unit, the transceiver unit is configured to send indication information, the indication information instructs the terminal device to send the location information of the DC sub-carrier of the partial bandwidth BWP of the second uplink carrier This transceiver unit is also used to receive the position information of the DC subcarrier of the BWP of the second uplink carrier from the terminal equipment; the transceiver unit is also used for the distributed unit DU to send the DC subcarrier of the BWP of the second uplink carrier. location information.

It should be understood that, before the transceiver unit is used to send the indication information, the apparatus communicates with the terminal device through the first uplink carrier.

With reference to the fifth aspect, in some implementation manners of the fifth aspect, the location information of the DC subcarrier is used to instruct the DU to set the resource element corresponding to the location of the DC subcarrier to zero RE.

With reference to the fifth aspect, in some implementations of the fifth aspect, before the transceiver unit sends the indication information, it receives the second uplink carrier configuration information and a request message from the DU, where the request message is used to request the second uplink Location information of the DC sub-carriers of the carrier's BWP.

With reference to the fifth aspect, in some implementations of the fifth aspect, the location information of the DC subcarrier is carried in the user equipment context change confirmation message.

With reference to the fifth aspect, in some implementations of the fifth aspect, the indication information is carried in a reconfiguration message or a secondary node change request message.

With reference to the fifth aspect, in some implementations of the fifth aspect, the location information of the DC subcarrier received by the CU is carried in the reconfiguration complete message or the secondary node change confirmation message.

In a sixth aspect, a communication device is provided, the device includes a transceiver unit, the transceiver unit is configured to receive indication information from the network device, the indication information instructs the terminal device to send the DC DC of the partial bandwidth BWP of the second uplink carrier The location information of the sub-carrier; the transceiver unit is further configured to send the location information of the DC sub-carrier of the BWP of the second uplink carrier.

It should be understood that before the transceiver unit receives the indication information, the device communicates with the network device through the first uplink carrier, and after the transceiver unit sends the location information of the DC subcarrier, the device has completed the switching of the uplink carrier, and then the The apparatus communicates with the network device through the second uplink carrier.

With reference to the sixth aspect, in some implementations of the sixth aspect, the location information of the DC subcarrier is carried in the reconfiguration complete message.

With reference to the sixth aspect, in some implementation manners of the sixth aspect, the indication information is carried in a reconfiguration message or a secondary node change request message.

In a seventh aspect, a communication apparatus is provided, including a processor. The processor is coupled to the memory and can be used to execute instructions in the memory, so as to implement the communication method in the first aspect to the second aspect and any one of the possible implementations of the first aspect to the second aspect. Optionally, the communication device further includes a memory. Optionally, the communication device further includes a communication interface to which the processor is coupled, and the communication interface is used for inputting and/or outputting information. The information includes at least one of instructions and data.

In one implementation, the communication apparatus is a network device. When the communication device is a network device, the communication interface may be a transceiver, or an input/output interface.

In another implementation manner, when the communication device is a chip or a chip system, the communication interface may be an input/output interface, an interface circuit, an output circuit, an input circuit, a pin or a related interface on the chip or a chip system circuit, etc. The processor may also be embodied as a processing circuit or a logic circuit.

In another implementation manner, the communication apparatus is a chip or a chip system configured in a network device.

In an eighth aspect, a communication device is provided, including a processor. The processor is coupled to the memory, and can be used to execute instructions in the memory, so as to implement the third aspect and the communication method in any possible implementation manner of the third aspect. Optionally, the communication device further includes a memory. Optionally, the communication device further includes a communication interface to which the processor is coupled, and the communication interface is used for inputting and/or outputting information. The information includes at least one of instructions and data.

In an implementation manner, the communication apparatus is a terminal device. When the communication device is a terminal device, the communication interface may be a transceiver, or an input/output interface. Optionally, the transceiver may be a transceiver circuit. Optionally, the input/output interface may be an input/output circuit.

In another implementation, the communication device is a chip or a system of chips. When the communication device is a chip or a chip system, the communication interface may be an input/output interface, an interface circuit, an output circuit, an input circuit, a pin or a related circuit on the chip or a chip system. The processor may also be embodied as a processing circuit or a logic circuit.

In another implementation manner, the communication apparatus is a chip or a chip system configured in a network device.

In a ninth aspect, a computer program product is provided, the computer program product comprising: a computer program (also referred to as code, or instructions), which, when the computer program is executed, causes a computer to execute the above and the first aspect to The third aspect and the method in any of the possible implementations of the first aspect to the third aspect.

In a tenth aspect, a computer-readable medium is provided, the computer-readable medium stores a computer program (also referred to as code, or instruction), when it runs on a computer, causing the computer to execute the above and the first aspect to The third aspect and the method in any of the possible implementations of the first aspect to the third aspect.

In an eleventh aspect, a communication system is provided, including the aforementioned network device and terminal device.

Description of drawings

FIG. 1 is a schematic diagram of a wireless communication system in an independent networking scenario applicable to an embodiment of the present application.

FIG. 2 is an interaction flowchart of wireless communication in an independent networking scenario applicable to an embodiment of the present application.

FIG. 3 is another interactive flowchart of wireless communication in an independent networking scenario applicable to an embodiment of the present application.

FIG. 4 is a schematic diagram of a wireless communication system in a non-standalone networking scenario applicable to an embodiment of the present application.

FIG. 5 is a flowchart of wireless communication interaction in a non-standalone networking scenario applicable to an embodiment of the present application.

FIG. 6 is another flowchart of wireless communication interaction in a non-standalone networking scenario applicable to an embodiment of the present application.

FIG. 7 is a schematic block diagram of a terminal device applicable to an embodiment of the present application.

FIG. 8 is a schematic block diagram of a network device applicable to this embodiment of the present application.

FIG. 9 is a schematic structural diagram of a terminal device applicable to an embodiment of the present application.

FIG. 10 is a schematic structural diagram of a network device suitable for an embodiment of the present application.

Detailed ways

The technical solutions in the present application will be described below with reference to the accompanying drawings.

The technical solutions of the embodiments of the present application can be applied to various communication systems, such as: a global system for mobile communications (GSM) system, a code division multiple access (CDMA) system, a wideband code division multiple access ( wideband code division multiple access (WCDMA) system, general packet radio service (GPRS), long term evolution (LTE) system, LTE frequency division duplex (FDD) system, LTE time division Duplex (time division duplex, TDD), universal mobile telecommunication system (UMTS), worldwide interoperability for microwave access (WiMAX) communication system, satellite communication system, fifth generation (5th generation) , 5G) system or new radio (NR), and future communication systems.

It should be understood that in a wireless communication system, air interface resources may be used for wireless communication between communication devices. The communication devices may include network devices and terminal devices, and the network devices may also be referred to as network-side devices. The air interface resources may include at least one of time domain resources, frequency domain resources, code resources and space resources. In this embodiment of the present application, at least one may also be described as one or more, and the multiple may be two, three or more, which is not limited in this application.

FIG. 1 is a schematic diagram of a wireless communication system 100 in an independent networking scenario applicable to an embodiment of the present application.

As shown in FIG. 1 , the wireless communication system 100 may include a network device, for example, the network device shown in FIG. 1 . The wireless communication system 100 may further include at least one terminal device, such as the terminal device shown in FIG. 1 . A wireless connection can be established between a terminal device and a network device and between a terminal device and a terminal device for wireless communication, and the sending device can indicate data scheduling information through control information, so that the receiving device can correctly receive data according to the control information.

The terminal device in the embodiments of the present application may also be referred to as UE, access terminal, subscriber unit, subscriber station, mobile station, mobile station, remote station, remote terminal, mobile device, user terminal, terminal, wireless communication device, and user agent or user device. The terminal device in the embodiment of the present application may be a mobile phone, a tablet computer, an indoor or outdoor customer premises equipment (CPE), a computer with a wireless transceiver function, a virtual reality terminal device, an augmented reality terminal device, an industrial control device wireless terminals in autonomous driving, wireless terminals in telemedicine, wireless terminals in smart grids, wireless terminals in transportation safety, wireless terminals in smart cities, wireless terminals in smart homes, cellular phones, Cordless telephones, session initiation protocol (SIP) telephones, wireless local loop (WLL) stations, personal digital assistants (PDAs), handheld devices with wireless communication capabilities, computing devices or Other processing equipment connected to the wireless modem, in-vehicle equipment, wearable equipment, terminal equipment in the 5G network or terminal equipment in the future evolved Public Land Mobile Network (PLMN), etc.

In addition, the terminal device may also be a terminal device in an internet of things (Internet of things, IoT) system. IoT is an important part of the development of information technology in the future. Its main technical feature is to connect items to the network through communication technology, so as to realize the intelligent network of human-machine interconnection and interconnection of things.

It should be understood that, in this embodiment of the present application, the terminal device may be a device for implementing the function of the terminal device, or a device capable of supporting the terminal device to realize the function, such as a chip system, and the device may be installed in the terminal. In this embodiment of the present application, the chip system may be composed of chips, or may include chips and other discrete devices. In the technical solutions provided by the embodiments of the present application, the terminal device is a UE as an example to describe the technical solutions provided by the embodiments of the present application.

The network device in this embodiment of the present application may be any device with a wireless transceiver function. The equipment includes but is not limited to: radio network controller (RNC), node B (node B, NB), base station controller (BSC), base transceiver station (base transceiver station, BTS), Home base station (eg, home evolved nodeB, or home node B, HNB), base band unit (BBU), access point (AP) in wireless fidelity (WIFI) systems, wireless Relay node, wireless backhaul node, transmission point (TP) or transmission and reception point (TRP), etc. It can also be 5G, such as gNB in NR system, or transmission point (TRP or TP) ), one or a group (including multiple antenna panels) antenna panels of the base station in the 5G system, or, it can also be a network node that constitutes a gNB or a transmission point, such as a baseband unit, or a distributed unit (distributed unit, DU) , and may also be a base station in a future mobile communication system or an access node in a Wi-Fi system.

In some deployments, a gNB may include a centralized unit (CU) and a DU. The gNB may also include an active antenna unit (active antenna unit, AAU for short). The CU implements some functions of the gNB, and the DU implements some functions of the gNB. For example, the CU is responsible for processing non-real-time protocols and services, and implementing functions of radio resource control (RRC) and packet data convergence protocol (PDCP) layers. The DU is responsible for processing physical layer protocols and real-time services, and implementing the functions of the radio link control (RLC) layer, the media access control (MAC) layer, and the physical layer. AAU implements some physical layer processing functions, radio frequency processing and related functions of active antennas. Since the information of the RRC layer will eventually become the information of the PHY layer, or be transformed from the information of the PHY layer, therefore, in this architecture, the higher-layer signaling, such as the RRC layer signaling, can also be considered to be sent by the DU. , or, sent by DU+AAU. It can be understood that the network device may be a device including one or more of a CU node, a DU node, and an AAU node. In addition, the CU may be divided into network devices in an access network (Radio Access Network, RAN), or the CU may be divided into network devices in a core network (Core Network, CN), which is not limited in this application. The CU and DU specified in the current standard are two entities of the base station, and the interface between them is the F1 interface.

It should be understood that, in this embodiment of the present application, the network device may be an apparatus for implementing the function of the network device, or may be an apparatus capable of supporting the network device to implement the function, such as a chip system, and the apparatus may be installed in the network device. In the technical solutions provided by the embodiments of the present application, the network device takes the base station as an example to describe the technical solutions provided by the embodiments of the present application.

As shown in Figure 1, in an area with good uplink coverage, both uplink and downlink data can be transmitted on the C-Band. In areas with limited uplink coverage, C-Band is used to transmit downlink data, and Sub-3G is used to transmit uplink transmission. This method of uplink and downlink decoupling improves uplink coverage by defining and supplementing uplink SUL carriers, thereby improving the uplink of UE. transfer throughput.

It should be understood that the above-mentioned area with limited uplink coverage refers to an area where the distance between the UE and the base station serving the UE is greater than a certain threshold. At this time, the uplink throughput decreases and the transmission efficiency is low. On the contrary, the area with good uplink coverage is Refers to the area where the distance between the UE and the base station serving the UE is less than or equal to a certain threshold.

FIG. 2 is an interactive flowchart of wireless communication in an independent networking scenario applicable to an embodiment of the present application. It can be seen from FIG. 2 that the method 200 includes:

In step S210, the UE initially accesses the NUL cell in the area with good uplink coverage, and at this time, the UE and the base station communicate in uplink through the NUL carrier.

In step S220, the DU judges that the UE has moved to the far point of the NUL cell, that is, the area with limited uplink coverage. At this time, the NUL carrier needs to be switched to the SUL carrier to improve the uplink throughput rate.

In step S230, the DU sends the first message to the CU.

Optionally, the first message is a UE context modification request message, that is, an F1 standard interface message (such as UE Context Modification Required). The first message carries SUL carrier configuration information and indication information that instructs the UE to report the location of a direct current (direct current, DC) subcarrier of a bandwidth part (BWP) of the SUL carrier.

Alternatively, the first message may include SUL carrier configuration information and request information, where the request information is used to request DC subcarrier location information of the BWP of the SUL carrier.

In this application, one or more BWPs may exist on one carrier. For one of the BWPs, it may contain multiple subcarriers. Among these subcarriers, there will be a DC subcarrier, and the DC subcarrier may be called the DC subcarrier of the BWP of the carrier, or the carrier The DC subcarrier corresponding to the BWP.

Step S240: After receiving the first message, the CU sends the SUL carrier configuration information and the indication information indicating the location of the DC subcarrier of the BWP of the SUL carrier to the UE through a reconfiguration message.

In step S250, after receiving the reconfiguration message, the UE sends a reconfiguration complete message to the CU.

The reconfiguration complete message carries the location information of the DC subcarrier of the BWP of the SUL carrier. Exemplarily, the location information of the DC subcarrier of the BWP of the SUL carrier may be carried in the UplinkTxDirectCurrentList information element.

In step S260, the CU sends the location information of the DC subcarrier of the BWP of the SUL carrier to the DU, so that the DU can determine the location of the DC subcarrier corresponding to the BWP.

Optionally, the location information of the DC subcarrier of the BWP of the SUL carrier may be carried in an F1 standard interface message, such as a UE context modification confirmation message (UE Context Modification Confirm).

Of course, the location information of the DC sub-carrier of the BWP of the SUL carrier can also be carried by other messages sent by the CU to the DU, such as the newly added F1 interface field after specific processing. The above UE Context Modification Confirm is only an example. The message of the location information of the DC sub-carrier corresponding to the BWP of the SUL carrier is not limited.

It should be understood that the BWP of the above-mentioned SUL carrier may be one or multiple, which is not limited herein.

In step S270, after the DU determines the position of the DC subcarrier corresponding to the BWP of the SUL carrier according to the position information of the DC subcarrier corresponding to the BWP of the SUL carrier, the DU sets the resource element (RE) corresponding to the position of the DC subcarrier to zero RE.

It should be understood that there may be multiple REs corresponding to the DC subcarrier position. Here, at least one RE corresponding to the DC subcarrier position is set to zero RE, that is to say, at least one RE corresponding to the DC subcarrier position does not send data. In this way, the interference caused by the local oscillator signal leaking to the output port or the input port at the at least one RE can be solved.

After the carrier switching is completed, the UE communicates with the base station in uplink through the SUL carrier.

FIG. 3 is an interactive flowchart of wireless communication in an independent networking scenario applicable to another embodiment of the present application. It can be seen from FIG. 3 that the method 300 includes:

In step S310, the UE initially accesses the SUL cell, and at this time, the UE and the base station communicate in uplink through the SUL carrier.

In step S320, the DU determines that the UE moves to an area with good uplink coverage, and at this time, the SUL carrier can be switched to the NUL carrier.

In step S330, the DU sends the first message to the CU.

Optionally, the first message is a UE context modification request message, that is, an F1 standard interface message (such as UE Context Modification Required). The first message carries NUL carrier configuration information and indication information that instructs the UE to report the location of the DC subcarrier of the BWP of the NUL carrier.

Alternatively, the first message may include NUL carrier configuration information and request information, where the request information is used to request DC subcarrier location information of the BWP of the NUL carrier.

In step S340, after receiving the first message, the CU sends the NUL carrier configuration information and the indication information indicating that the UE reports the location of the DC subcarrier of the BWP of the NUL carrier to the UE through a reconfiguration message.

In step S350, after receiving the reconfiguration message, the UE sends a reconfiguration complete message to the CU.

The reconfiguration complete message carries the location information of the DC subcarrier of the BWP of the NUL carrier. Exemplarily, the location information of the DC subcarrier of the BWP of the NUL carrier may be carried in the UplinkTxDirectCurrentList information element.

In step S360, the CU sends the location information of the DC sub-carrier of the BWP of the NUL carrier to the DU, so that the DU can determine the location of the DC sub-carrier of the BWP.

Optionally, the location information of the DC subcarrier of the BWP of the NUL carrier may be carried in an F1 standard interface message, such as a UE Context Modification Confirm message.

Of course, the location information of the DC sub-carrier of the BWP of the NUL carrier can also be carried by other messages sent by the CU to the DU, for example, through the newly added F1 interface field after specific processing. The above UE Context Modification Confirm message is only an example, this application The message of the DC subcarrier location information of the BWP carrying the NUL carrier is not limited.

It should be understood that the number of BWPs corresponding to the above-mentioned NUL carrier may be one or multiple, which is not limited herein.

Step S370, after the DU determines the location of the DC subcarrier of the BWP of the NUL carrier according to the location information of the DC subcarrier of the BWP of the NUL carrier, the DU sets the RE corresponding to the location of the DC subcarrier to zero RE.

It should be understood that there may be multiple REs corresponding to the position of the DC subcarrier, and here at least one RE corresponding to the position of the DC subcarrier is set as a zero RE.

After the carrier switching is completed, the UE communicates with the base station in uplink through the NUL carrier.

The wireless communication interaction in Figures 2 and 3 is performed in the scenario of UE carrier switching in the independent networking mode. It should be noted that the NUL carrier initially accessed by the UE in Figure 2 is the first uplink carrier. The SUL carrier is the second uplink carrier, the SUL carrier initially accessed by the UE in FIG. 3 is the first uplink carrier, and the switched NUL carrier is the second uplink carrier, but this application does not limit the first uplink carrier and the second uplink carrier. As long as it is in the carrier switching scenario, the network equipment, such as the DU, can obtain the DC subcarrier location information of the BWP of the second uplink carrier, which belongs to the scope of protection of the present application.

FIG. 4 is a schematic diagram of a wireless communication system 400 in a non-standalone networking scenario applicable to an embodiment of the present application.

As shown in FIG. 4 , the wireless communication system 400 may include at least two network devices, for example, the network devices shown in FIG. 4 . The wireless communication system 400 may also include at least one terminal device, such as the terminal device shown in FIG. 4 . A wireless connection can be established between a terminal device and a network device and between a terminal device and a terminal device for wireless communication, and the sending device can indicate data scheduling information through control information, so that the receiving device can correctly receive data according to the control information.

It should be understood that the specific devices included in the terminal device are the same as those of the terminal device in FIG. 1 , and for the sake of brevity, details are not described herein.

It should be understood that the network equipment in the Long Term Evolution (LTE) system may include an evolved Node B (evolved Node B, eNB), a radio network controller (Radio Network Controller, RNC), a Node B (Node B, NB) ), Base Station Controller (BSC), Base Transceiver Station (BTS), Home Base Station (for example, Home evolved NodeB, or Home Node B, HNB), Base Band Unit (BBU) , Access Point (AP), Wireless Relay Node, Wireless Backhaul Node, Transmission Point (TP) or Transmission and Reception Point (Transmission and Reception Point) in Wireless Fidelity (WIFI) system , TRP) and so on.

The network device in the NR system is the network device in FIG. 1 , which is not described here for brevity.

FIG. 5 is a flowchart of wireless communication interaction in a non-independent networking scenario provided by an embodiment of the present application. It can be seen from FIG. 5 that the method 500 includes:

In step S510, the UE accesses from a NUL cell in an area with good uplink coverage, and enters a connected state.

It should be understood that the NUL cell accessed by the UE at this time belongs to the gNB. Before that, the UE may initially access the NUL cell of the eNB, and the eNB sends the UE an inter-system event measurement, instructing the UE to measure the signal of the gNB, and to The measurement report is fed back to the eNB. After receiving the inter-system measurement report reported by the UE, the eNB decides to add a gNB as a secondary base station for the UE, and sends the measurement report to the gNB at the same time. The gNB selects a NUL cell for the UE to access according to the signal strength in the measurement report, and enters the connected state. At this time, the UE communicates with the gNB through the NUL carrier.

In step S520, the DU determines that the UE has moved to an area with limited uplink coverage of the NUL cell, and at this time, the NUL carrier needs to be switched to the SUL carrier to improve the uplink throughput rate.

In step S530, the DU sends the first message to the CU.

Optionally, the first message is UE Context Modification Required. The first message carries SUL carrier configuration information and indication information that instructs the UE to report the location of the DC subcarrier of the BWP of the SUL carrier.

Alternatively, the first message may include SUL carrier configuration information and request information, where the request information is used to request location information of the DC subcarrier of the BWP of the SUL carrier.

In step S540, after receiving the first message, the CU sends the SUL carrier configuration information and the indication information indicating that the UE reports the location of the DC subcarrier of the BWP of the SUL carrier to the eNB through a secondary node modification request message (SgNB Modification Required).

In step S550, the eNB sends the received SUL carrier configuration information and the indication information indicating the location of the DC sub-carrier of the BWP of the SUL carrier reported by the UE to the UE through a reconfiguration message.

In step S560, after receiving the reconfiguration message, the UE sends a reconfiguration complete message to the eNB.

The reconfiguration complete message carries the location information of the DC subcarrier of the BWP of the SUL carrier. Exemplarily, the location information of the DC subcarrier of the BWP of the SUL carrier may be carried in the UplinkTxDirectCurrentList information element.

In step S570, the eNB sends a secondary node modification confirmation message (SgNB Modification Confirm) to the CU.

The secondary node change confirmation message carries the location information of the DC subcarrier of the BWP of the SUL carrier. Exemplarily, the location information of the DC subcarrier of the BWP of the SUL carrier may be carried in the UplinkTxDirectCurrentList information element.

In step S580, the CU sends the location information of the DC sub-carrier of the BWP of the SUL carrier to the DU, so that the DU can determine the location of the DC sub-carrier of the BWP.

Optionally, the location information of the DC subcarrier of the BWP of the SUL carrier may be carried in an F1 standard interface message, such as UE Context Modification Confirm.

The same as the independent networking scenario, the location information of the DC sub-carrier of the BWP of the SUL carrier can also be carried by other messages sent by the CU to the DU, such as the newly added F1 interface field after specific processing. The above UE Context Modification Confirm is only an example , the present application does not limit the message of the location information of the DC sub-carrier of the BWP carrying the SUL carrier.

It should be understood that the BWP corresponding to the above-mentioned SUL carrier may be one or multiple, which is not limited herein.

Step S590, after the DU determines the position of the DC subcarrier of the BWP of the SUL carrier according to the position information of the DC subcarrier of the BWP of the SUL carrier, the DU sets the RE corresponding to the position of the DC subcarrier to zero RE.

It should be understood that there may be multiple REs corresponding to the position of the DC subcarrier, and here at least one RE corresponding to the position of the DC subcarrier is set as a zero RE.

After the carrier switching is completed, the UE communicates with the gNB in uplink through the SUL carrier.

FIG. 6 is a flowchart of wireless communication interaction in a non-independent networking scenario provided by another embodiment of the present application. It can be seen from FIG. 6 that the method 600 includes:

In step S610, the UE initially accesses the SUL cell, and at this time, the UE communicates with the gNB through the SUL carrier.

In step S620, when the UE moves to an area with good uplink coverage, it is necessary to switch the SUL carrier to the NUL carrier.

In step S630, the DU sends the first message to the CU.

Optionally, the first message is UE Context Modification Required, and the first message carries NUL carrier configuration information and indication information indicating the location of the DC subcarrier of the BWP for the UE to report the NUL carrier.

Alternatively, the first message may be NUL carrier configuration information and request information, where the request information is used to request location information of the DC subcarrier of the BWP of the NUL carrier.

In step S640, after receiving the first message, the CU sends the NUL carrier configuration information and the indication information indicating that the UE reports the location of the DC subcarrier of the BWP of the NUL carrier to the eNB through SgNB Modification Required.

In step S650, the eNB sends the received NUL carrier configuration information and the indication information indicating the location of the DC sub-carrier of the BWP of the NUL carrier reported by the UE to the UE through a reconfiguration message.

In step S660, after receiving the reconfiguration message, the UE sends a reconfiguration complete message to the eNB.

The reconfiguration complete message carries the location information of the DC subcarrier of the BWP of the NUL carrier. Exemplarily, the location information of the DC subcarrier of the BWP of the NUL carrier may be carried in the UplinkTxDirectCurrentList information element.

In step S670, the eNB sends a secondary node modification confirmation message (SgNB Modification Confirm) to the CU.

The message carries the location information of the DC sub-carrier of the BWP of the NUL carrier. Exemplarily, the location information of the DC subcarrier of the BWP of the NUL carrier may be carried in the UplinkTxDirectCurrentList information element.

In step S680, the CU sends the location information of the DC subcarrier of the BWP of the NUL carrier to the DU, so that the DU can determine the location of the DC subcarrier of the BWP.

Optionally, the location information of the DC subcarrier of the BWP of the NUL carrier may be carried in an F1 standard interface message, such as UE Context Modification Confirm.

In the same independent networking scenario, the location information of the DC sub-carrier of the BWP of the NUL carrier can also be carried by other messages sent by the CU to the DU, such as the newly added F1 interface field after specific processing. The above UE Context Modification Confirm is only an example , this application does not limit the message of the DC subcarrier location information of the BWP bearing the NUL carrier.

It should be understood that the number of BWPs corresponding to the above-mentioned NUL carrier may be one or multiple, which is not limited herein.

Step S690, after the DU determines the position of the DC subcarrier corresponding to the BWP of the NUL carrier according to the position information of the DC subcarrier of the BWP of the NUL carrier, the DU sets the RE corresponding to the position of the DC subcarrier to zero RE.

It should be understood that there may be multiple REs corresponding to the position of the DC subcarrier, and here at least one RE corresponding to the position of the DC subcarrier is set as a zero RE.

After the carrier switching is completed, the UE communicates with the gNB in uplink through the NUL carrier.

Same as above, the wireless communication interaction in Figure 5 and Figure 6 is performed in the scenario of UE carrier switching in the independent networking mode. It should be noted that the NUL carrier initially accessed by the UE in Figure 5 is the first uplink carrier. The subsequent SUL carrier is the second uplink carrier, the SUL carrier initially accessed by the UE in FIG. 6 is the first uplink carrier, and the switched NUL carrier is the first uplink carrier, but this application does not limit the first uplink carrier and the second uplink carrier. As long as the carrier is in the carrier switching scenario, the network device, such as the DU, can obtain the location information of the DC subcarrier of the BWP of the second uplink carrier, which belongs to the scope of protection of this application.

It should be understood that setting RE to zero in the above-mentioned embodiment may be performed by means of a log-likelihood ratio (Log-likelihood Ratio, LLR).

Based on the above solution, in the scenario of uplink carrier switching, the DU can know the location of the DC subcarrier of the BWP of the second uplink carrier, so that the DU can determine the location of the DC subcarrier when dealing with interference caused by local oscillator signal leakage. Then, the DU can set at least one resource element RE corresponding to the DC subcarrier to zero RE through log-likelihood ratio or other methods, that is to say, no data is sent on at least one RE corresponding to the DC subcarrier, so as to solve the problem. The interference caused by the local oscillator signal leaking to the output port or input port at the RE.

The methods provided by the embodiments of the present application have been described in detail above with reference to FIGS. 1 to 6 . It can be understood that each network element, for example, a terminal device or a network device, includes corresponding hardware structures and/or software modules for performing each function in order to implement the above-mentioned functions. Those skilled in the art should realize that the present application can be implemented in hardware or a combination of hardware and computer software with the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein. Whether a function is performed by hardware or computer software driving hardware depends on the specific application and design constraints of the technical solution. Skilled artisans may implement the described functionality using different methods for each particular application, but such implementations should not be considered beyond the scope of this application.

In this embodiment of the present application, the transmitting-end device or the receiving-end device may be divided into functional modules according to the foregoing method examples. For example, each functional module may be divided corresponding to each function, or two or more functions may be integrated into one processing module. middle. The above-mentioned integrated modules can be implemented in the form of hardware, or can be implemented in the form of software function modules. It should be noted that, the division of modules in the embodiments of the present application is schematic, and is only a logical function division, and there may be other division manners in actual implementation. The following description will be given by using the division of each function module corresponding to each function as an example.

Hereinafter, the device provided by the embodiment of the present application will be described in detail with reference to FIG. 7 to FIG. 10 . It should be understood that the description of the apparatus embodiment corresponds to the description of the method embodiment. Therefore, for the content not described in detail, reference may be made to the above method embodiment, which is not repeated here for brevity.

FIG. 7 is a schematic block diagram of a terminal device provided by an embodiment of the present application.

The terminal device 700 may correspond to the terminal device in the method 200 , 300 , 500 or 600 of the embodiments of the present application, and the terminal device 700 may include a unit for executing the method performed by the terminal device in the method 200 , 300 , 500 or 600 . Moreover, each unit in the terminal device and the above-mentioned other operations and/or functions are to implement the corresponding flow of the method 200, 300, 500 or 600, respectively.

As shown in Figure 7, the terminal device includes a transceiver unit and a processing unit. The transceiver unit is configured to receive indication information from a network device, the indication information instructing the terminal device to send location information of the DC sub-carrier of the BWP of the second uplink carrier, and to send the DC sub-carrier of the BWP of the second uplink carrier to the network device Location information of the carrier.

Optionally, the location information of the DC subcarrier is carried in the reconfiguration complete message, and the indication information is carried in the reconfiguration message or the secondary node change request message.

It should also be understood that the transceiver unit in the terminal device may correspond to the transceiver in the terminal device shown in FIG. 9 , and the processing unit in the terminal device may correspond to the processor in the terminal device shown in FIG. 9 .

It should also be understood that the transceiver unit in the terminal device may be implemented through a communication interface (such as a transceiver or an input/output interface), for example, it may correspond to the transceiver in the terminal device shown in FIG. The unit may be implemented by at least one processor, for example, may correspond to the processor in the terminal device shown in FIG. 9 , and the processing unit in the terminal device may also be implemented by at least one logic circuit.

Optionally, the terminal device may further include a storage unit, which may be used to store instructions or data, and the processing unit may call the instructions or data stored in the storage unit to implement corresponding operations.

It should be understood that for the beneficial effects of the foregoing apparatus, reference may be made to the descriptions in the foregoing method embodiments, which are not repeated here for brevity.

FIG. 8 is a schematic block diagram of a network device provided by an embodiment of the present application.

It should be understood that the network device 800 may correspond to the DU in the method 200 , 300 , 500 or 600 in the embodiments of the present application, and the network device may include a unit for executing the method performed by the network device in the method 200 , 300 , 500 or 600 . Moreover, each unit in the network device and the above-mentioned other operations and/or functions are to implement the corresponding flow of the method 200, 300, 500 or 600, respectively.

As shown in FIG. 8 , the network device may include a transceiver unit and a processing unit, where the transceiver unit is configured to receive location information of the DC sub-carrier corresponding to the BWP of the second uplink carrier from the CU, and the processing unit is configured to receive the location information of the DC sub-carrier according to the DC sub-carrier. The location information of the carrier determines the location of the DC subcarrier, and the processing unit is further configured to set at least one RE corresponding to the DC subcarrier to a zero resource element.

Optionally, before the transceiver unit receives the location information of the DC DC subcarrier of the BWP of the second uplink carrier from the CU, the transceiver unit sends the second uplink carrier configuration information and a request message to the CU, and the request message is used for Request the DC subcarrier location information of the BWP of the second uplink carrier.

Optionally, the location information of the above-mentioned DC subcarriers is carried in the user equipment context change confirmation message.

It should be understood that the network device 800 may also correspond to the CU in the method 200 , 300 , 500 or 600 of the embodiments of the present application, and the network device may include a unit for executing the method performed by the CU in the method 200 , 300 , 500 or 600 . Moreover, each unit in the network device and the above-mentioned other operations and/or functions are to implement the corresponding flow of the method 200, 300, 500 or 600, respectively.

The network device may include a transceiver unit and a processing unit, the transceiver unit is configured to send indication information, instructing the terminal device to send the location information of the DC sub-carrier of the BWP of the second uplink carrier, and the transceiver unit is further configured to receive the information from the terminal device. The location information of the DC subcarrier of the BWP of the second uplink carrier, and the location information of the DC subcarrier is sent to the DU.

Optionally, before sending the indication information, the transceiver unit receives configuration information of the second uplink carrier and a request message from the DU, where the request message is used to request DC subcarrier location information of the BWP of the second uplink carrier.

Specifically, the location information of the DC subcarrier sent by the CU to the DU may be carried in the user equipment context change confirmation message. The indication information may be carried in the reconfiguration message or the secondary node change request message. The location information of the DC subcarrier received by the CU may be carried in the reconfiguration complete message or the secondary node change confirmation message.

It should also be understood that the transceiver unit in the network device may correspond to the transceiver in the network device shown in FIG. 10 , and the processing unit in the network device may correspond to the processor in the network device shown in FIG. 10 . .

Optionally, the network device may further include a storage unit, where the storage unit may be used to store instructions or data, and the processing unit may call the instructions or data stored in the storage unit to implement corresponding operations.

It should also be understood that the transceiver unit in the network device may be implemented through a communication interface (such as a transceiver or an input/output interface), for example, it may correspond to the transceiver in the network device shown in FIG. The processing unit may be implemented by at least one processor, for example, may correspond to the processor in the network device shown in FIG. 10 , and the processing unit in the network device may be implemented by at least one logic circuit.

FIG. 9 is a schematic structural diagram of a terminal device provided by an embodiment of the present application. The terminal device can be applied to the system as shown in FIG. 1 or 4, and performs the functions of the terminal device in the foregoing method embodiments. As shown in Figure 9, the terminal device includes a processor and a transceiver. Optionally, the terminal device further includes a memory. Wherein, the processor, the transceiver and the memory can communicate with each other through an internal connection path to transmit control and/or data signals, the memory is used to store a computer program, and the processor is used to call and run the computer program from the memory, to control the transceiver to send and receive signals. Optionally, the terminal device may further include an antenna for sending the uplink data or uplink control signaling output by the transceiver through wireless signals.

The above-mentioned processor and the memory can be combined into a processing device, and the processor is configured to execute the program codes stored in the memory to realize the above-mentioned functions. During specific implementation, the memory can also be integrated in the processor, or be independent of the processor. The processor may correspond to the processing unit in FIG. 7 .

The above transceiver may correspond to the transceiver unit in FIG. 7 . A transceiver may include a receiver (or receiver, receiving circuit) and a transmitter (or transmitter, transmitting circuit). Among them, the receiver is used for receiving signals, and the transmitter is used for transmitting signals.

It should be understood that the terminal device shown in FIG. 9 can implement each process involving the terminal device in the methods 200 , 300 , 500 or 600 . The operations and/or functions of each module in the terminal device are respectively to implement the corresponding processes in the foregoing method embodiments. For details, reference may be made to the descriptions in the foregoing method embodiments, and to avoid repetition, the detailed descriptions are appropriately omitted here.

The above-mentioned processor may be used to perform the actions described in the foregoing method embodiments implemented by the terminal device, and the transceiver may be used to perform the actions described in the foregoing method embodiments that the terminal device sends to or receives from the network device. For details, please refer to the descriptions in the foregoing method embodiments, which will not be repeated here.

Optionally, the above-mentioned terminal device may further include a power supply for providing power to various devices or circuits in the terminal device.

FIG. 10 is a schematic structural diagram of a network device (CU or DU) provided by an embodiment of the present application. The network device can be applied to the system shown in FIG. 1 or 4, and performs the functions of the network device in the foregoing method embodiments. As shown in Figure 10, the network device includes a processor and a transceiver. Optionally, the network device further includes a memory. Wherein, the processor, the transceiver and the memory can communicate with each other through an internal connection path to transmit control and/or data signals, the memory is used to store a computer program, and the processor is used to call and run the computer program from the memory, to control the transceiver to send and receive signals. Optionally, the network device may further include an antenna, configured to send the downlink data or downlink control signaling output by the transceiver through wireless signals.

The above-mentioned processor and the memory can be combined into a processing device, and the processor is configured to execute the program codes stored in the memory to realize the above-mentioned functions. During specific implementation, the memory can also be integrated in the processor, or be independent of the processor. The processor may correspond to the processing unit in FIG. 8 .

The above transceiver may correspond to the transceiver unit in FIG. 8 . A transceiver may include a receiver (or receiver, receiving circuit) and a transmitter (or transmitter, transmitting circuit). Among them, the receiver is used for receiving signals, and the transmitter is used for transmitting signals.

It should be understood that the network device shown in FIG. 10 can implement each process involving the CU and DU in the method 200 , 300 , 500 or 600 . The operations and/or functions of each module in the network device are respectively to implement the corresponding processes in the foregoing method embodiments. For details, reference may be made to the descriptions in the foregoing method embodiments, and to avoid repetition, the detailed descriptions are appropriately omitted here.

The above-mentioned processor may be used to perform the actions implemented by the network device described in the foregoing method embodiments, and the transceiver may be used to execute the actions described in the foregoing method embodiments that the network device sends to or receives from the terminal device. For details, please refer to the descriptions in the foregoing method embodiments, which will not be repeated here.

Optionally, the above-mentioned network device may further include a power supply for providing power to various devices or circuits in the network device.

It should be understood that the network device shown in FIG. 10 is only a possible architecture of the network device, and should not constitute any limitation to the present application. The methods provided in this application may be applicable to network devices of other architectures. For example, CU, DU, or a network device including CU and DU, etc. This application does not limit the specific architecture of the network device.

Embodiments of the present application also provide a communication device, including a processor and an interface. The processor is coupled to the interface, and the interface is used for inputting and/or outputting information, and the processor is used for executing the method in any of the above method embodiments.

It should be understood that when the communication device is a network device or a terminal device, the interface may be a transceiver, or an input/output interface. When the communication device is a chip or a chip system, the interface may be an input/output interface, an interface circuit, an output circuit, an input circuit, a pin or a related circuit on the chip or a chip system.

It should also be understood that the above-mentioned processing device may be one or more chips. For example, the processing device may be a field programmable gate array (FPGA), an application specific integrated circuit (ASIC), a system on chip (SoC), or a It is a central processing unit (CPU), a network processor (NP), a digital signal processing circuit (DSP), or a microcontroller (microcontroller unit). , MCU), it can also be a programmable logic device (PLD) or other integrated chips.

In the implementation process, each step of the above-mentioned method can be completed by a hardware integrated logic circuit in a processor or an instruction in the form of software. The steps of the methods disclosed in conjunction with the embodiments of the present application may be directly embodied as executed by a hardware processor, or executed by a combination of hardware and software modules in the processor. The software modules may be located in random access memory, flash memory, read-only memory, programmable read-only memory or electrically erasable programmable memory, registers and other storage media mature in the art. The storage medium is located in the memory, and the processor reads the information in the memory, and completes the steps of the above method in combination with its hardware. To avoid repetition, detailed description is omitted here.

It should be noted that the processor in this embodiment of the present application may be an integrated circuit chip, which has a signal processing capability. In the implementation process, each step of the above method embodiments may be completed by a hardware integrated logic circuit in a processor or an instruction in the form of software. The aforementioned processors may be general purpose processors, digital signal processors (DSPs), application specific integrated circuits (ASICs), field programmable gate arrays (FPGAs) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components . The methods, steps, and logic block diagrams disclosed in the embodiments of this application can be implemented or executed. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like. The steps of the method disclosed in conjunction with the embodiments of the present application may be directly embodied as executed by a hardware decoding processor, or executed by a combination of hardware and software modules in the decoding processor. The software modules may be located in random access memory, flash memory, read-only memory, programmable read-only memory or electrically erasable programmable memory, registers and other storage media mature in the art. The storage medium is located in the memory, and the processor reads the information in the memory, and completes the steps of the above method in combination with its hardware.

It can be understood that the memory in this embodiment of the present application may be a volatile memory or a non-volatile memory, or may include both volatile and non-volatile memory. The non-volatile memory may be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically programmable Erase programmable read-only memory (electrically EPROM, EEPROM) or flash memory. Volatile memory may be random access memory (RAM), which acts as an external cache. By way of example and not limitation, many forms of RAM are available, such as static random access memory (SRAM), dynamic random access memory (DRAM), synchronous DRAM, SDRAM), double data rate synchronous dynamic random access memory (double data rate SDRAM, DDR SDRAM), enhanced synchronous dynamic random access memory (enhanced SDRAM, ESDRAM), synchronous link dynamic random access memory (synchlink DRAM, SLDRAM) ) and direct memory bus random access memory (direct rambus RAM, DR RAM). It should be noted that the memory of the systems and methods described herein is intended to include, but not be limited to, these and any other suitable types of memory.

According to the method provided by the embodiment of the present application, the present application also provides a computer program product, the computer program product includes: computer program code, when the computer program code is run on a computer, the computer is made to execute Fig. 2, 3, 5 or the method in the embodiment shown in 6.

According to the method provided by the embodiments of the present application, the present application further provides a computer-readable medium, where the computer-readable medium stores program codes, and when the program codes run on a computer, causes the computer to execute Figs. 2 , 3 , and 5 or the method in the embodiment shown in 6.

According to the method provided by the embodiment of the present application, the present application further provides a system, which includes the aforementioned one or more terminal devices and one or more network devices.

The network equipment in each of the above apparatus embodiments completely corresponds to the terminal equipment and the network equipment or terminal equipment in the method embodiments, and corresponding steps are performed by corresponding modules or units. For the sending step, other steps except sending and receiving may be performed by a processing unit (processor). For functions of specific units, reference may be made to corresponding method embodiments. The number of processors may be one or more.

The terms "component", "module", "system" and the like are used in this specification to refer to a computer-related entity, hardware, firmware, a combination of hardware and software, software, or software in execution. For example, a component may be, but is not limited to, a process running on a processor, a processor, an object, an executable, a thread of execution, a program, and/or a computer. By way of illustration, both an application running on a computing device and the computing device may be components. One or more components may reside within a process and/or thread of execution, and a component may be localized on one computer and/or distributed between 2 or more computers. In addition, these components can execute from various computer readable media having various data structures stored thereon. A component may, for example, be based on a signal having one or more data packets (eg, data from two components interacting with another component between a local system, a distributed system, and/or a network, such as the Internet interacting with other systems via signals) Communicate through local and/or remote processes.

Those of ordinary skill in the art can realize that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of 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. Skilled artisans may implement the described functionality using different methods for each particular application, but such implementations should not be considered beyond the scope of this application.

In the several embodiments provided in this application, it should be understood that the disclosed system, apparatus and method may be implemented in other manners. For example, the apparatus embodiments described above are only illustrative. For example, the division of the unit is only a logical function division. In actual implementation, there may be other division methods, for example, multiple units or components may be combined or Integration into another system, or some features can be ignored, or not implemented. On the other hand, the shown or discussed mutual coupling or direct coupling or communication connection may be through some interfaces, indirect coupling or communication connection of devices or units, and may be in electrical, mechanical or other forms.

Units described as separate components may or may not be physically separated, and components shown as units may or may not be physical units, that is, may be located in one place, or may be distributed to multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solutions of the embodiments of the present application.

In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically alone, or two or more units may be integrated into one unit.

In the above embodiments, the functions of each functional unit may be implemented in whole or in part by software, hardware, firmware, or any combination thereof. When implemented in software, it can be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions (programs). When the computer program instructions (programs) are loaded and executed on the computer, all or part of the processes or functions according to the embodiments of the present application are generated. The computer may be a general purpose computer, a special purpose computer, a computer network, or other programmable device. The computer instructions may be stored on or transmitted from one computer readable storage medium to another computer readable storage medium, for example, the computer instructions may be transmitted over a wire from a website site, computer, server or data center (eg coaxial cable, fiber optic, digital subscriber line (DSL)) or wireless (eg infrared, wireless, microwave, etc.) to another website site, computer, server or data center. The computer-readable storage medium can be any available medium that can be accessed by a computer or a data storage device such as a server, data center, etc. that includes one or more available media integrated. The available media may be magnetic media (eg, floppy disks, hard disks, magnetic tapes), optical media (eg, DVDs), or semiconductor media (eg, solid state disks (SSDs)), and the like.

If the function is implemented in the form of a software functional unit and sold or used as an independent product, it may be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application can be embodied in the form of a software product in essence, or the part that contributes to the prior art or the part of the technical solution. The computer software product is stored in a storage medium, including Several instructions are used to cause a computer device (which may be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the method of the present application. The aforementioned storage medium includes: U disk, mobile hard disk, read-only memory (ROM), random access memory (RAM), magnetic disk or optical disk and other media that can store program codes .

The above are only specific embodiments of the present application, but the protection scope of the present application is not limited to this. Any person skilled in the art can easily think of changes or substitutions within the technical scope disclosed in the present application, All should be covered within the scope of protection of this application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims and the description.

Claims (33)

1. A communication method, comprising:

   The distributed unit DU communicates with the terminal device through the first uplink carrier;

   The DU receives the location information of the DC sub-carrier of the partial bandwidth BWP of the second uplink carrier from the centralized unit CU;

   The DU determines the location of the DC subcarrier according to the location information of the DC subcarrier.
2. The method according to claim 1, wherein the method further comprises:

   The DU sets at least one resource element RE corresponding to the DC subcarrier to zero RE.
3. The method according to claim 1 or 2, wherein before the DU receives the location information of the DC subcarrier of the BWP of the second uplink carrier of the CU, the method further comprises:

   The DU sends the second uplink carrier configuration information and a request message to the CU, where the request message is used to request location information of the DC subcarrier of the BWP of the second uplink carrier.
4. The method according to any one of claims 1 to 3, wherein the location information of the DC subcarrier is carried in a user equipment context change confirmation message.
5. A communication method, comprising:

   The centralized unit CU communicates with the terminal equipment through the first uplink carrier;

   The CU sends indication information, the indication information instructs the terminal device to send the location information of the DC sub-carrier of the partial bandwidth BWP of the second uplink carrier;

   receiving, by the CU, location information of the DC subcarrier of the BWP of the second uplink carrier from the terminal device;

   The CU sends the location information of the DC subcarrier of the BWP of the second uplink carrier to the distributed unit DU.
6. The method according to claim 5, wherein the location information of the DC subcarrier is used to indicate that the resource element RE corresponding to the location of the DC subcarrier is set as a zero RE.
7. The method according to claim 5 or 6, wherein before the CU sends the indication information, the method further comprises:

   The CU receives the second uplink carrier configuration information and a request message from the DU, where the request message is used to request DC subcarrier location information of the BWP of the second uplink carrier.
8. The method according to any one of claims 5 to 7, wherein the location information of the DC subcarrier sent by the CU to the DU is carried in a user equipment context change confirmation message.
9. The method according to any one of claims 5 to 8, wherein the indication information is carried in a reconfiguration message or a secondary node change request message.
10. The method according to any one of claims 5 to 9, wherein the location information of the DC subcarrier received by the CU is carried in a reconfiguration complete message or a secondary node change confirmation message.
11. A communication method, comprising:

    The terminal device communicates with the network device through the first uplink carrier;

    receiving, by the terminal device, indication information from the network device, where the indication information instructs the terminal device to send location information of the DC sub-carrier of the partial bandwidth BWP of the second uplink carrier;

    sending, by the terminal device, the location information of the DC subcarrier of the BWP of the second uplink carrier;

    The terminal device communicates with the network device through the second uplink carrier.
12. The method according to claim 11, wherein the location information of the DC subcarrier is carried in a reconfiguration complete message.
13. The method according to claim 11 or 12, wherein the indication information is carried in a reconfiguration message or a secondary node change request message.
14. The method according to any one of claims 11 to 13, wherein the first uplink carrier is a normal uplink carrier NUL, and the second uplink carrier is an extended uplink carrier SUL.
15. A communication device, comprising:

    a transceiver unit, which communicates with the terminal device through the first uplink carrier;

    the transceiver unit, configured to receive the location information of the direct current DC sub-carrier of the partial bandwidth BWP of the second uplink carrier from the centralized unit CU;

    The processing unit is configured to determine the position of the DC sub-carrier according to the position information of the DC sub-carrier.
16. The apparatus according to claim 15, wherein the processing unit is further configured to set at least one resource element RE corresponding to the DC subcarrier to a zero RE.
17. The device according to claim 15 or 16, characterized in that,

    The transceiver unit is further configured to send the second uplink carrier configuration information and a request message to the CU before receiving the location information of the DC subcarrier of the BWP of the second uplink carrier from the CU, the request The message is used to request the location information of the DC subcarrier of the BWP of the second uplink carrier.
18. The apparatus according to any one of claims 15 to 17, wherein the location information of the DC subcarrier is carried in a user equipment context change confirmation message.
19. A communication device, comprising:

    a transceiver unit, which communicates with the terminal device through the first uplink carrier;

    the transceiver unit, configured to send indication information, the indication information instructing the terminal device to send the location information of the DC sub-carrier of the partial bandwidth BWP of the second uplink carrier;

    The transceiver unit is further configured to receive location information of the DC subcarrier of the BWP of the second uplink carrier from the terminal device;

    The transceiver unit is further configured to send the location information of the DC subcarrier corresponding to the BWP of the second uplink carrier to the distributed unit DU.
20. The apparatus according to claim 19, wherein the location information of the DC subcarrier is used to indicate that the resource element RE corresponding to the location of the DC subcarrier is set to a zero RE.
21. The device according to claim 19 or 20, characterized in that,

    The transceiver unit is further configured to receive the second uplink carrier configuration information and a request message from the DU before sending the indication information, where the request message is used to request the BWP of the second uplink carrier. Location information of DC subcarriers.
22. The apparatus according to any one of claims 19 to 21, wherein the location information of the DC subcarrier sent by the transceiver unit is carried in a user equipment context change confirmation message.
23. The apparatus according to any one of claims 19 to 22, wherein the indication information is carried in a reconfiguration message or a secondary node change request message.
24. The apparatus according to any one of claims 19 to 23, wherein the location information of the DC subcarrier received by the transceiver unit is carried in a reconfiguration complete message or a secondary node change confirmation message.
25. A communication device, characterized in that it includes:

    a transceiver unit, which communicates with the network device through the first uplink carrier;

    The transceiver unit is configured to receive indication information from the network device, where the indication information instructs the terminal device to send location information of the DC sub-carrier of the partial bandwidth BWP of the second uplink carrier;

    The transceiver unit is further configured to send location information of the DC subcarrier of the BWP of the second uplink carrier;

    The transceiver unit communicates with the network device through the second uplink carrier.
26. The apparatus according to claim 25, wherein the location information of the DC subcarrier is carried in a reconfiguration complete message.
27. The apparatus according to claim 25 or 26, wherein the indication information is carried in a reconfiguration message or a secondary node change request message.
28. The apparatus according to any one of claims 15 to 27, wherein the first uplink carrier is a normal uplink carrier NUL, and the second uplink carrier is an extended uplink carrier SUL.
29. A communication device, characterized in that it includes:

    memory for storing computer instructions;

    a processor for executing computer instructions stored in the memory to cause the means for communicating to perform a method as claimed in any one of claims 1 to 4 or to perform any one of claims 5 to 10 The method as claimed in any one of claims 11 to 14 is performed.
30. A communication device, characterized in that, the communication device is configured to execute the method as claimed in any one of claims 1 to 4 or execute the method as claimed in any one of claims 5 to 10 or execute the method as claimed in any one of claims 5 to 10. The method of any one of claims 11 to 14.
31. A communication device, characterized by comprising: at least one processor and an interface circuit, and a related computer program is executed in the at least one processor, so that the communication device performs any one of claims 1 to 4 The described method either performs a method as claimed in any one of claims 5 to 10 or performs a method as claimed in any one of claims 11 to 14 .
32. A computer-readable storage medium, characterized in that a computer program is stored thereon, and when the computer program is executed by an apparatus for communication, the apparatus for communication is made to execute any one of claims 1 to 4. Item 1 or perform a method as claimed in any one of claims 5 to 10 or perform a method as claimed in any one of claims 11 to 14.
33. A computer program product, characterized in that the computer program product comprises: computer program code, which, when the computer program code is run on a computer, causes the computer to execute the method according to any one of claims 1 to 4 Either perform a method as claimed in any one of claims 5 to 10 or perform a method as claimed in any one of claims 11 to 14 .

Images