WO2025167568A1 - Communication method and related device - Google Patents

Abstract

Embodiments of the present application provide a communication method and a related device. A terminal device sends first indication information to a network device, wherein the first indication information is used for indicating that the terminal device supports that a first long term evolution (LTE) carrier is non-contiguous with a first new radio (NR) carrier, and the first LTE carrier and the first NR carrier are two carriers in intra-band EN-DC. The terminal device receives configuration information sent by the network device, and accesses a network on the basis of a first rule and the configuration information, wherein the configuration information is used for configuring the first LTE carrier and the first NR carrier, and the first rule comprises: nominal channel spacing is equal to the channel spacing between an LTE carrier and an NR carrier in intra-band non-contiguous EN-DC, wherein the nominal channel spacing is the channel spacing between an LTE carrier and an NR carrier adjacent to each other in intra-band contiguous EN-DC. The first rule can enable a terminal device that reports the capability of only supporting that an LTE carrier and an NR carrier in intra-band EN-DC are non-contiguous can access a network that only supports that the LTE carrier and the NR carrier in the intra-band EN-DC are contiguous.

Description

A communication method and related equipment

This application claims priority to the Chinese patent application filed with the State Intellectual Property Office on February 7, 2024, with application number 202410175868.9 and application name “A Communication Method and Related Equipment”, the entire contents of which are incorporated by reference into this application.

Technical Field

The present application relates to the field of communications, and in particular to a communication method and related equipment.

Background Art

In the Long Term Evolution (LTE) system, terminal devices support simultaneous access to two network devices, an access method called dual connectivity (DC), where one network device serves as the primary network device and the other as the secondary network device. As wireless communication systems evolve, operators will deploy both 5G New Radio Interface (NR) and LTE systems. Terminal devices also support simultaneous access to both LTE and NR network devices. LTE is also known as evolved universal terrestrial radio access (E-UTRA), so this access method can be referred to as E-UTRA NR dual connectivity (EN-DC). In EN-DC mode, the LTE network device serves as the primary network device, and the NR network device serves as the secondary network device.

EN-DC combinations are further divided into intra-band EN-DC combinations and inter-band EN-DC combinations. Among them, the intra-band EN-DC combination means that at least one LTE carrier and at least one NR carrier in the same frequency band form a dual-connection combination. In this combination, the terminal device can report capability information to the network, and the capability information is used to indicate the continuity between adjacent LTE carriers and NR carriers. For example, if the capability information reported by the terminal device indicates non-contiguous, non-contiguous is supported. For another example, if the capability information reported by the terminal device indicates non-contiguous and contiguous (or understood as both), both contiguous and discontinuous are supported. For another example, if the terminal device does not report this capability information, only contiguous is supported by default.

However, some special networks may only support contiguous intra-band carriers. If a terminal device reports that only discontinuous carriers are supported, the terminal device will not be able to access the network, thus affecting the normal use of the terminal device.

Summary of the Invention

The present application provides a communication method and related devices, which enable a terminal device that only reports that the LTE carrier and NR carrier supporting intra-band EN-DC are discontinuous to access a network that only supports intra-band EN-DC and that has continuous LTE and NR carriers, through a first rule. The first rule is that the nominal channel spacing is equal to the channel spacing between the LTE carrier and the NR carrier in intra-band discontinuous EN-DC.

In a first aspect, the present application provides a communication method, which is executed by a terminal device, or the method is executed by some components in the terminal device (such as a processor, a chip or a chip system, etc.), or the method can also be implemented by a logic module or software that can realize all or part of the terminal device functions. In the first aspect and its possible implementation, the method is described as an example of being executed by a terminal device. In this method, the terminal device sends a first indication information to a network device, and the first indication information is used to indicate that the terminal device supports the first long-term evolution LTE carrier and the first new air interface NR carrier to be discontinuous, and the first LTE carrier and the first NR carrier are two carriers in the intra-band EN-DC. The terminal device receives the configuration information sent by the network device and accesses the network according to the first rule and the configuration information. The configuration information is used to configure the first LTE carrier and the first NR carrier. The first rule includes: the nominal channel spacing is equal to the channel spacing between the LTE carrier and the NR carrier in the intra-band discontinuous EN-DC, and the nominal channel spacing is the channel spacing between adjacent LTE carriers and NR carriers in the intra-band continuous EN-DC.

Based on the above scheme, the first rule can enable terminal devices that only report that the LTE and NR carriers that support in-band EN-DC are discontinuous to access a network where the LTE and NR carriers that only support in-band EN-DC are continuous. The first rule is that the nominal channel spacing is equal to the channel spacing between the LTE carrier and the NR carrier in the in-band discontinuous EN-DC. That is, the existing continuous situation is regarded as a special case of the discontinuous situation. This also meets the current actual needs, that is, the discontinuous capability of the terminal device should support both continuous and discontinuous networks.

The second aspect of the present application provides a communication method, which is executed by a network device, or the method is executed by some components in the network device (such as a processor, a chip or a chip system, etc.), or the method can also be implemented by a logic module or software that can realize all or part of the network device functions. In the second aspect and its possible implementation, the method is described as an example of being executed by a network device. In this method, the network device receives first indication information sent by a terminal device. The first indication information is used to indicate that the terminal device supports the first long-term evolution LTE carrier and the first new air interface NR carrier to be discontinuous, and the first LTE carrier and the first NR carrier are two carriers in the intra-band EN-DC. The network device sends configuration information according to the first rule, and the configuration information is used to configure the first LTE carrier and the first NR carrier; the first rule includes: the nominal channel spacing is equal to the channel spacing between the LTE carrier and the NR carrier in the intra-band discontinuous EN-DC, and the nominal channel spacing is the channel spacing between adjacent LTE carriers and NR carriers in the intra-band continuous EN-DC.

Based on the above scheme, the first rule can enable terminal devices that only report that the LTE carrier and NR carrier supporting in-band EN-DC are discontinuous to access a network where the LTE and NR carriers supporting in-band EN-DC are continuous. The first rule is that the nominal channel spacing is equal to the channel spacing between the LTE carrier and the NR carrier in the in-band discontinuous EN-DC. That is, the existing continuous situation is regarded as a special case of the discontinuous situation. This also meets the current actual needs, that is, the discontinuous capability of the terminal device should support both continuous and discontinuous networks.

Optionally, in a possible implementation of the first aspect or the second aspect, the above-mentioned first indication information is also used to indicate that the terminal device supports the continuity of the first LTE carrier and the first NR carrier.

In this possible implementation, the method can be applied not only to the case where the terminal device only supports discontinuous, but also to the case where the terminal device supports both continuous and discontinuous (or understood as both), so that the method can be applied to terminal devices with different capabilities, thereby improving the breadth of application scenarios.

Optionally, in a possible implementation of the first aspect or the second aspect, the above-mentioned first indication information is also used to indicate the frequency band identifier, the bandwidth level of the first LTE carrier, and the bandwidth level of the first NR carrier in the in-band EN-DC scenario.

In this possible implementation, the first indication information may also specifically indicate the frequency band identifier, bandwidth level, etc., so as to facilitate the network device to configure the first LTE carrier and the first NR carrier for the terminal device that are more suitable for the terminal device.

Optionally, in a possible implementation of the first aspect or the second aspect, the above-mentioned configuration information specifically includes at least one of the following: the frequency domain position or the number of resource blocks of the first LTE carrier and the first NR carrier.

In this possible implementation, by configuring the frequency domain position or the number of resource blocks of the carrier, etc., the terminal device can clearly understand the configuration of the carrier, thereby improving the efficiency of the terminal device accessing the network.

Optionally, in a possible implementation of the first aspect or the second aspect, the first LTE carrier and the first NR carrier include a downlink carrier and/or an uplink carrier.

This possible implementation can be applied not only to the configuration or communication of uplink carriers, but also to the configuration or communication of downlink carriers, thereby increasing the breadth of application scenarios.

The third aspect of the present application provides a communication method, which is executed by a terminal device, or the method is executed by some components in the terminal device (such as a processor, a chip or a chip system, etc.), or the method can also be implemented by a logic module or software that can realize all or part of the terminal device functions. In the third aspect and its possible implementation, the method is described as an example of being executed by a terminal device. In this method, the terminal device sends a first indication information to a network device. The first indication information is used to indicate that the terminal device supports the discontinuity of the first long-term evolution LTE carrier and the first new air interface NR carrier, and the first LTE carrier and the first NR carrier are two carriers in the intra-band EN-DC. The terminal device receives the configuration information sent by the network device, and the configuration information is used to configure the first LTE carrier and the first NR carrier; the terminal device accesses the network based on the configuration information and the second protection band, the second protection band is the protection band supported by the terminal device, the second protection band is smaller than the first protection band, and the first protection band is a predefined protection band corresponding to any channel bandwidth and subcarrier spacing.

Based on the above solution, by limiting the second protection band supported by the terminal device to be smaller than the first protection band defined in the existing standard, the radio frequency indicators can be met.

Optionally, in a possible implementation manner of the third aspect, the above steps further include: sending second indication information, where the second indication information is used to indicate a second protection band supported by the terminal device.

In this possible implementation, the terminal device can report the second indication information so that the network device can clearly understand the second protection band supported by the terminal device, thereby meeting the radio frequency indicators.

Optionally, in a possible implementation of the third aspect, the difference between the first guard band and the second guard band is at least one frequency domain unit, and the frequency domain unit includes any one of the following: resource block, grid, subcarrier spacing.

In this possible implementation, it can be understood as indirectly indicating at least one frequency domain unit. The network device can configure the discontinuity of at least one frequency domain unit for the first LTE carrier and the first NR carrier, thereby meeting the discontinuous capability supported by the terminal device, and then the terminal device can access the network normally.

Optionally, in a possible implementation manner of the third aspect, the above steps further include: sending third indication information, where the third indication information is used to indicate a frequency domain unit.

In this possible implementation, it can be understood as directly indicating at least one frequency domain unit. The network device can configure the discontinuity of at least one frequency domain unit for the first LTE carrier and the first NR carrier, thereby meeting the discontinuous capability supported by the terminal device, and then the terminal device can access the network normally.

In a fourth aspect of the present application, a communication method is provided, which is executed by a network device, or the method is executed by some components in the network device (such as a processor, a chip or a chip system, etc.), or the method can also be implemented by a logic module or software that can realize all or part of the network device functions. In the fourth aspect and its possible implementation, the method is described as an example of being executed by a network device. In this method, the network device receives a first indication information sent by a terminal device. The first indication information is used to indicate that the terminal device supports the first long-term evolution LTE carrier and the first new air interface NR carrier to be discontinuous, and the first LTE carrier and the first NR carrier are two carriers in the intra-band EN-DC; the network device receives the second indication information sent by the terminal device, and the second indication information is used to indicate the second protection band supported by the terminal device, the second protection band is smaller than the first protection band, and the first protection band is a predefined protection band corresponding to any channel bandwidth and subcarrier spacing. The network device sends configuration information to the terminal device, and the configuration information is used to configure the first LTE carrier and the first NR carrier. The configuration information and the second protection band are used for the terminal device to access the network.

Based on the above solution, the network device receives the second indication information to clarify that the second protection band supported by the terminal device is smaller than the first protection band defined in the existing standard, and can meet the radio frequency indicators.

Optionally, in a possible implementation manner of the fourth aspect, the above steps further include: receiving third indication information, where the third indication information is used to indicate a frequency domain unit.

In this possible implementation method, it can be understood that by receiving the frequency domain unit directly indicated by the third indication information, the network device can configure the discontinuity of at least one frequency domain unit for the first LTE carrier and the first NR carrier, thereby meeting the discontinuous capability supported by the terminal device, and then the terminal device can access the network normally.

Optionally, in a possible implementation of the third aspect or the fourth aspect, the difference between the first guard band and the second guard band is at least one frequency domain unit, and the frequency domain unit includes any one of the following: resource block, grid, subcarrier spacing.

In this possible implementation, it can be understood as indirectly indicating at least one frequency domain unit. The network device can configure the discontinuity of at least one frequency domain unit for the first LTE carrier and the first NR carrier, thereby meeting the discontinuous capability supported by the terminal device, and then the terminal device can access the network normally.

Optionally, in a possible implementation of the third aspect or the fourth aspect, the frequency domain position of the first NR carrier is configured to be separated from the frequency domain position of the first LTE carrier by at least one frequency domain unit. For example, the frequency domain position of the first NR carrier is configured to be offset by at least one frequency domain unit toward one side away from the frequency domain position of the first LTE carrier. For another example, the frequency domain position of the first LTE carrier is configured to be offset by at least one frequency domain unit toward one side away from the frequency domain position of the first NR carrier.

In this possible implementation, when the network device configures a carrier for the terminal device, the first LTE carrier and the first NR carrier are separated by at least one frequency domain unit (or it can be understood that the frequency domain positions of the first LTE carrier and the first NR carrier are configured to be discontinuous). This allows the network side to configure the terminal device in a manner that complies with the terminal device's support for discontinuous LTE and NR carriers in the intra-band EN-DC combination. For example, when the network device configures the first NR carrier, it moves at least one frequency domain unit away from the first LTE carrier. For another example, when the network device configures the first LTE carrier, it moves at least one frequency domain unit away from the first NR carrier, and so on.

Optionally, in a possible implementation of the third aspect or the fourth aspect, the resource blocks that exceed the legal spectrum boundary of the operator due to at least one frequency domain unit are not configured or scheduled for transmission, or the resource blocks adjacent to the legal spectrum boundary of the operator are not configured or scheduled for transmission.

In this possible implementation, the interference to the spectrum outside the boundary that may not comply with the protocol or regulations due to the configuration of at least one frequency domain unit of the first LTE carrier and the first NR carrier can be reduced.

Optionally, in a possible implementation of the third aspect or the fourth aspect, the above-mentioned first indication information is also used to indicate the frequency band identifier, the bandwidth level of the first LTE carrier, and the bandwidth level of the first NR carrier in the in-band EN-DC scenario.

In this possible implementation, the first indication information may also specifically indicate the frequency band identifier, bandwidth level, etc., so as to facilitate the network device to configure the first LTE carrier and the first NR carrier for the terminal device that are more suitable for the terminal device.

Optionally, in a possible implementation of the third aspect or the fourth aspect, the above-mentioned configuration information specifically includes at least one of the following: the frequency domain position or the number of resource blocks of the first LTE carrier and the first NR carrier.

In this possible implementation, by configuring the frequency domain position or the number of resource blocks of the carrier, etc., the terminal device can clearly understand the configuration of the carrier, thereby improving the efficiency of the terminal device accessing the network.

Optionally, in a possible implementation of the third aspect or the fourth aspect, the first LTE carrier and the first NR carrier include a downlink carrier and/or an uplink carrier.

This possible implementation can be applied not only to the configuration or communication of uplink carriers, but also to the configuration or communication of downlink carriers, thereby increasing the breadth of application scenarios.

In a fifth aspect, the present application provides a communication device, which is a terminal device, or a component of a terminal device (such as a processor, chip, or chip system), or a logic module or software that can implement all or part of the terminal device functions. The communication device includes a transceiver unit and a processing unit.

A transceiver unit is configured to send first indication information, where the first indication information is used to indicate that the terminal device supports discontinuity between a first long term evolution LTE carrier and a first new radio interface NR carrier, where the first LTE carrier and the first NR carrier are two carriers in an intra-band EN-DC;

The transceiver unit is further configured to receive configuration information, where the configuration information is used to configure the first LTE carrier and the first NR carrier;

A processing unit is configured to access a network according to a first rule and configuration information, wherein the first rule includes: a nominal channel spacing is equal to a channel spacing between an LTE carrier and an NR carrier in an intra-band discontinuous EN-DC, and a nominal channel spacing is a channel spacing between adjacent LTE carriers and NR carriers in an intra-band continuous EN-DC.

A sixth aspect of the present application provides a communication device, which is a network device, or a component of a network device (such as a processor, chip, or chip system), or a logic module or software that can implement all or part of the network device functions. The communication device includes a transceiver unit.

A transceiver unit is configured to receive first indication information, where the first indication information is used to indicate that the terminal device supports discontinuity between a first long term evolution LTE carrier and a first new radio interface NR carrier, where the first LTE carrier and the first NR carrier are two carriers in an intra-band EN-DC;

The transceiver unit is further used to send configuration information according to a first rule, where the configuration information is used to configure the first LTE carrier and the first NR carrier; the first rule includes: the nominal channel spacing is equal to the channel spacing between the LTE carrier and the NR carrier in the intra-band discontinuous EN-DC, and the nominal channel spacing is the channel spacing between adjacent LTE carriers and NR carriers in the intra-band continuous EN-DC.

Optionally, in a possible implementation of the fifth aspect or the sixth aspect, the above-mentioned first indication information is also used to indicate that the terminal device supports the continuity of the first LTE carrier and the first NR carrier.

Optionally, in a possible implementation of the fifth aspect or the sixth aspect, the above-mentioned first indication information is also used to indicate the frequency band identifier, the bandwidth level of the first LTE carrier, and the bandwidth level of the first NR carrier in the in-band EN-DC scenario.

Optionally, in a possible implementation of the fifth aspect or the sixth aspect, the above-mentioned configuration information specifically includes: the frequency domain position and the number of resource blocks of the first LTE carrier and the first NR carrier.

Optionally, in a possible implementation of the fifth aspect or the sixth aspect, the first LTE carrier and the first NR carrier include a downlink carrier and/or an uplink carrier.

In a seventh aspect, the present application provides a communication device, which is a terminal device, or a component of a terminal device (such as a processor, chip, or chip system), or a logic module or software that can implement all or part of the terminal device functions. The communication device includes a transceiver unit and a processing unit.

A transceiver unit is configured to send first indication information, where the first indication information is used to indicate that the terminal device supports discontinuity between a first long term evolution LTE carrier and a first new radio interface NR carrier, where the first LTE carrier and the first NR carrier are two carriers in an intra-band EN-DC;

The transceiver unit is further configured to receive configuration information, where the configuration information is used to configure the first LTE carrier and the first NR carrier;

A processing unit is used to access the network based on configuration information and a second protection band, where the second protection band is a protection band supported by the terminal device, the second protection band is smaller than the first protection band, and the first protection band is a predefined protection band corresponding to any channel bandwidth and subcarrier spacing.

Optionally, in a possible implementation of the seventh aspect, the above-mentioned transceiver unit is further used to send second indication information, and the second indication information is used to indicate a second protection band supported by the terminal device.

Optionally, in a possible implementation manner of the seventh aspect, the above-mentioned transceiver unit is further used to send third indication information, and the third indication information is used to indicate the frequency domain unit.

In an eighth aspect, the present application provides a communication device, which is a network device, or a component of a network device (such as a processor, chip, or chip system), or a logic module or software that can implement all or part of the network device functions. The communication device includes a transceiver unit.

A transceiver unit is configured to receive first indication information, where the first indication information is used to indicate that the terminal device supports discontinuity between a first long term evolution LTE carrier and a first new radio interface NR carrier, where the first LTE carrier and the first NR carrier are two carriers in an intra-band EN-DC;

The transceiver unit is further configured to receive second indication information, where the second indication information is used to indicate a second guard band supported by the terminal device, where the second guard band is smaller than the first guard band, and the first guard band is a predefined guard band corresponding to any channel bandwidth and subcarrier spacing;

The transceiver unit is also used to send configuration information, the configuration information is used to configure the first LTE carrier and the first NR carrier, and the configuration information and the second protection band are used for the terminal device to access the network.

Optionally, in a possible implementation manner of the eighth aspect, the above-mentioned transceiver unit is further used to receive third indication information, and the third indication information is used to indicate the frequency domain unit.

Optionally, in a possible implementation of the seventh aspect or the eighth aspect, the difference between the first guard band and the second guard band is at least one frequency domain unit, and the frequency domain unit includes any one of the following: resource block, grid, subcarrier spacing.

Optionally, in a possible implementation manner of the seventh aspect or the eighth aspect, the frequency domain position of the first NR carrier is configured to be separated from the frequency domain position of the first LTE carrier by at least one frequency domain unit. For example, the frequency domain position of the first NR carrier is configured to be offset by at least one frequency domain unit toward one side away from the frequency domain position of the first LTE carrier. For another example, the frequency domain position of the first LTE carrier is configured to be offset by at least one frequency domain unit toward one side away from the frequency domain position of the first NR carrier.

Optionally, in a possible implementation of the seventh aspect or the eighth aspect, the resource blocks that exceed the legal spectrum boundary of the operator due to at least one frequency domain unit are not configured or scheduled for transmission, or the resource blocks adjacent to the legal spectrum boundary of the operator are not configured or scheduled for transmission.

Optionally, in a possible implementation of the seventh aspect or the eighth aspect, the above-mentioned first indication information is also used to indicate the frequency band identifier, the bandwidth level of the first LTE carrier, and the bandwidth level of the first NR carrier in the in-band EN-DC scenario.

Optionally, in a possible implementation of the seventh aspect or the eighth aspect, the above-mentioned configuration information specifically includes: the frequency domain position and the number of resource blocks of the first LTE carrier and the first NR carrier.

Optionally, in a possible implementation of the seventh aspect or the eighth aspect, the above-mentioned first LTE carrier and the first NR carrier include a downlink carrier and/or an uplink carrier.

In the ninth aspect of the present application, a communication device is provided, comprising at least one processor coupled to at least one memory; the at least one memory is used to store programs or instructions; the at least one processor is used to execute the programs or instructions so that the device implements a method of any possible implementation method in the aforementioned first aspect, or implements a method of any possible implementation method in the aforementioned third aspect.

In the tenth aspect of the present application, a communication device is provided, comprising at least one processor, wherein the at least one processor is coupled to at least one memory; the at least one memory is used to store programs or instructions; the at least one processor is used to execute the programs or instructions so that the device implements a method of any possible implementation method in the aforementioned second aspect, or implements a method of any possible implementation method in the aforementioned fourth aspect.

In the eleventh aspect of the present application, a communication device is provided, comprising at least one logic circuit and at least one input/output interface; the logic circuit is used to execute the method described in any possible implementation of the first aspect, or the method described in any possible implementation of the third aspect.

The twelfth aspect of the present application provides a communication device, comprising at least one logic circuit and at least one input and output interface; the logic circuit is used to execute a method as described in any possible implementation of the second aspect, or a method as described in any possible implementation of the fourth aspect.

The thirteenth aspect of the present application provides a communication system, which includes a communication device of any possible implementation method of the fifth aspect and a communication device of any possible implementation method of the sixth aspect, or includes a communication device of any possible implementation method of the seventh aspect and a communication device of any possible implementation method of the eighth aspect, or includes a communication device of any possible implementation method of the ninth aspect and a communication device of any possible implementation method of the tenth aspect, or includes a communication device of any possible implementation method of the eleventh aspect and a communication device of any possible implementation method of the twelfth aspect.

In the fourteenth aspect of the present application, a computer-readable storage medium is provided, which is used to store one or more computer-executable instructions. When the computer-executable instructions are executed by a processor, the processor executes the method described in any possible implementation of any aspect of the first to fourth aspects above.

The fifteenth aspect of the present application provides a computer program product (or computer program). When the computer program in the computer program product is executed by the processor, the processor executes the method described in any possible implementation of any one of the first to fourth aspects above.

In the sixteenth aspect, the present application provides a chip or a chip system, which includes at least one processor for supporting a communication device to implement the method described in any possible implementation method of any aspect of the first to fourth aspects.

In one possible design, the chip system may also include at least one memory for storing program instructions and data necessary for the communication device. The chip system may be composed of a chip or may include a chip and other discrete components. Optionally, the chip system also includes an interface circuit that provides program instructions and/or data to at least one processor.

Among them, the technical effects brought about by any design method in the fifth to sixteenth aspects can refer to the technical effects brought about by the different design methods in the above-mentioned first to fourth aspects, and will not be repeated here.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG1A is a schematic diagram of a communication system involved in this application;

FIG1B is another schematic diagram of the communication system involved in this application;

FIG1C is another schematic diagram of the communication system involved in this application;

FIG2 is another schematic diagram of the communication system involved in this application;

FIG3 is a flow chart of the communication method involved in this application;

FIG4 is another schematic diagram of a flow chart of the communication method involved in this application;

FIG5 is an example diagram of channel spacing involved in this application;

FIG6 is an example diagram of redundant frequency domain units involved in this application;

7 to 10 are several schematic diagrams of the communication device involved in this application.

DETAILED DESCRIPTION

The technical solutions in the embodiments of the present application will be described clearly and completely below in conjunction with the drawings in the embodiments of the present application.

First, some of the terms used in the embodiments of the present application are explained to facilitate understanding by those skilled in the art.

1. Configuration and pre-configuration

In this application, configuration and pre-configuration are used simultaneously. Configuration refers to the network device/server sending some parameter configuration information or parameter values to the terminal through messages or signaling, so that the terminal can determine the communication parameters or resources during transmission based on these values or information. Pre-configuration is similar to configuration and can be parameter information or parameter values pre-negotiated between the network device/server and the terminal device, parameter information or parameter values used by the base station/network device or terminal device as specified in the standard protocol, or parameter information or parameter values pre-stored in the base station/server or terminal device. This application does not limit this.

Furthermore, these values and parameters can be changed or updated.

2. In this application, "used for indication" can include direct indication and indirect indication. When describing that a certain indication information is used to indicate A, it can be understood that the indication information carries A, directly indicates A, or indirectly indicates A.

In this application, the information indicated by the indication information is referred to as the information to be indicated. In the specific implementation process, there are many ways to indicate the information to be indicated. For example, it can be implemented by direct indication, such as by indicating the information to be indicated itself or the index of the information to be indicated. It can also be implemented by indirectly indicating other information, wherein there is an association between the other information and the information to be indicated. It is also possible to indicate only a part of the information to be indicated, while the other parts of the information to be indicated are known or agreed in advance. For example, the indication of specific information can also be achieved with the help of the arrangement order of each information agreed in advance (for example, stipulated in the protocol), thereby reducing the indication overhead to a certain extent.

The information to be indicated can be sent as a whole, or divided into multiple sub-information and sent separately, and the sending period and/or sending time of these sub-information can be the same or different. The specific sending method is not limited in this application. Among them, the sending period and/or sending time of these sub-information can be predefined, for example, predefined according to the protocol, or configured by the transmitting device by sending configuration information to the receiving device. Among them, the configuration information can, for example, but not limited to, include one or a combination of at least two of RRC signaling, medium access control (MAC) layer signaling and physical layer signaling. Among them, MAC layer signaling, for example, includes MAC CE; physical layer signaling, for example, includes downlink control information (DCI).

3. In the embodiments of this application, "sending" and "receiving" refer to the direction of signal transmission. In this application, when entity A sends information to entity B, A can send it directly to B or indirectly to B through another entity. Similarly, when entity B receives information from entity A, entity B can receive the information sent by entity A directly or indirectly through another entity. Entities A and B herein can be RAN nodes or terminals, or modules within RAN nodes or terminals. Information transmission and reception can be the exchange of information between a RAN node and a terminal, for example, between a base station and a terminal; between two RAN nodes, for example, between a CU and a DU; or between different modules within a device, for example, between a terminal chip and other modules in the terminal, or between a base station chip and other modules within the base station. "Sending" can also be understood as the "output" of a chip interface, for example, a baseband chip outputting information to a radio frequency chip; for example, "sending" can also be understood as the output of information from the baseband component within a device to the radio frequency component.

4. The terms "system" and "network" in the embodiments of the present application can be used interchangeably. "At least one" means one or more, and "plurality" means 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 mean: A exists alone, A and B exist at the same time, and B exists alone, where A and B can be singular or plural. The character "/" generally indicates that the previous and next associated objects are in an "or" relationship. "At least one of the following" or similar expressions refers to any combination of these items, including any combination of single or plural items. For example, "at least one of A, B and C" includes A, B, C, AB, AC, BC or ABC. And, unless otherwise specified, the ordinal numbers such as "first" and "second" mentioned in the embodiments of the present application are used to distinguish multiple objects, and are not used to limit the order, timing, priority or importance of multiple objects.

Please refer to Figure 1A, which is a schematic diagram of the architecture of a communication system 1000 used in an embodiment of the present application. As shown in Figure 1A, the communication system includes a radio access network (RAN) 100 and a core network 200. Optionally, the communication system 1000 may also include the Internet 300. The RAN 100 includes at least one RAN node (e.g., 110a and 110b in Figure 1A, collectively referred to as 110) and may also include at least one terminal (e.g., 120a-120j in Figure 1A, collectively referred to as 120). The RAN 100 may also include other RAN nodes, such as wireless relay devices and/or wireless backhaul devices (not shown in Figure 1A). The terminal 120 is wirelessly connected to the RAN node 110, and the RAN node 110 is wirelessly or wiredly connected to the core network 200. The core network devices in the core network 200 and the RAN node 110 in the RAN 100 may be independent and different physical devices, or they may be the same physical device that integrates the logical functions of the core network devices and the logical functions of the RAN nodes. Terminals and RAN nodes may be connected to each other via wired or wireless means.

RAN 100 may be an evolved universal terrestrial radio access (E-UTRA) system, a NR system, or a future radio access system defined in 3GPP. RAN 100 may also include two or more of the aforementioned different radio access systems. RAN 100 may also be an open RAN (O-RAN).

A RAN node, also known as radio access network equipment, a RAN entity, or an access node, facilitates wireless access to a communication system by terminals. In one application scenario, a RAN node can be a base station (BS), an evolved NodeB (eNodeB), a transmission reception point (TRP), a next-generation NodeB (gNB) in a fifth-generation (5G) mobile communication system, a next-generation NodeB in a sixth-generation (6G) mobile communication system, or a base station in a future mobile communication system. A RAN node can be a macro BS (such as 110a in Figure 1A), a micro BS, an indoor BS (such as 110b in Figure 1A), a relay node, or a donor node.

In another application scenario, multiple RAN nodes can collaborate to help terminals achieve wireless access, with different RAN nodes implementing portions of the base station's functions. For example, a RAN node can be a centralized unit (CU), a distributed unit (DU), or a radio unit (RU). The CU implements the base station's radio resource control protocol and packet data convergence protocol (PDCP) functions, as well as the service data adaptation protocol (SDAP) functions. The DU implements the base station's radio link control layer and medium access control (MAC) layer functions, as well as some or all of the physical layer functions. For detailed descriptions of each of these protocol layers, please refer to the relevant 3GPP technical specifications. The RU is responsible for transmitting and receiving RF signals. The CU and DU can be two independent RAN nodes, or they can be integrated into the same RAN node, such as in the baseband unit (BBU). The RU can be included in radio equipment, such as a remote radio unit (RRU) or an active antenna unit (AAU). The CU can be further divided into two types of RAN nodes: the CU-control plane and the CU-user plane.

In different systems, RAN nodes may have different names. For example, in an O-RAN system, the CU may be called an open CU (O-CU), the DU may be called an open DU (O-DU), and the RU may be called an open RU (O-RU). The RAN nodes in the embodiments of the present application may be implemented using software modules, hardware modules, or a combination of software and hardware modules. For example, the RAN node may be a server loaded with the corresponding software module. The embodiments of the present application do not limit the specific technology and device form used by the RAN node.

A RAN node can also be referred to as a network device. A network device is a device deployed in a radio access network that provides wireless communication capabilities for terminal devices. Network devices can include various forms of macro base stations, micro base stations (also known as small cells), relay stations, access points, and so on. In systems using different radio access technologies, the names of network devices may vary, such as eNB or eNodeB (Evolutionary NodeB) in Long Term Evolution (LTE). A network device can also be a wireless controller in a Cloud Radio Access Network (CRAN) scenario. A network device can also be a base station in a future 5G network or a network device in a future evolved PLMN network. A network device can also be a wearable device or an in-vehicle device. A network device can also be a Transmission and Reception Point (TRP). Furthermore, in one network architecture, a network device can include a centralized unit (CU) node, a distributed unit (DU) node, or a RAN device that includes both CU and DU nodes. For ease of description, the following description uses a base station as an example of a RAN node.

A terminal is a device with wireless transceiver capabilities that can send signals to or receive signals from a base station. A terminal may also be referred to as a terminal device, user equipment (UE), mobile station, mobile terminal, etc. Terminals 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. A terminal can be a mobile phone, tablet computer, computer with wireless transceiver capabilities, wearable device, vehicle, aircraft, ship, robot, robotic arm, smart home appliance, etc. The embodiments of this application do not limit the specific technology and specific device form used by the terminal.

Base stations and terminals can be fixed or mobile. They can be deployed on land, indoors or outdoors, handheld or vehicle-mounted; on water; or on aircraft, balloons, and satellites. The embodiments of this application do not limit the application scenarios of base stations and terminals.

The roles of base stations and terminals can be relative. For example, the helicopter or drone 120i in Figure 1A can be configured as a mobile base station. To terminals 120j accessing the wireless access network 100 via 120i, terminal 120i is a base station. However, to base station 110a, 120i is a terminal, meaning that communication between 110a and 120i occurs via a wireless air interface protocol. Of course, communication between 110a and 120i can also occur via a base station-to-base station interface protocol. In this case, 120i is also a base station relative to 110a. Therefore, base stations and terminals can be collectively referred to as communication devices. 110a and 110b in Figure 1A can be referred to as communication devices with base station functionality, while 120a-120j in Figure 1A can be referred to as communication devices with terminal functionality.

Communication between base stations and terminals, between base stations, and between terminals can be carried out through authorized spectrum, unauthorized spectrum, or both; communication can be carried out through spectrum below 6 gigahertz (GHz), spectrum above 6 GHz, or spectrum below 6 GHz and spectrum above 6 GHz. The embodiments of the present application do not limit the spectrum resources used for wireless communication.

In the embodiments of the present application, the functions of the base station may also be performed by a module (such as a chip) in the base station, or by a control subsystem that includes the base station functions. The control subsystem that includes the base station functions here may be a control center in the above-mentioned application scenarios such as smart grid, industrial control, smart transportation, and smart city. The functions of the terminal may also be performed by a module (such as a chip or modem) in the terminal, or by a device that includes the terminal functions.

It can be understood that the RAN 100 described above includes at least one RAN node (such as 110 a and 110 b in FIG. 1A , collectively referred to as 110 ), and may also include at least one terminal (such as 120 a - 120 j in FIG. 1A , collectively referred to as 120 ).

In one possible implementation, the communication system shown in FIG1A may also be as shown in FIG1B , that is, including a RAN node 110 and multiple terminals (such as 120A and 120B in FIG1B ). In this case, a single RAN node can transmit data or control signaling to a single terminal or multiple terminals.

In another possible implementation, the communication system shown in FIG1A may also be shown in FIG1C , that is, include multiple RAN nodes (such as 110A, 110B, and 110C in FIG1C ) 110 and a terminal 120. In this case, multiple RAN nodes may also simultaneously transmit data or control signaling for a single terminal.

Evolved Universal Terrestrial Radio Access with New Radio Dual Connectivity (E-UTRA-NR dual connectivity, EN-DC) is a special scenario in the communication system shown in Figure 1C above. EN-DC refers to a scenario in which a terminal device simultaneously accesses both an LTE network device and a NR network device. Typically, a terminal device uses an LTE network device as the primary network device and an NR network device as the secondary network device for dual connectivity. An example of an EN-DC communication system is shown in Figure 2, which includes a terminal device 201, an LTE network device 202, an NR network device 203, and a core network device 204.

Terminal device 201 is connected to LTE network device 202 and NR network device 203, respectively. LTE network device 202 and NR network device 203 are each connected to core network device 204. LTE network device 202 and NR network device 203 both provide air interface transmission resources for data transmission between terminal device 201 and core network device 204. This constitutes the dual-link deployment scenario shown in Figure 2. In this case, LTE network device 202 can be, for example, the LTE eNB described previously, NR network device 203 can be, for example, the gNB described previously, and core network device 204 can be, for example, a 4G core network device or a 5G core network device.

Optionally, a control plane connection and a data plane connection exist between the LTE network device 202 and the core network device 204, and a data plane connection exists between the NR network device 203 and the core network device 204. For example, an X2 interface exists between the LTE network device 202 and the NR network device 203, providing at least a control plane connection and possibly a user plane connection. An S1 interface exists between the LTE network device 202 and the core network device 204, providing at least a control plane connection and possibly a user plane connection. An S1-U interface exists between the NR network device 203 and the core network device 204, indicating that a user plane connection may exist.

In addition, EN-DC includes intra-band EN-DC and inter-band EN-DC according to the different frequency bands. Intra-band EN-DC means that the working carrier used for data transmission between the terminal device and the LTE network device and the working carrier for data transmission between the terminal device and the NR network device are in the same frequency band (that is, the LTE carrier and the NR carrier correspond to the same frequency band number). For example, the LTE carrier is on band 48, and the NR carrier is on band n48. Inter-band EN-DC means that the working carrier used for data transmission between the terminal device and the LTE network device and the working carrier for data transmission between the terminal device and the NR network device are in different frequency bands (that is, the LTE carrier and the NR carrier correspond to different frequency band numbers). For example, the LTE carrier is on band 48, and the NR carrier is on band n41.

Furthermore, intra-band EN-DC can be further divided into intra-band non-contiguous EN-DC and intra-band contiguous EN-DC, depending on the continuity of the carriers. Intra-band non-contiguous EN-DC can also be referred to as intra-band discontinuous EN-DC, discontinuous intra-band EN-DC, or discontinuous intra-band EN-DC. Intra-band contiguous EN-DC can also be referred to as continuous intra-band EN-DC.

In the existing mechanism, terminal devices can report capability information to the network. This capability information is used to indicate the contiguousness between adjacent LTE carriers and NR carriers in an intra-band EN-DC combination. For example, if the capability information reported by the terminal device indicates non-contiguous, then non-contiguous is supported. For another example, if the capability information reported by the terminal device indicates both non-contiguous and contiguous (or both), then both contiguous and discontinuous are supported. For another example, if the terminal device does not report this capability information, then only contiguous is supported by default.

However, some special networks (such as those in South Africa) may only support contiguous intra-band transmission of two carriers. If a terminal device reports that it only supports discontinuous transmission, the terminal device will not be able to access the network, thus affecting the normal use of the terminal device.

Specifically, the terminal device reports that it only supports discontinuous coverage, while the special network only supports continuous coverage. Therefore, the network sends the terminal device a configuration for continuous carriers. The terminal device checks the channel spacing between the LTE and NR carriers according to existing rules. If the spacing is equal to the nominal spacing, it determines that it is in-band continuous EN-DC. The network-configured carrier continuity conflicts with the terminal device's supported discontinuous capability, preventing the terminal device from accessing the network.

To solve the above technical problems, the present invention provides two approaches:

The first approach is to use the first rule to allow a terminal device that only supports discontinuous intra-band EN-DC combinations to operate in a network that only supports contiguous intra-band two-carrier combinations. This first rule requires that the nominal channel spacing be equal to the channel spacing between the LTE and NR carriers in discontinuous intra-band EN-DC. This treats the contiguous case as a special case of the discontinuous case. This also meets current practical requirements, namely that the discontinuous capability of a terminal device should support both contiguous and discontinuous networks.

The second approach is: when the network configures carriers for the terminal device, the LTE carrier and the NR carrier are separated by at least one frequency domain unit (or, in other words, the frequency domain positions of the first LTE carrier and the first NR carrier are configured to be discontinuous). This allows the network to configure the terminal device in a manner that satisfies the terminal device's support for the discontinuous LTE and NR carriers in the intra-band EN-DC combination. For example, when the network configures the NR carrier, it moves at least one frequency domain unit away from the LTE carrier. For another example, when the network configures the LTE carrier, it moves at least one frequency domain unit away from the NR carrier, and so on.

The first idea is first introduced below. Please refer to Figure 3, which is a flow chart of a communication method provided in an embodiment of the present application. The method may include steps 301 to 303. Steps 301 to 303 may be performed by a communication device, or may be performed by some components in the communication device (such as a processor, a chip or a chip system, etc.), or may be implemented by a logic module or software that can realize all or part of the functions of the communication device. The following description is taken as an example of execution by a communication device. The processing performed by a single execution subject in steps 301 to 303 may also be divided into executions by multiple execution subjects, and these execution subjects may be logically and/or physically separated. For example, in the case where the communication device is a network device, such as a base station, the processing performed by the communication device may be divided into executions by at least one of a CU, a DU and a RU. Steps 301 to 303 are described in detail below. The communication device may include the terminal device and/or network device in Figures 1A to 2 above. The embodiments of the present application are only described by taking the network device as the main network device of the terminal device (for example, the LTE network device in the aforementioned Figure 2) as an example. It can be understood that in actual applications, the network device can also be an auxiliary network device of the terminal device (for example, the NR network device in the aforementioned Figure 2) or a core network device (for example, the core network device in the aforementioned Figure 2), etc., which is not limited here.

Step 301: The terminal device sends first indication information to the network device.

The terminal device sends a first indication message to the network device. Accordingly, the network device receives the first indication message sent by the terminal device. The first indication message is used to indicate that the terminal device supports non-contiguous (non-contiguous) support of the first LTE carrier and the first NR carrier. The first LTE carrier and the first NR carrier are two carriers in the intra-band EN-DC. As can be seen from the previous description, the first LTE carrier and the first NR carrier of the intra-band EN-DC correspond to the same frequency band (or frequency band number).

It should be noted that the transmission between the network device and the terminal device in the embodiments of the present application (including the embodiment shown in Figure 3 and subsequent embodiments) can be the transmission between some components in the network device (such as a processor, chip, or chip system, etc.) and some components in the terminal device (such as a processor, chip, or chip system, etc.). Furthermore, "sending" can also be understood as the "output" of the chip interface, such as the baseband chip outputting information to the RF chip; for example, "sending" can also be understood as the baseband part inside the device outputting information to the RF part.

This step can also be understood as the process of the terminal device reporting capability information. For example, the first indication information can be carried in the Multi-RAT Dual Connectivity-Parameters (MRDC-Parameters) intraBand ENDC-Support and/or intraBand ENDC-Support-UL, but the specific details are not limited here.

Optionally, the first indication information can also be used to indicate that the terminal device supports the first LTE carrier and the first NR carrier to be contiguous. This situation can also be understood as that the first indication information indicates that the terminal device supports both contiguous and discontinuous (or understood as both).

Furthermore, the first indication information can also be used to indicate at least one of the following: the frequency band identifier (or frequency band number) in the in-band EN-DC scenario, the bandwidth level of the first LTE carrier, and the bandwidth level of the first NR carrier. Among them, the bandwidth level represents the number of consecutive carriers in the LTE or NR frequency band. In addition, the first LTE carrier includes an LTE uplink carrier and/or an LTE downlink carrier, and the first NR carrier includes an NR uplink carrier and/or an NR downlink carrier. Of course, in actual applications, the bandwidth level of the uplink frequency band may not be reported, for example, the LTE uplink carrier may not be reported. For another example, the NR uplink carrier may not be reported, and so on.

It is understandable that this step may be actively reported by the terminal device, or may be passively reported based on a query from the network device, and is not specifically limited here.

Step 302: The network device sends configuration information to the terminal device according to the first rule.

The network device sends configuration information to the terminal device according to the first rule. Correspondingly, the terminal device receives the configuration information sent by the network device. The configuration information is used to configure the first LTE carrier and the first NR carrier.

The first rule includes: the nominal channel spacing is equal to the channel spacing (also referred to as the center frequency) between the LTE and NR carriers in intra-band discontinuous EN-DC (or described as the channel spacing between the LTE and NR carriers in intra-band discontinuous EN-DC is equal to the nominal channel spacing), and the nominal channel spacing is the channel spacing between adjacent LTE and NR carriers in intra-band continuous EN-DC. Alternatively, the first rule includes: the channel spacing between the LTE and NR carriers in intra-band discontinuous EN-DC is greater than or equal to the nominal channel spacing (or described as the channel spacing between the LTE and NR carriers in intra-band discontinuous EN-DC is greater than or equal to the nominal channel spacing). This treats the continuous case as a special case of the discontinuous case.

In addition, the above nominal channel spacing has the following multiple cases:

1. For frequency bands using a 100 kHz channel grid:

Nominal channel spacing = (BW _{E-UTRA_Channel} + BW _{NR_Channel} )/2;

2. For frequency bands using a 15kHz channel grid:

Nominal channel spacing = (BW _{E-UTRA_Channel} + BW _{NR_Channel} )/2 + {-5 kHz, 0 kHz, 5 kHz} ΔF _Raster = 15 kHz;

Nominal channel spacing = (BW _{E-UTRA_Channel} + BW _{NR_Channel} )/2 + {-10 kHz, 0 kHz, 10 kHz} ΔF _Raster = 30 kHz;

Where BW _{E-UTRA_Channel} represents the bandwidth of the LTE channel, and BW _{NR_Channel} represents the bandwidth of the NR channel. For frequency bands below 3 GHz using a 15 kHz channel grid: ΔF _Raster = I × ΔF _Global , I∈{3,6}, ΔF _Global = 5 kHz; for frequency bands above 3 GHz using a 15 kHz channel grid: ΔF _Raster = I × ΔF _Global , I∈{1,2}, ΔF _Global = 15 kHz.

Optionally, the above-mentioned configuration information may specifically include at least one of the following: the frequency domain position of the first LTE carrier and the first NR carrier, the number of resource blocks of the first LTE carrier and the first NR carrier, etc.

Step 303: The terminal device accesses the network according to the first rule and configuration information.

After obtaining the configuration information, the terminal device can access the network according to the first rule and the configuration information.

Optionally, after the terminal device receives the configuration information, the terminal device checks the size of the channel spacing between its first LTE carrier and the first NR carrier and the nominal channel spacing. Since the first rule includes: the nominal channel spacing is equal to the channel spacing between the LTE carrier and the NR carrier in the intra-band discontinuous EN-DC, or the channel spacing between the LTE carrier and the NR carrier in the intra-band discontinuous EN-DC is greater than or equal to the nominal channel spacing. If the channel spacing between the first LTE carrier and the first NR carrier is equal to the nominal channel spacing, it is determined according to the first rule that the configuration information sent by the network device meets the discontinuous capability supported by the terminal device, thereby accessing the network.

The access network in the embodiments of the present application can be understood as a network through which a terminal device can wirelessly communicate. For example, accessing a network includes: a terminal device establishing a connection with a primary network device. Another example includes: a terminal device establishing a connection with a secondary network device, etc., and the specifics are not limited here.

In an embodiment of the present application, the first rule can enable a terminal device that only reports that the LTE carrier and NR carrier supporting in-band EN-DC are discontinuous to access a network in which the LTE and NR carriers supporting only in-band EN-DC are continuous. The first rule is that the nominal channel spacing is equal to the channel spacing between the LTE carrier and the NR carrier in the in-band discontinuous EN-DC. That is, the continuous case is regarded as a special case of the discontinuous case. This also meets the current actual needs, that is, the discontinuous capability of the terminal device should be to support both continuous and discontinuous networks.

The second idea is introduced below. Please refer to Figure 4, which is a flow chart of a communication method provided in an embodiment of the present application. The method may include steps 401 to 404. Steps 401 to 404 can be performed by a communication device, or by some components in the communication device (such as a processor, a chip or a chip system, etc.), or by a logic module or software that can realize all or part of the functions of the communication device. The following description is taken as an example of execution by a communication device. The processing performed by a single execution subject in steps 401 to 404 can also be divided into executions by multiple execution subjects, and these execution subjects can be logically and/or physically separated. For example, in the case where the communication device is a network device, such as a base station, the processing performed by the communication device can be divided into executions by at least one of a CU, a DU and a RU. Steps 401 to 404 are described in detail below. The communication device may include the terminal device and/or network device in Figures 1A to 2 above. The embodiments of the present application are only described by taking the network device as the main network device of the terminal device (for example, the LTE network device in the aforementioned Figure 2) as an example. It can be understood that in actual applications, the network device can also be an auxiliary network device of the terminal device (for example, the NR network device in the aforementioned Figure 2) or a core network device (for example, the core network device in the aforementioned Figure 2), etc., which is not limited here.

Step 401: The terminal device sends first indication information to the network device.

For step 401 in this embodiment, reference may be made to the description of step 301 in the embodiment shown in FIG3 , and details thereof will not be repeated here.

Step 402: The terminal device sends second indication information to the network device. This step is optional.

Optionally, the terminal device sends second indication information to the network device. Accordingly, the network device receives the second indication information sent by the terminal device. The second indication information is used to indicate a second guard band supported by the terminal device, where the second guard band is smaller than the first guard band, and the first guard band is a predefined guard band corresponding to any channel bandwidth and subcarrier spacing.

The guard bands (e.g., the first guard band and the second guard band) in the embodiments of the present application can be understood as guard bands. A guard band refers to a frequency range reserved in a communication system to prevent interference between signals of different frequencies. Alternatively, it can be understood as the interval between frequency bands. This interval is not used for transmission, but rather serves as a guard band to facilitate communication.

Exemplarily, the predefined first guard band is shown in Table 1:

Table 1

Among them, the predefined guard band (in kHz) corresponding to each UE channel bandwidth and subcarrier spacing, N/A means not applicable.

Exemplarily, the difference between the second guard band reported by the terminal device and the first guard band defined in the standard is 1 grid (eg, 100 kHz).

This step is a case of the second approach. To meet RF specifications, a special second guard band is defined. For example, the terminal device can report its ability to support a smaller guard band (i.e., the second guard band supported by the terminal device is smaller than the first guard band).

Furthermore, the difference between the first guard band and the second guard band is at least one frequency domain unit.

The frequency domain unit in the embodiments of the present application is used to describe a distance or position in the frequency domain. The frequency domain unit may also be referred to as a gap, interval, unit distance, unit granularity, etc. The frequency domain unit may include any of the following: resource block (RB), raster (grid), subcarrier spacing (SCS), etc.

Step 403: The terminal device sends third indication information to the network device. This step is optional.

Optionally, the terminal device sends third indication information to the network device. Accordingly, the network device receives the third indication information sent by the terminal device. The third indication information is used to indicate the frequency domain unit. The third indication information can also be understood as indicating to the network device that the interval granularity between the LTE carrier and the NR carrier needs to be set, or it can be understood that the network device can determine the unit distance of the carrier shift based on the third indication information reported by the terminal device.

For example, if the frequency domain unit reported by the terminal device is 1RB, the network device moves 1RB away from the LTE carrier when setting the NR carrier. Alternatively, the network device moves 1RB away from the NR carrier when setting the LTE carrier. For another example, if the frequency domain unit reported by the terminal device is 1 subcarrier, the network device can move 1 subcarrier away from the LTE carrier when setting the NR carrier. Alternatively, the network device moves 1 subcarrier away from the NR carrier when setting the LTE carrier.

Step 404: The network device sends configuration information to the terminal device.

The network device determines the configuration information and sends the configuration information to the terminal device. Correspondingly, the terminal device receives the configuration information sent by the network device. The configuration information is used to configure the first LTE carrier and the first NR carrier.

Alternatively, the network device configures the first LTE and the first NR carrier according to the second information and/or the third information, so that the first LTE and the first NR carrier are separated by at least one frequency domain unit in the frequency domain. The frequency domain unit is related to the second information and/or the third information.

Among them, the above-mentioned configuration information may specifically include at least one of the following: the frequency domain position of the first LTE carrier and the first NR carrier, the number of resource blocks of the first LTE carrier and the first NR carrier, etc. And the frequency domain position of the first NR carrier in the configuration information is configured to be separated from the frequency domain position of the first LTE carrier by at least one frequency domain unit, or the frequency domain position of the first LTE carrier in the configuration information is configured to be separated from the frequency domain position of the first NR carrier by at least one frequency domain unit. The frequency domain unit can refer to the previous description, and can specifically include any one of the following: resource block, grid, subcarrier spacing, etc.

This step can also be understood as the second approach to solving the existing technical problems, that is, when the network device configures a carrier for the terminal device, the first LTE carrier and the first NR carrier are separated by at least one frequency domain unit (or it can be understood that the frequency domain positions of the first LTE carrier and the first NR carrier are configured to be discontinuous). This allows the network device to configure the terminal device in accordance with the terminal device's support for discontinuous LTE and NR carriers in the intra-band EN-DC combination. For example, when the network device configures the first NR carrier, it moves at least one frequency domain unit away from the first LTE carrier. For another example, when the network device configures the first LTE carrier, it moves at least one frequency domain unit away from the first NR carrier, and so on.

For example, an example of the above-configured first LTE carrier and first NR carrier is shown in Figure 5. As can be seen, when the network device configures the first LTE carrier and the first NR carrier, it shifts at least one frequency domain unit to create a discontinuous situation. In this way, when the terminal device subsequently determines based on the rules that the configuration information issued by the network device meets the discontinuous capabilities supported by the terminal device, it will then access the network.

Exemplarily, continuing the example of the second indication information above, the difference between the second guard band reported by the terminal device and the first guard band defined in the standard is 1 grid (for example, 100kHz). The network device can move 1 grid away from the LTE carrier when configuring the NR carrier. That is, the guard band corresponding to the corresponding channel bandwidth is -100kHz.

Furthermore, the network device configuration process described above, as shown in Figure 6, may exceed the operator's legal spectrum due to the movement of at least one frequency domain unit. In other words, the redundant frequency domain units in Figure 6 may cause interference to spectrum outside the boundaries that does not comply with protocols or regulations.

In order to further solve the above technical problems, two solutions are provided under the second approach of the embodiment of the present application.

The first solution is to define a special second guard band to meet RF specifications. For example, a terminal device can report its ability to support a smaller guard band (i.e., the second guard band supported by the terminal device is smaller than the first guard band defined in the standard). This is a case of the second approach described in step 402. Of course, the network device can obtain the second guard band by reporting it to the terminal device, by sending measurement data, or by configuration or pre-configuration, etc., and the specifics are not limited here.

The second solution is for network equipment to not allocate or schedule resource blocks (RBs) that exceed the operator's legal spectrum boundaries. This can also be understood as not allocating or scheduling resource blocks (RBs) near the operator's legal spectrum boundaries. In other words, resource blocks outside the legal spectrum boundaries, resulting from the shifting of at least one frequency unit, are not allocated or scheduled for transmission.

For example, if step 402 and step 403 do not exist, that is, the network device can determine the configuration information based on the first indication information. Specifically, the network device can configure the frequency domain positions of the first LTE carrier and the first NR carrier to be discontinuous based on the first indication information reported by the terminal device.

For another example, if step 402 is present, step 403 is absent. That is, the network device can determine the configuration information based on the first indication information and the second indication information. Specifically, the network device can determine the second guard band supported by the terminal device based on the second indication information in step 402, and then, by comparing it with the first guard band, determine the frequency domain unit that needs to be shifted when setting the carrier. In this case, it can also be understood that the terminal device indirectly indicates to the network device, through the second indication information, the frequency domain unit that needs to be shifted when setting the carrier.

For another example, if steps 402 and 403 are present, the network device can determine the configuration information based on the first indication information, the second indication information, and the third indication information. Specifically, the network device can specify the frequency domain unit to be shifted when setting the carrier based on the third indication information in step 403. This scenario can also be understood as the terminal device directly instructing the network device, via the third indication information, on the frequency domain unit to be shifted when setting the carrier.

Step 405: The terminal device accesses the network according to the configuration information.

After the terminal device obtains the configuration information, it can access the network according to the configuration information.

Optionally, after the terminal device receives the configuration information, the terminal device checks the size of the channel spacing between its own first LTE carrier and the first NR carrier and the nominal channel spacing, because the rule includes: the channel spacing between the LTE carrier and the NR carrier in the intra-band discontinuous EN-DC is greater than the nominal channel spacing. If the channel spacing between the first LTE carrier and the first NR carrier is greater than the nominal channel spacing, it is determined according to the above rules that the configuration information sent by the network device meets the discontinuous capability supported by the terminal device, thereby accessing the network.

The method provided in this embodiment has various scenarios. For example, the method provided in this embodiment includes step 401, step 404, and step 405. For another example, the method provided in this embodiment includes step 401, step 402, step 404, and step 405. For another example, the method provided in this embodiment includes step 401, step 403, step 404, and step 405. For another example, the method provided in this embodiment includes steps 401 to 405.

In addition, step 403 may be dependent on step 402 (ie, if step 402 is included, step 403 may be further included). Step 403 may also be independent of step 402 (ie, if step 402 is not included, step 403 may also be included).

In an embodiment of the present application, on the one hand, when the network side configures a carrier for a terminal device, the LTE carrier and the NR carrier are separated by at least one frequency domain unit (or it can be understood that the frequency domain positions where the first LTE carrier and the first NR carrier are configured are discontinuous). As a result, the network side configures the terminal device in accordance with the terminal device's support for discontinuous LTE carriers and NR carriers in the intra-band EN-DC combination. For example, when the network side configures the NR carrier, it moves at least one frequency domain unit to the side away from the LTE carrier. For another example, when the network side configures the LTE carrier, it moves at least one frequency domain unit to the side away from the NR carrier, and so on. On the other hand, by not configuring or scheduling frequency domain units that exceed the operator's legal spectrum boundary, or defining that the terminal device can support a special protection band that is smaller than the standard protection band (that is, the second protection band is smaller than the first protection band defined in the standard), it is possible to reduce the interference that may be caused by the creation of discontinuous frequency domain units to the spectrum outside the boundary that does not meet the agreement or regulations.

The communication method in the embodiment of the present application is described above. The communication device in the embodiment of the present application is described below. Please refer to Figure 7, which is an embodiment of a communication device 700 in the embodiment of the present application. The communication device 700 can implement the functions of the terminal device or network device in the above method embodiment, and thus can also achieve the beneficial effects of the above method embodiment. In the embodiment of the present application, the communication device 700 can be a communication device, or it can be an integrated circuit or component inside the communication device, such as a chip. The communication device 700 includes: a transceiver unit 701 and a processing unit 702. Or the communication device 700 includes: a transceiver unit 701.

In one possible implementation, the communication device 700 is the terminal device in the embodiments shown in FIG. 1A to FIG. 3 . In this case, the functions of each unit are as follows:

The transceiver unit 701 is configured to send first indication information, where the first indication information is used to indicate that the terminal device supports discontinuity between a first long term evolution LTE carrier and a first new radio interface NR carrier, where the first LTE carrier and the first NR carrier are two carriers in an intra-band EN-DC;

The transceiver unit 701 is further configured to receive configuration information, where the configuration information is used to configure the first LTE carrier and the first NR carrier;

The processing unit 702 is used to access the network according to the first rule and configuration information, where the first rule includes: the nominal channel spacing is equal to the channel spacing between the LTE carrier and the NR carrier in the intra-band discontinuous EN-DC, and the nominal channel spacing is the channel spacing between adjacent LTE carriers and NR carriers in the intra-band continuous EN-DC.

Optionally, the first indication information is also used to indicate that the terminal device supports the continuity of the first LTE carrier and the first NR carrier.

Optionally, the first indication information is also used to indicate the frequency band identifier, the bandwidth level of the first LTE carrier, and the bandwidth level of the first NR carrier in the in-band EN-DC scenario.

Optionally, the configuration information specifically includes: the frequency domain position and number of resource blocks of the first LTE carrier and the first NR carrier.

Optionally, the first LTE carrier and the first NR carrier include a downlink carrier and/or an uplink carrier.

In this embodiment, the operations performed by each unit in the communication device are similar to the description of the terminal device in the embodiments shown in Figures 1A to 3 above, and will not be repeated here.

In this embodiment, the first rule can enable a terminal device that only reports that the LTE carrier supporting in-band EN-DC and the NR carrier are discontinuous to access a network in which the LTE and NR carriers that only support in-band EN-DC are continuous. The first rule is that the nominal channel spacing is equal to the channel spacing between the LTE carrier and the NR carrier in the in-band discontinuous EN-DC. That is, the continuous case is regarded as a special case of the discontinuous case. This also meets the current actual needs, that is, the discontinuous capability of the terminal device should support both continuous and discontinuous networks.

In another possible implementation, the communication device 700 is the network device in the embodiments shown in FIG. 1A to FIG. 3 . In this case, the functions of the various units are as follows:

The transceiver unit 701 is configured to receive first indication information, where the first indication information is used to indicate that the terminal device supports discontinuity between a first long term evolution LTE carrier and a first new radio interface NR carrier, where the first LTE carrier and the first NR carrier are two carriers in an intra-band EN-DC;

The transceiver unit 701 is also used to send configuration information according to the first rule, where the configuration information is used to configure the first LTE carrier and the first NR carrier; the first rule includes: the nominal channel spacing is equal to the channel spacing between the LTE carrier and the NR carrier in the intra-band discontinuous EN-DC, and the nominal channel spacing is the channel spacing between adjacent LTE carriers and NR carriers in the intra-band continuous EN-DC.

Optionally, the first indication information is also used to indicate that the terminal device supports the continuity of the first LTE carrier and the first NR carrier.

Optionally, the first indication information is also used to indicate the frequency band identifier, the bandwidth level of the first LTE carrier, and the bandwidth level of the first NR carrier in the in-band EN-DC scenario.

Optionally, the configuration information specifically includes: the frequency domain position and number of resource blocks of the first LTE carrier and the first NR carrier.

Optionally, the first LTE carrier and the first NR carrier include a downlink carrier and/or an uplink carrier.

In this embodiment, the operations performed by each unit in the communication device are similar to the description of the network device in the embodiments shown in Figures 1A to 3 above, and will not be repeated here.

In this embodiment, the first rule can enable a terminal device that only reports that the LTE carrier supporting in-band EN-DC and the NR carrier are discontinuous to access a network in which the LTE and NR carriers that only support in-band EN-DC are continuous. The first rule is that the nominal channel spacing is equal to the channel spacing between the LTE carrier and the NR carrier in the in-band discontinuous EN-DC. That is, the continuous case is regarded as a special case of the discontinuous case. This also meets the current actual needs, that is, the discontinuous capability of the terminal device should support both continuous and discontinuous networks.

In another possible implementation, the communication device 700 is the terminal device in the embodiments shown in FIG. 1A to FIG. 2 and FIG. 4 to FIG. 6 . In this case, the functions of each unit are as follows:

The transceiver unit 701 is configured to send first indication information, where the first indication information is used to indicate that the terminal device supports discontinuity between a first long term evolution LTE carrier and a first new radio interface NR carrier, where the first LTE carrier and the first NR carrier are two carriers in an intra-band EN-DC;

The transceiver unit 701 is further configured to receive configuration information, where the configuration information is used to configure the first LTE carrier and the first NR carrier;

Processing unit 702 is used to access the network based on configuration information and the second protection band, where the second protection band is a protection band supported by the terminal device, the second protection band is smaller than the first protection band, and the first protection band is a predefined protection band corresponding to any channel bandwidth and subcarrier spacing.

Optionally, the transceiver unit 701 is further used to send second indication information, where the second indication information is used to indicate a second protection band supported by the terminal device.

Optionally, the difference between the first guard band and the second guard band is at least one frequency domain unit, and the frequency domain unit includes any one of the following: resource block, grid, subcarrier spacing.

Optionally, the transceiver unit 701 is further used to send third indication information, where the third indication information is used to indicate a frequency domain unit.

Optionally, the frequency domain position of the first NR carrier is configured to be separated from the frequency domain position of the first LTE carrier by at least one frequency domain unit. For example, the frequency domain position of the first NR carrier is configured to be offset by at least one frequency domain unit toward a side away from the frequency domain position of the first LTE carrier. For another example, the frequency domain position of the first LTE carrier is configured to be offset by at least one frequency domain unit toward a side away from the frequency domain position of the first NR carrier.

Optionally, resource blocks outside the legal spectrum boundary of the operator due to at least one frequency domain unit are not configured or scheduled for transmission, or resource blocks adjacent to the legal spectrum boundary of the operator are not configured or scheduled for transmission.

Optionally, the first indication information is also used to indicate the frequency band identifier, the bandwidth level of the first LTE carrier, and the bandwidth level of the first NR carrier in the in-band EN-DC scenario.

Optionally, the configuration information specifically includes: the frequency domain position and number of resource blocks of the first LTE carrier and the first NR carrier.

Optionally, the first LTE carrier and the first NR carrier include a downlink carrier and/or an uplink carrier.

In this embodiment, the operations performed by each unit in the communication device are similar to the description of the terminal equipment in the embodiments shown in Figures 1A to 2 and Figures 4 to 6 above, and will not be repeated here.

In this embodiment, by limiting the second guard band supported by the terminal device to be smaller than the predefined first guard band, the radio frequency indicator can be met.

In another possible implementation, the communication device 700 is the network device in the embodiments shown in FIG. 1A to FIG. 2 and FIG. 4 to FIG. 6 . In this case, the functions of each unit are as follows:

The transceiver unit 701 is configured to receive first indication information, where the first indication information is used to indicate that the terminal device supports discontinuity between a first long term evolution LTE carrier and a first new radio interface NR carrier, where the first LTE carrier and the first NR carrier are two carriers in an intra-band EN-DC;

The transceiver unit 701 is further configured to receive second indication information, where the second indication information is used to indicate a second guard band supported by the terminal device, where the second guard band is smaller than the first guard band, and the first guard band is a predefined guard band corresponding to any channel bandwidth and subcarrier spacing;

The transceiver unit 701 is also used to send configuration information, where the configuration information is used to configure the first LTE carrier and the first NR carrier, and the configuration information and the second protection band are used for the terminal device to access the network.

Optionally, the difference between the first guard band and the second guard band is at least one frequency domain unit, and the frequency domain unit includes any one of the following: resource block, grid, subcarrier spacing.

Optionally, the transceiver unit 701 is further used to receive third indication information, where the third indication information is used to indicate a frequency domain unit.

Optionally, the frequency domain position of the first NR carrier is configured to be separated from the frequency domain position of the first LTE carrier by at least one frequency domain unit. For example, the frequency domain position of the first NR carrier is configured to be offset by at least one frequency domain unit toward a side away from the frequency domain position of the first LTE carrier. For another example, the frequency domain position of the first LTE carrier is configured to be offset by at least one frequency domain unit toward a side away from the frequency domain position of the first NR carrier.

Optionally, resource blocks outside the legal spectrum boundary of the operator due to at least one frequency domain unit are not configured or scheduled for transmission, or resource blocks adjacent to the legal spectrum boundary of the operator are not configured or scheduled for transmission.

Optionally, the first indication information is also used to indicate the frequency band identifier, the bandwidth level of the first LTE carrier, and the bandwidth level of the first NR carrier in the in-band EN-DC scenario.

Optionally, the configuration information specifically includes: the frequency domain position and number of resource blocks of the first LTE carrier and the first NR carrier.

Optionally, the first LTE carrier and the first NR carrier include a downlink carrier and/or an uplink carrier.

In this embodiment, the operations performed by each unit in the communication device are similar to the description of the network devices in the embodiments shown in Figures 1A to 2 and Figures 4 to 6 above, and will not be repeated here.

In this embodiment, the network device receives the second indication information to clarify that the second protection band supported by the terminal device is smaller than the predefined first protection band and can meet the radio frequency indicators.

Please refer to Fig. 8, which is another schematic structural diagram of a communication device 800 provided in this application. The communication device 800 includes a logic circuit 801 and an input/output interface 802. The communication device 800 may be a chip or an integrated circuit.

The transceiver unit 701 shown in FIG7 may be a communication interface, which may be the input/output interface 802 in FIG8 , which may include an input interface and an output interface. Alternatively, the communication interface may be a transceiver circuit, which may include an input interface circuit and an output interface circuit. The processing unit 702 shown in FIG7 may be the logic circuit 801 in FIG8 .

Optionally, when the communication device is the terminal device in the aforementioned embodiment, the input and output interface 802 is used to send instruction information and receive configuration information. The logic circuit 801 is used to access the network.

Optionally, when the communication device is the network device in the aforementioned embodiment, the input and output interface 802 is used to send configuration information and receive instruction information.

The logic circuit 801 and the input/output interface 802 may also execute other steps executed by the terminal device or the network device in any embodiment and achieve corresponding beneficial effects, which will not be described in detail here.

Optionally, the logic circuit 801 may be a processing device, and the functions of the processing device may be partially or entirely implemented by software. The functions of the processing device may be partially or entirely implemented by software.

Optionally, the processing device may include a memory and a processor, wherein the memory is used to store a computer program, and the processor reads and executes the computer program stored in the memory to perform corresponding processing and/or steps in any one of the method embodiments.

Alternatively, the processing device may include only a processor. A memory for storing the computer program is located outside the processing device, and the processor is connected to the memory via circuits/wires to read and execute the computer program stored in the memory. The memory and processor may be integrated or physically separate.

Optionally, the processing device may be one or more chips, or one or more integrated circuits. For example, the processing device may be one or more field-programmable gate arrays (FPGAs), application-specific integrated circuits (ASICs), system-on-chips (SoCs), central processing units (CPUs), network processors (NPs), digital signal processing circuits (DSPs), microcontrollers (MCUs), programmable logic devices (PLDs), or other integrated chips, or any combination of the above chips or processors.

Please refer to FIG. 9 , which shows a communication device 900 involved in the above embodiments provided in an embodiment of the present application. Specifically, the communication device 900 may be a communication device serving as a terminal device in the above embodiments.

Here, a possible logical structure diagram of the communication device 900 is shown. The communication device 900 may include but is not limited to at least one processor 901 and at least one communication port 902 .

The transceiver unit 701 shown in FIG7 may be a communication interface, which may be the communication port 902 in FIG9 , which may include an input interface and an output interface. Alternatively, the communication port 902 may be a transceiver circuit, which may include an input interface circuit and an output interface circuit.

It is understood that the communication port 902 in FIG. 9 can be used to transmit instruction information. For example, if the communication device 900 is a terminal device in the aforementioned embodiment, the communication port 902 is used to send instruction information and receive configuration information. For another example, if the communication device 900 is a network device in the aforementioned embodiment, the communication port 902 is used to receive instruction information and send configuration information.

Further optionally, the device may also include at least one of a memory 903 and a bus. In an embodiment of the present application, the at least one processor 901 is used to control and process the actions of the communication device 900.

In addition, the processor 901 can be a central processing unit, a general-purpose processor, a digital signal processor, an application-specific integrated circuit, a field programmable gate array or other programmable logic device, a transistor logic device, a hardware component, or any combination thereof. It can implement or execute the various exemplary logic blocks, modules, and circuits described in conjunction with the disclosure of this application. The processor can also be a combination that implements computing functions, such as a combination of one or more microprocessors, a combination of a digital signal processor and a microprocessor, and so on. Those skilled in the art will clearly understand that for the convenience and brevity of description, the specific working processes of the systems, devices, and units described above can refer to the corresponding processes in the aforementioned method embodiments and will not be repeated here.

It is understood that the present application does not limit the number of components shown in Figure 9. For example, the number of processors 901, the number of communication ports 902, and the number of memories 903 can be one or more, and are not specifically limited here.

It should be noted that the communication device 900 shown in Figure 9 can be specifically used to implement the steps implemented by the terminal device in the aforementioned method embodiment and achieve the corresponding technical effects of the terminal device. The specific implementation methods of the communication device shown in Figure 9 can refer to the description in the aforementioned method embodiment and will not be repeated here.

Please refer to Figure 10, which is a structural diagram of the communication device 1000 involved in the above-mentioned embodiments provided in an embodiment of the present application. The communication device 1000 can specifically be a communication device serving as a network device in the above-mentioned embodiments, wherein the structure of the communication device can refer to the structure shown in Figure 10.

The communication device 1000 includes at least one processor 1011 and at least one network interface 1014. Further optionally, the communication device also includes at least one memory 1012, at least one transceiver 1013 and one or more antennas 1015. The processor 1011, the memory 1012, the transceiver 1013 and the network interface 1014 are connected, for example, via a bus. In an embodiment of the present application, the connection may include various interfaces, transmission lines or buses, etc., which are not limited in this embodiment. The antenna 1015 is connected to the transceiver 1013. The network interface 1014 is used to enable the communication device to communicate with other communication devices through a communication link. For example, the network interface 1014 may include a network interface between the communication device and the core network device, such as an S1 interface, and the network interface may include a network interface between the communication device and other communication devices (such as other network devices or core network devices), such as an X2 or Xn interface.

The transceiver unit 701 shown in FIG7 may be a communication interface, which may be the network interface 1014 in FIG10 , which may include an input interface and an output interface. Alternatively, the network interface 1014 may be a transceiver circuit, which may include an input interface circuit and an output interface circuit.

Processor 1011 is primarily used to process communication protocols and communication data, control the entire communication device, execute software programs, and process software program data, for example, to support the communication device in performing the actions described in the embodiments. A communication device may include a baseband processor and a central processing unit. The baseband processor is primarily used to process communication protocols and communication data, while the central processing unit is primarily used to control the entire communication device, execute software programs, and process software program data. Processor 1011 in Figure 10 may integrate the functions of both a baseband processor and a central processing unit. Those skilled in the art will appreciate that the baseband processor and the central processing unit may also be independent processors interconnected via a bus or other technology. Those skilled in the art will appreciate that a communication device may include multiple baseband processors to accommodate different network standards, multiple central processing units to enhance processing capabilities, and various components of the communication device may be connected via various buses. The baseband processor may also be referred to as a baseband processing circuit or a baseband processing chip. The central processing unit may also be referred to as a central processing circuit or a central processing chip. The functionality for processing communication protocols and communication data may be built into the processor or stored in memory as a software program, which is executed by the processor to implement the baseband processing functionality.

The memory is primarily used to store software programs and data. Memory 1012 can exist independently and be connected to processor 1011. Alternatively, memory 1012 and processor 1011 can be integrated together, for example, within a single chip. Memory 1012 can store program code for executing the technical solutions of the embodiments of the present application, and execution is controlled by processor 1011. The various computer program codes executed can also be considered drivers for processor 1011.

Figure 10 shows only one memory and one processor. In an actual communication device, there may be multiple processors and multiple memories. The memory may also be referred to as a storage medium or storage device. The memory may be a storage element on the same chip as the processor, i.e., an on-chip storage element, or an independent storage element, which is not limited in the present embodiment.

The transceiver 1013 can be used to support the reception or transmission of radio frequency signals between the communication device and the terminal. The transceiver 1013 can be connected to the antenna 1015. The transceiver 1013 includes a transmitter Tx and a receiver Rx. Specifically, one or more antennas 1015 can receive radio frequency signals. The receiver Rx of the transceiver 1013 is used to receive the radio frequency signal from the antenna, convert the radio frequency signal into a digital baseband signal or a digital intermediate frequency signal, and provide the digital baseband signal or digital intermediate frequency signal to the processor 1011 so that the processor 1011 can further process the digital baseband signal or digital intermediate frequency signal, such as demodulation and decoding. In addition, the transmitter Tx in the transceiver 1013 is also used to receive a modulated digital baseband signal or digital intermediate frequency signal from the processor 1011, convert the modulated digital baseband signal or digital intermediate frequency signal into a radio frequency signal, and transmit the radio frequency signal through one or more antennas 1015. Specifically, the receiver Rx can selectively perform one or more stages of down-mixing and analog-to-digital conversion on the RF signal to obtain a digital baseband signal or a digital intermediate frequency signal. The order of the down-mixing and analog-to-digital conversion processes is adjustable. The transmitter Tx can selectively perform one or more stages of up-mixing and digital-to-analog conversion on the modulated digital baseband signal or digital intermediate frequency signal to obtain a RF signal. The order of the up-mixing and digital-to-analog conversion processes is adjustable. The digital baseband signal and the digital intermediate frequency signal may be collectively referred to as digital signals.

The transceiver 1013 may also be referred to as a transceiver unit, a transceiver, a transceiver device, etc. Optionally, a device in the transceiver unit that implements a receiving function may be referred to as a receiving unit, and a device in the transceiver unit that implements a transmitting function may be referred to as a transmitting unit. That is, the transceiver unit includes a receiving unit and a transmitting unit. The receiving unit may also be referred to as a receiver, an input port, a receiving circuit, etc., and the transmitting unit may be referred to as a transmitter, a transmitter, or a transmitting circuit, etc.

It should be noted that the communication device 1000 shown in Figure 10 can be specifically used to implement the steps implemented by the network device in the aforementioned method embodiment, and to achieve the corresponding technical effects of the network device. The specific implementation methods of the communication device 1000 shown in Figure 10 can refer to the description in the aforementioned method embodiment, and will not be repeated here one by one.

When the above-mentioned communication device is a chip applied to a terminal, the terminal chip implements the functions of the terminal in the above-mentioned method embodiment. The terminal chip receives information from other modules in the terminal (such as a radio frequency module or antenna), and the information is sent by the base station to the terminal; or the terminal chip sends information to other modules in the terminal (such as a radio frequency module or antenna), and the information is sent by the terminal to the base station. For example, when the first device is a terminal, the terminal sending the indication information can be understood as the process of the terminal chip outputting the indication information.

When the above-mentioned communication device is a module applied to a base station, the base station module implements the functions of the base station in the above-mentioned method embodiment. The base station module receives information from other modules in the base station (such as a radio frequency module or an antenna), and the information is sent by the terminal to the base station; or, the base station module sends information to other modules in the base station (such as a radio frequency module or an antenna), and the information is sent by the base station to the terminal. The base station module here can be a baseband chip of the base station, or it can be a DU or other module. The DU here can be a DU under the open radio access network (O-RAN) architecture. For example, in the case where the network device is a base station, the base station sending indication information can be understood as the process of the base station chip outputting indication information.

The method steps in the embodiments of the present application can be implemented in hardware or in software instructions that can be executed by a processor. The software instructions can be composed of corresponding software modules, and the software modules can be stored in random access memory, flash memory, read-only memory, programmable read-only memory, erasable programmable read-only memory, electrically erasable programmable read-only memory, registers, hard disk, mobile hard disk, CD-ROM or any other form of storage medium well known in the art. An exemplary storage medium is coupled to the processor so that the processor can read information from the storage medium and write information to the storage medium. The storage medium can also be an integral part of the processor. The processor and storage medium can be located in an ASIC. In addition, the ASIC can be located in a base station or a terminal. The processor and storage medium can also exist in a base station or a terminal as discrete components.

In the above embodiments, all or part of the embodiments may be implemented using software, hardware, firmware, or any combination thereof. When implemented using software, all or part of the embodiments may be implemented in the form of a computer program product. The computer program product includes one or more computer programs or instructions. When the computer program or instructions are loaded and executed on a computer, the processes or functions described in the embodiments of the present application are performed in whole or in part. The computer may be a general-purpose computer, a special-purpose computer, a computer network, a network device, a user device, or other programmable device. The computer program or instructions may be stored in a computer-readable storage medium or transferred from one computer-readable storage medium to another. For example, the computer program or instructions may be transferred from one website, computer, server, or data center to another website, computer, server, or data center via wired or wireless means. The computer-readable storage medium may be any available medium that can be accessed by a computer or a data storage device such as a server or data center that integrates one or more available media. The available medium may be a magnetic medium, such as a floppy disk, hard disk, or magnetic tape; an optical medium, such as a digital video disk; or a semiconductor medium, such as a solid-state drive. The computer-readable storage medium may be a volatile or nonvolatile storage medium, or may include both volatile and nonvolatile types of storage media.

In the various embodiments of the present application, unless otherwise specified or there is a logical conflict, the terms and/or descriptions between different embodiments are consistent and can be referenced by each other. The technical features in different embodiments can be combined to form new embodiments according to their inherent logical relationships.

Claims (17)

A communication method, characterized in that the method comprises: Sending first indication information, where the first indication information is used to indicate that the terminal device supports discontinuity between a first long term evolution LTE carrier and a first new radio interface NR carrier, where the first LTE carrier and the first NR carrier are two carriers in intra-band EN-DC; receiving configuration information, where the configuration information is used to configure the first LTE carrier and the first NR carrier; Accessing the network according to the first rule and the configuration information, the first rule includes: the nominal channel spacing is equal to the channel spacing between the LTE carrier and the NR carrier in the intra-band discontinuous EN-DC, and the nominal channel spacing is the channel spacing between adjacent LTE carriers and NR carriers in the intra-band continuous EN-DC. The method according to claim 1 is characterized in that the first indication information is also used to indicate that the terminal device supports the first LTE carrier and the first NR carrier to be continuous. A communication method, characterized in that the method comprises: Receive first indication information, where the first indication information is used to indicate that the terminal device supports discontinuity between a first long term evolution (LTE) carrier and a first new radio (NR) carrier, where the first LTE carrier and the first NR carrier are two carriers in intra-band EN-DC; Configuration information is sent according to a first rule, where the configuration information is used to configure the first LTE carrier and the first NR carrier; the first rule includes: a nominal channel spacing is equal to the channel spacing between the LTE carrier and the NR carrier in intra-band discontinuous EN-DC, and the nominal channel spacing is the channel spacing between adjacent LTE carriers and NR carriers in intra-band continuous EN-DC. The method according to claim 3 is characterized in that the first indication information is also used to indicate that the terminal device supports the continuity of the first LTE carrier and the first NR carrier. A communication method, characterized in that the method comprises: Sending first indication information, where the first indication information is used to indicate that the terminal device supports discontinuity between a first long term evolution LTE carrier and a first new radio interface NR carrier, where the first LTE carrier and the first NR carrier are two carriers in intra-band EN-DC; receiving configuration information, where the configuration information is used to configure the first LTE carrier and the first NR carrier; Accessing the network based on the configuration information and the second guard band, the second guard band is the guard band supported by the terminal device, the second guard band is smaller than the first guard band, and the first guard band is a predefined guard band corresponding to any channel bandwidth and subcarrier spacing. The method according to claim 5, further comprising: The second indication information is sent, where the second indication information is used to indicate the second protection band supported by the terminal device. The method according to claim 5 or 6 is characterized in that the difference between the first guard band and the second guard band is at least one frequency domain unit, and the frequency domain unit includes any one of the following: resource block, grid, subcarrier spacing. The method according to claim 7, further comprising: Third indication information is sent, where the third indication information is used to indicate the frequency domain unit. A communication method, characterized in that the method comprises: Receive first indication information, where the first indication information is used to indicate that the terminal device supports discontinuity between a first long term evolution (LTE) carrier and a first new radio (NR) carrier, where the first LTE carrier and the first NR carrier are two carriers in intra-band EN-DC; Receive second indication information, where the second indication information is used to indicate a second guard band supported by the terminal device, where the second guard band is smaller than the first guard band, and the first guard band is a predefined guard band corresponding to any channel bandwidth and subcarrier spacing; Send configuration information, where the configuration information is used to configure the first LTE carrier and the first NR carrier, and the configuration information and the second protection band are used for the terminal device to access the network. The method according to claim 9 is characterized in that the difference between the first guard band and the second guard band is at least one frequency domain unit, and the frequency domain unit includes any one of the following: resource block, grid, and subcarrier spacing. The method according to claim 9 or 10, characterized in that the method further comprises: Third indication information is received, where the third indication information is used to indicate the frequency domain unit. A communication device, characterized in that the communication device comprises: a processing unit and a transceiver unit; The processing unit and the transceiver unit are configured to execute the method according to any one of claims 1 to 11. A communication device, characterized by comprising at least one processor, wherein the at least one processor is coupled to at least one memory; the at least one processor is configured to execute the method according to any one of claims 1 to 11. A chip or a chip system, characterized in that the chip or the chip system is used to execute the method according to any one of claims 1 to 11. A communication system, characterized in that it includes a communication device for executing the method of any one of claims 1-2, and a communication device for executing the method of any one of claims 3-4, or includes a communication device for executing the method of any one of claims 5-8, and a communication device for executing the method of any one of claims 9-11. A readable storage medium, characterized in that a computer program or instruction is stored in the storage medium, and when the computer program or instruction is executed by a communication device, the method according to any one of claims 1 to 11 is implemented. A computer program product, characterized by comprising instructions, which, when the instructions are executed on a computer, cause the computer to execute the method according to any one of claims 1 to 11.