CN115668838B - Wireless communication method, terminal device and network device - Google Patents

Abstract

The embodiment of the present application provides a wireless communication method, a terminal device and a network device, the method comprising: the terminal device receives indication information, the indication information is used to indicate whether to activate the cross-carrier scheduling mode or the same-carrier scheduling mode of the first serving cell of the terminal device, thereby improving the adaptability of the carrier scheduling mode.

Description

Wireless communication method, terminal device and network device

Technical Field

The embodiments of the present application relate to the field of communications, and more specifically, to a wireless communication method, a terminal device, and a network device.

Background technique

Carrier Aggregation (CA) enables the New Radio (NR) system to support a larger bandwidth and achieve a higher system peak rate by jointly scheduling and using resources on multiple component carriers (CCs). In CA, the scheduling of each CC is divided into same-carrier scheduling and cross-carrier scheduling according to whether the CC where the Physical Downlink Control Channel (PDCCH) resources used for scheduling are located and the CC being scheduled are the same CC.

In the prior art, the scheduling mode of a CC is either a cross-carrier scheduling mode or a same-carrier scheduling mode, and the carrier scheduling mode is semi-statically configured through Radio Resource Control (RRC) signaling. The reason for using cross-carrier scheduling is that the PDCCH of the current serving cell of the terminal device is interfered, so scheduling is performed through the PDCCH of another cell. However, since the interference to a cell is not necessarily stable, the above-mentioned carrier scheduling mode configured by semi-static RRC signaling has the problem of low adaptability.

Summary of the invention

The embodiments of the present application provide a wireless communication method, a terminal device, and a network device, thereby improving the adaptability of the carrier scheduling method.

In a first aspect, a wireless communication method is provided, the method comprising: a terminal device receives indication information, the indication information being used to indicate whether to activate a cross-carrier scheduling mode or a same-carrier scheduling mode of a first service cell of the terminal device.

In a second aspect, a wireless communication method is provided, the method comprising: a network device sends indication information to a terminal device, the indication information being used to indicate whether to activate a cross-carrier scheduling mode or a same-carrier scheduling mode of a first service cell of the terminal device.

In a third aspect, a terminal device is provided for executing the method in the first aspect or its various implementations.

Specifically, the terminal device includes a functional module for executing the method in the above-mentioned first aspect or its various implementation modes.

In a fourth aspect, a network device is provided for executing the method in the second aspect or its respective implementation manners.

Specifically, the network device includes a functional module for executing the method in the above-mentioned second aspect or its various implementation modes.

In a fifth aspect, a terminal device is provided, comprising a processor and a memory, wherein the memory is used to store a computer program, and the processor is used to call and run the computer program stored in the memory to execute the method in the first aspect or its implementations.

In a sixth aspect, a network device is provided, comprising a processor and a memory, wherein the memory is used to store a computer program, and the processor is used to call and run the computer program stored in the memory to execute the method in the second aspect or its implementation manners.

In a seventh aspect, a device is provided for implementing the method in any one of the first to second aspects or any of their implementations.

Specifically, the apparatus includes: a processor, configured to call and run a computer program from a memory, so that a device equipped with the apparatus executes a method as described in any one of the first to second aspects or in each of their implementations.

In an eighth aspect, a computer-readable storage medium is provided for storing a computer program, wherein the computer program enables a computer to execute the method of any one of the first to second aspects or any of their implementations.

In a ninth aspect, a computer program product is provided, comprising computer program instructions, wherein the computer program instructions enable a computer to execute the method in any one of the first to second aspects or any of their implementations.

In a tenth aspect, a computer program is provided, which, when executed on a computer, enables the computer to execute the method in any one of the first to second aspects or in each of their implementations.

Through the technical solution of the first aspect or the second aspect above, the terminal device can determine whether to activate the cross-carrier scheduling mode or the same-carrier scheduling mode of the first service cell of the terminal device according to the indication information to dynamically adjust the carrier scheduling mode, thereby improving the adaptability of the carrier scheduling mode to adapt to the cell environment, such as changes in interference. For example, when the interference of the first service cell is large, the terminal device can activate the cross-carrier scheduling mode to perform data scheduling in other cells. When the interference of the first service cell is small, the terminal device can activate the same-carrier scheduling mode to perform data scheduling in the current cell.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG1 is a schematic diagram of a communication system architecture provided in an embodiment of the present application;

FIG2 is a schematic diagram of carrier aggregation provided in an embodiment of the present application;

FIG3 is a schematic diagram of another carrier aggregation provided in an embodiment of the present application;

FIG4 is a schematic diagram of same-carrier scheduling provided by an embodiment of the present application;

FIG5 is a schematic diagram of cross-carrier scheduling provided by an embodiment of the present application;

FIG6 is an interactive flow chart of a wireless communication method provided by an embodiment of the present application;

FIG7 is a schematic diagram of a MAC CE provided in an embodiment of the present application;

FIG8 is a schematic diagram of another MAC CE provided in an embodiment of the present application;

FIG9 is a schematic diagram of another MAC CE provided in an embodiment of the present application;

FIG10 shows a schematic block diagram of a terminal device 1000 according to an embodiment of the present application;

FIG11 shows a schematic block diagram of a network device 1100 according to an embodiment of the present application;

FIG12 is a schematic structural diagram of a communication device 1200 provided in an embodiment of the present application;

FIG13 is a schematic structural diagram of a device according to an embodiment of the present application;

FIG. 14 is a schematic block diagram of a communication system 1400 provided in an embodiment of the present application.

Detailed ways

The following will describe the technical solutions in the embodiments of the present application in conjunction with the drawings in the embodiments of the present application. Obviously, the described embodiments are part of the embodiments of the present application, not all of the embodiments. For the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of this application.

The embodiments of the present application can be applied to various communication systems, such as: Global System of Mobile communication (GSM) system, Code Division Multiple Access (CDMA) system, Wideband Code Division Multiple Access (WCDMA) system, General Packet Radio Service (GPRS), Long Term Evolution (LTE) system, Advanced Long Term Evolution (LTE-A) system, New Radio (NR), NR system evolution system, LTE on unlicensed spectrum (LTE-U) system, NR on unlicensed spectrum (NR-based access to unlicensed spectrum, NR-U) system, Universal Mobile Telecommunication System (UMTS), Wireless Local Area Networks (WLAN), Wireless Fidelity (WiFi), next generation communication system or other communication systems, etc.

Generally speaking, traditional communication systems support a limited number of connections and are easy to implement. However, with the development of communication technology, mobile communication systems will not only support traditional communications, but will also support, for example, device to device (Device to Device, D2D) communication, machine to machine (Machine to Machine, M2M) communication, machine type communication (Machine Type Communication, MTC), and vehicle to vehicle (Vehicle to Vehicle, V2V) communication, etc. The embodiments of the present application can also be applied to these communication systems.

Optionally, the communication system in the embodiment of the present application can be applied to a CA scenario or a dual connectivity (DC) + CA scenario.

The embodiments of the present application do not limit the spectrum to which they are applied. For example, the embodiments of the present application can be applied to licensed spectrum or unlicensed spectrum.

Exemplarily, a communication system 100 used in an embodiment of the present application is shown in FIG1. The communication system 100 may include a network device 110, which may be a device that communicates with a terminal device 120 (or referred to as a communication terminal or terminal). The network device 110 may provide communication coverage for a specific geographic area and may communicate with terminal devices located in the coverage area.

FIG1 exemplarily shows a network device and two terminal devices. Optionally, the communication system 100 may include multiple network devices and each network device may include another number of terminal devices within its coverage area, which is not limited in the embodiments of the present application.

Optionally, the communication system 100 may also include other network entities such as a network controller and a mobility management entity, which is not limited in the embodiments of the present application.

It should be understood that the device with communication function in the network/system in the embodiment of the present application can be called a communication device. Taking the communication system 100 shown in Figure 1 as an example, the communication device may include a network device 110 and a terminal device 120 with communication function, and the network device 110 and the terminal device 120 may be the specific devices described above, which will not be repeated here; the communication device may also include other devices in the communication system 100, such as other network entities such as a network controller and a mobile management entity, which is not limited in the embodiment of the present application.

It should be understood that the terms "system" and "network" are often used interchangeably in this article. The term "and/or" in this article is only a description of the association relationship of associated objects, indicating that there can be three relationships. For example, A and/or B can represent: A exists alone, A and B exist at the same time, and B exists alone. In addition, the character "/" in this article generally indicates that the associated objects before and after are in an "or" relationship.

The embodiments of the present application describe various embodiments in combination with terminal devices and network devices, wherein: the terminal device may also be referred to as user equipment (UE), access terminal, user unit, user station, mobile station, mobile station, remote station, remote terminal, mobile device, user terminal, terminal, wireless communication device, user agent or user device, etc. The terminal device may be a station (STAION, ST) in a WLAN, a cellular phone, a cordless phone, a Session Initiation Protocol (SIP) phone, a Wireless Local Loop (WLL) station, a Personal Digital Assistant (PDA) device, a handheld device with wireless communication function, a computing device or other processing device connected to a wireless modem, a vehicle-mounted device, a wearable device, and a next-generation communication system, for example, a terminal device in an NR network or a terminal device in a future evolved Public Land Mobile Network (PLMN) network, etc.

As an example but not limitation, in the embodiments of the present application, the terminal device may also be a wearable device. Wearable devices may also be referred to as wearable smart devices, which are a general term for wearable devices that are intelligently designed and developed using wearable technology for daily wear, such as glasses, gloves, watches, clothing, and shoes. A wearable device is a portable device that is worn directly on the body or integrated into the user's clothes or accessories. Wearable devices are not only hardware devices, but also powerful functions achieved through software support, data interaction, and cloud interaction. Broadly speaking, wearable smart devices include full-featured, large-sized, and fully or partially independent of smartphones, such as smart watches or smart glasses, as well as devices that only focus on a certain type of application function and need to be used in conjunction with other devices such as smartphones, such as various types of smart bracelets and smart jewelry for vital sign monitoring.

The network device can be a device used to communicate with a mobile device. The network device can be an access point (AP) in WLAN, a base station (Base Transceiver Station, BTS) in GSM or CDMA, a base station (NodeB, NB) in WCDMA, an evolved base station (Evolutional Node B, eNB or eNodeB) in LTE, or a relay station or access point, or a vehicle-mounted device, a wearable device, and a network device or base station (gNB) in an NR network, or a network device in a future evolved PLMN network, etc.

In an embodiment of the present application, a network device provides services for a cell, and a terminal device communicates with the network device through transmission resources (e.g., frequency domain resources, or spectrum resources) used by the cell. The cell may be a cell corresponding to a network device (e.g., a base station). The cell may belong to a macro base station or a base station corresponding to a small cell. The small cells here may include: a metro cell, a micro cell, a picocell, a femtocell, etc. These small cells have the characteristics of small coverage and low transmission power, and are suitable for providing high-speed data transmission services.

Before introducing the technical solution of this application, the following first introduces CA:

In order to provide a higher system peak rate, a maximum transmission bandwidth of 100MHz is required. However, due to the scarcity of such a large continuous spectrum, CA is proposed, that is, aggregating multiple continuous or non-continuous carriers to obtain a larger transmission bandwidth, thereby obtaining a higher peak rate and throughput. Among them, according to whether the aggregated carriers are continuous in the spectrum, it can be divided into continuous carrier aggregation and non-continuous carrier aggregation.

CA aggregates two or more CCs to support a larger transmission bandwidth (up to 100 MHz). The standard stipulates that CA aggregates up to five CCs, and the aggregated CCs belong to the same network device.

The bandwidth of each CC can be 5MHz, 10MHz, 15MHz and 20MHz, but the maximum bandwidth does not exceed 20MHz. As shown in Figure 2, using CA technology, 2 non-contiguous 20MHz CCs can be aggregated to obtain a bandwidth of 40MHz. As shown in Figure 3, using CA technology, 5 consecutive 20MHz CCs can be aggregated to obtain a bandwidth of 100MHz.

In order to efficiently utilize fragmented spectrum, CA supports aggregation between different CCs as follows:

(1) CCs with the same or different bandwidths;

(2) Adjacent or non-adjacent CCs in the same frequency band;

(3) CCs in different frequency bands;

Depending on whether the frequency bands of aggregated CCs are the same, CA can be divided into intra-band carrier aggregation and inter-band carrier aggregation.

Basic concepts in CA:

Primary Cell (PCell): It is the cell where the terminal device establishes the initial connection, or the cell where the RRC connection is reestablished, or the primary cell designated during the handover process. PCell is responsible for RRC communication with the terminal device. The CC corresponding to the PCell is called the Primary Component Carrier (PCC). The Physical Uplink Control Channel (PUCCH) is on the PCC and only exists on the PCC. Among them, the downlink carrier of the PCell is called the downlink (DL) PCC, and the uplink carrier of the PCell is called the uplink (UL) PCC.

Secondary Cell (SCell): It is added during RRC reconfiguration to provide additional wireless resources. There is no RRC communication between the SCell and the terminal device. The CC corresponding to the SCell is called the Secondary Component Carrier (SCC). The downlink carrier of the SCell is called the DL SCC, and the uplink carrier of the SCell is called the UL SCC.

The PCell is determined at the time of connection establishment. The SCell is added/modified/released via the RRC Connection Reconfiguration message after the initial security activation procedure.

Serving cell: A cell that provides services (i.e., uplink and downlink transmission) for terminal devices. If the terminal device is in the RRC connected state (RRC_CONNECTED) but CA is not configured, the terminal device has only one serving cell, namely PCell; if the terminal device is in the RRC_CONNECTED state and CA is configured, the serving cell set of the terminal device includes PCell and all SCells. That is, the serving cell can refer to both PCell and SCell. A terminal device configured with CA can be connected to 1 PCell and up to 4 SCells. A terminal device configured with CA uses the same Cell-RadioNetworkTemporaryIdentifier (C-RNTI) in all serving cells to ensure that C-RNTI does not conflict in all serving cells.

For any terminal device, each CC (cell) has a corresponding index. The index of PCell is fixed to 0, while the index of each SCell is specially configured by the network device for the terminal device.

Since both asymmetric and symmetric carrier aggregation are supported, downlink carrier aggregation is required, but uplink carrier aggregation is not required. In addition, for PCell, there must be PDCCH and PUCCH of this cell, and only PCell has PUCCH, while other secondary cells may have PDCCH.

As described above, the scheduling of each CC in CA is divided into same-carrier scheduling and cross-carrier scheduling according to whether the CC where the PDCCH resources used for scheduling are located and the scheduled CC are the same CC.

Same-carrier scheduling means that the PDCCH scheduling of a serving cell is performed on the radio resources of the cell, that is, the scheduling information and the CC used for data transmission are the same CC.

Cross-carrier scheduling refers to allowing the PDCCH of one serving cell to schedule the radio resources of another serving cell. That is, the scheduling information is transmitted on one CC, while the corresponding data is transmitted on another CC. The introduction of cross-carrier scheduling is based on interference avoidance in heterogeneous networks.

Exemplarily, FIG4 is a schematic diagram of same-carrier scheduling provided in an embodiment of the present application. As shown in FIG4, the scheduling of each physical downlink shared channel (PDSCH) is scheduled through the PDCCH on its own CC. FIG5 is a schematic diagram of cross-carrier scheduling provided in an embodiment of the present application. As shown in FIG5, the scheduling of PDSCH on three CCs is scheduled through the PDCCH on one CC.

It should be noted that in cross-carrier scheduling, the scheduling information between different CCs is distinguished by the Carrier Indicator Field (CIF) in the Downlink Control Information (DCI). CIF is used to indicate the CC number, which is fixed to 3 bits and takes values from 0 to 7, of which the CIF of the PCC is fixed to 0. There may be multiple CCs with PDCCH channels, but the PCC must have its own PDCCH channel. The network device can indicate which CC's PDCCH channel the current SCC uses for scheduling through high-level signaling configuration.

As described above, in the prior art, the scheduling mode of a CC is either cross-carrier scheduling mode or same-carrier scheduling mode, and the carrier scheduling mode is semi-statically configured through RRC signaling. This carrier scheduling mode configured semi-statically through RRC signaling has the problem of low adaptability.

In order to solve the above technical problems, the present application enables the terminal device to dynamically change or adjust the carrier scheduling method through dynamic indication.

The technical solution of the present application is described in detail below through specific embodiments.

FIG6 is an interactive flow chart of a wireless communication method provided by an embodiment of the present application, the method comprising the following steps:

Step S610: The terminal device receives indication information, where the indication information is used to indicate whether to activate the cross-carrier scheduling mode or the same-carrier scheduling mode of the first service cell of the terminal device.

It should be understood that, in the present application, certain information of a cell may also be referred to as certain information of a CC, where the CC is the CC corresponding to the cell. For example, a carrier scheduling mode of a cell may be referred to as a scheduling mode of a CC.

Optionally, the network device may configure an initial default carrier scheduling mode of the first serving cell for the first serving cell through a first dedicated signaling.

Optionally, the first dedicated signaling may be RRC signaling, DCI or Media Access Control Control Element (MAC CE).

In the present application, when the terminal device enters the RRC_CONNECTED state, the network device may send first configuration information to the terminal device, where the first configuration information includes: configuration information of a cross-carrier scheduling method of a first serving cell of the terminal device.

Optionally, the network device may send the first configuration information via second dedicated signaling.

Optionally, the second dedicated signaling may be RRC signaling, DCI signaling or MAC CE.

Optionally, the first serving cell is also described as a current serving cell of the terminal device.

Optionally, the first service cell is a PCell or SCell of the terminal device.

Optionally, the configuration information of the cross-carrier scheduling method includes: an identity (ID) of the second serving cell and a CIF in the scheduling information of the first serving cell. The second serving cell is used to schedule the first serving cell. That is, the PDCCH on the second serving cell is used to schedule data of the first serving cell.

Optionally, the data of the first service cell may be uplink data or downlink data. When the data of the first service cell is uplink data, the PDCCH on the second service cell is used to schedule the data of the first service cell, which can also be described as: the PDCCH on the second service cell is used to schedule the physical uplink shared channel (Physical Uplink Shared Channel, PUSCH) of the first service cell. When the data of the first service cell is downlink data, the PDCCH on the second service cell is used to schedule the data of the first service cell, which can also be described as: the PDCCH on the second service cell is used to schedule the PDSCH of the first service cell.

Optionally, the scheduling information of the first serving cell may also be described as scheduling information of the PDCCH or DCI of the first serving cell, where the scheduling information is used to schedule data of the first serving cell.

It should be understood that for the same carrier scheduling method, since the scheduling information and the CC used for data transmission are the same CC, the network device does not need to send the configuration information of the same carrier scheduling method to the terminal device. However, the terminal device needs to know whether the network device supports the same carrier scheduling method or whether it supports the dynamic adjustment of the carrier scheduling method. Among them, the terminal device can know whether the network device supports the same carrier scheduling method or whether it supports the dynamic adjustment of the carrier scheduling method in the following ways, but not limited to this:

(1) The first configuration information further includes: a first indication. The first indication is used to indicate a same-carrier scheduling mode of a first serving cell supporting the terminal device.

(2) The first configuration information further includes: a second indication. The second indication is used to indicate support for dynamic adjustment of carrier scheduling mode.

(3) The terminal device supports the same-carrier scheduling mode by default.

Explanation for item (1):

Optionally, the first indication may be set at a preset bit position of the second dedicated signaling, and the length may be a preset length.

Optionally, the preset bit position and preset length may be configured by the network device, and the present application does not limit how to determine the preset bit position and preset length, as well as the position of the preset bit position and the preset length.

Optionally, the preset length may be 1, and accordingly, the value of the first indication may be 0 or 1. When the value of the first indication is 0, it indicates that the same-carrier scheduling mode of the first serving cell of the terminal device is supported. Alternatively, when the value of the first indication is 1, it indicates that the same-carrier scheduling mode of the first serving cell of the terminal device is supported.

Optionally, when the first configuration information includes the first indication and configuration information of the cross-carrier scheduling method of the first service cell, it means that the terminal device supports the same-carrier scheduling method and the cross-carrier scheduling method of the first service cell. Based on this, the terminal device can dynamically adjust the carrier scheduling method according to the above indication information.

Explanation for item (2):

Optionally, the second indication is at a serving cell level or a terminal device level. That is, the second indication may indicate that the first serving cell supports dynamic adjustment of the carrier scheduling mode. It may also indicate that the terminal device supports adjustment of the carrier scheduling mode.

Optionally, the second indication may be set at a preset bit position of the second dedicated signaling, and the length may be a preset length.

Optionally, the preset bit position and preset length may be configured by the network device, and the present application does not limit how to determine the preset bit position and preset length, as well as the position of the preset bit position and the preset length.

Optionally, the preset length may be 1, and accordingly, the value of the second indication may be 0 or 1. When the value of the second indication is 0, it indicates that the dynamic adjustment of the carrier scheduling mode is supported. Alternatively, when the value of the first indication is 1, it indicates that the dynamic adjustment of the carrier scheduling mode is supported.

Optionally, when the first configuration information includes the second indication and configuration information of the cross-carrier scheduling mode of the first service cell, it means that the terminal device supports the same-carrier scheduling mode and cross-carrier scheduling mode of the first service cell. Based on this, the terminal device can dynamically adjust the carrier scheduling mode according to the above indication information.

It should be understood that when the initial default carrier scheduling mode of the first service cell is the same-carrier scheduling mode, then activating the same-carrier scheduling mode can be understood as using the same-carrier scheduling mode; when the initial default carrier scheduling mode of the first service cell is the cross-carrier scheduling mode, then activating the same-carrier scheduling mode can be understood as switching the carrier scheduling mode to the cross-carrier scheduling mode or using the cross-carrier scheduling mode; when the initial default carrier scheduling mode of the first service cell is the cross-carrier scheduling mode, then activating the same-carrier scheduling mode can be understood as switching the carrier scheduling mode to the same-carrier scheduling mode or using the same-carrier scheduling mode; when the initial default carrier scheduling mode of the first service cell is the cross-carrier scheduling mode, then activating the cross-carrier scheduling mode can be understood as using the cross-carrier scheduling mode.

Alternatively, "activated" is relative to "inactivated", and the initial default carrier scheduling mode can be understood as the carrier scheduling mode in the inactivated state.

It should be noted that the time when the terminal device receives the indication information is the same as the time when the cross-carrier scheduling mode or the same-carrier scheduling mode is activated. Alternatively, the time difference between the time when the terminal device receives the indication information and the time when the cross-carrier scheduling mode or the same-carrier scheduling mode is activated is a preset value. For example: the time when the terminal device receives the indication information is n, and the time when the cross-carrier scheduling mode or the same-carrier scheduling mode is activated is n+k, where k is a preset value.

Optionally, the preset value is configured by the network device, such as the preset value is configured by the network device through RRC signaling, DCI or MAC CE.

Optionally, in the present application, the time unit may be a subframe, a symbol, or a time slot, etc., and the present application does not impose any limitation on this.

In summary, in the present application, the terminal device can determine whether to activate the cross-carrier scheduling mode or the same-carrier scheduling mode of the first service cell of the terminal device according to the indication information to dynamically adjust the carrier scheduling mode, thereby improving the adaptability of the carrier scheduling mode to adapt to the cell environment, such as changes in interference. For example: when the interference of the first service cell is large, the terminal device can activate the cross-carrier scheduling mode to perform data scheduling in other cells. When the interference of the first service cell is small, the terminal device can activate the same-carrier scheduling mode to perform data scheduling in this cell.

The above-mentioned indication information will be described in detail below, wherein the functions of the indication information are as follows, but not limited to these:

(1) The indication information includes multiple bits, each bit being used to indicate whether a serving cell activates a cross-carrier scheduling mode or a same-carrier scheduling mode of the serving cell.

(2) The indication information includes a plurality of bits, each bit being used to indicate whether a serving cell configured to support a cross-carrier scheduling mode activates the cross-carrier scheduling mode or the same-carrier scheduling mode of the serving cell.

(3) The indication information includes a plurality of bits, each bit being used to indicate whether a serving cell configured to support dynamic adjustment of carrier scheduling mode activates the cross-carrier scheduling mode or the same-carrier scheduling mode of the serving cell.

Optionally, the above indication information may be carried in a MAC CE or a DCI. If the indication information is carried in a MAC CE, each MAC CE defines a logical channel identity (LCID) to identify the MAC CE in a MAC packet data unit (PDU).

When the indication information is carried in the MAC CE, the functions of the indication information are described as follows:

Explanation for item (1):

MAC CE can be 8 bits, as shown in Figure 7, or 32 bits, as shown in Figure 8. Each bit corresponds to a service cell. Ci corresponds to the service cell with ID i, and the value of Ci indicates whether to activate the same-carrier scheduling mode or the cross-carrier scheduling mode of the service cell. For example, 0 indicates activation of the same-carrier scheduling, and 1 indicates activation of the cross-carrier scheduling. Alternatively, 1 indicates activation of the same-carrier scheduling, and 0 indicates activation of the cross-carrier scheduling.

Explanation for item (2):

MAC CE can be a MAC CE with an integer multiple of 8 bits. As shown in Figure 9, the MAC CE is a 16-bit MAC CE, in which each bit corresponds to a service cell configured to support cross-carrier scheduling. Ci corresponds to the service cell with ID i that is configured to support cross-carrier scheduling. The value of Ci indicates whether the same-carrier scheduling mode or cross-carrier scheduling mode of the service cell is activated. For example, 0 indicates activation of same-carrier scheduling, and 1 indicates activation of cross-carrier scheduling. Or, 1 indicates activation of same-carrier scheduling, and 0 indicates activation of cross-carrier scheduling. The number of bits included in the indication information or MAC CE is ceil(n/8)*8, where n is the number of service cells supporting cross-carrier scheduling. ceil() is an upward rounding function. For example, n=12, the number of bits included in the MAC CE is Ceil(12/8)*8=16.

Explanation for item (3):

MAC CE can be a MAC CE with an integer multiple of 8 bits. As shown in Figure 9, the MAC CE is a 16-bit MAC CE, where each bit corresponds to a service cell configured to support dynamic adjustment of carrier scheduling, Ci corresponds to a service cell with ID i configured to support dynamic adjustment of carrier scheduling, and the value of Ci indicates whether the same-carrier scheduling mode or cross-carrier scheduling mode of the service cell is activated. For example, 0 indicates activation of same-carrier scheduling, and 1 indicates activation of cross-carrier scheduling. Alternatively, 1 indicates activation of same-carrier scheduling, and 0 indicates activation of cross-carrier scheduling. The number of bits included in the indication information or MAC CE is ceil(n/8)*8, where n is the number of service cells supporting dynamic adjustment of carrier scheduling. For example, n=12, and the number of bits included in the MAC CE is Ceil(12/8)*8=16.

When the indication information is carried in the DCI, the DCI may carry a bitmap defined according to the number of bits in the MAC CE in the above three cases, wherein the definition of each bit in the DCI or the indication information may refer to the definition of each bit in the above MAC CE, and this application will not go into details therein.

In summary, in the present application, the indication information includes multiple bits, each bit is used to indicate whether a service cell activates the cross-carrier scheduling mode or the same-carrier scheduling mode of the service cell. Alternatively, the indication information includes multiple bits, each bit is used to indicate whether a service cell configured to support the cross-carrier scheduling mode activates the cross-carrier scheduling mode or the same-carrier scheduling mode of the service cell. Alternatively, the indication information includes multiple bits, each bit is used to indicate whether a service cell configured to support the dynamic adjustment of the carrier scheduling mode activates the cross-carrier scheduling mode or the same-carrier scheduling mode of the service cell. This allows the terminal device to determine whether to activate the cross-carrier scheduling mode or the same-carrier scheduling mode of the first service cell of the terminal device according to the indication information, so as to dynamically adjust the carrier scheduling mode, thereby improving the adaptability of the carrier scheduling mode.

The above text, in combination with Figures 6 to 9, describes in detail the method embodiment of the present application. The following text, in combination with Figures 10 to 14, describes in detail the device embodiment of the present application. It should be understood that the device embodiment and the method embodiment correspond to each other, and similar descriptions can refer to the method embodiment.

Fig. 10 shows a schematic block diagram of a terminal device 1000 according to an embodiment of the present application. As shown in Fig. 10, the terminal device 1000 includes: a communication unit 1010, configured to receive indication information, the indication information being used to indicate whether to activate a cross-carrier scheduling mode or a same-carrier scheduling mode of a first serving cell of the terminal device.

Optionally, the communication unit 1010 is further used to receive first configuration information, where the first configuration information includes: configuration information of a cross-carrier scheduling method of a first serving cell of the terminal device.

Optionally, the first configuration information further includes: a first indication. The first indication is used to indicate a same-carrier scheduling mode of the first serving cell supporting the terminal device.

Optionally, the first configuration information further includes: a second indication. The second indication is used to indicate support for dynamic adjustment of carrier scheduling mode.

Optionally, the second indication is at a serving cell level or a terminal device level.

Optionally, the terminal device supports the same-carrier scheduling mode by default.

Optionally, the configuration information of the cross-carrier scheduling mode includes: an identifier of the second serving cell and a CIF in the scheduling information of the first serving cell. The second serving cell is used to schedule the first serving cell.

Optionally, the indication information includes multiple bits, each bit is used to indicate whether a serving cell activates a cross-carrier scheduling mode or a same-carrier scheduling mode of the serving cell.

Optionally, the indication information includes multiple bits, each bit being used to indicate whether a serving cell configured to support a cross-carrier scheduling mode activates the cross-carrier scheduling mode or the same-carrier scheduling mode of the serving cell.

Optionally, the number of bits included in the indication information is ceil(n/8)*8, where n is the number of service cells supporting the cross-carrier scheduling method.

Optionally, the indication information includes multiple bits, each bit being used to indicate whether a service cell configured to support dynamic adjustment of carrier scheduling mode activates the cross-carrier scheduling mode or the same-carrier scheduling mode of the service cell.

Optionally, the number of bits included in the indication information is ceil(n/8)*8, where n is the number of service cells that support dynamic adjustment of carrier scheduling.

Optionally, the time when the terminal device receives the indication information is the same as the time when the cross-carrier scheduling mode or the same-carrier scheduling mode is activated.

Optionally, the time difference between the time when the terminal device receives the indication information and the time when the cross-carrier scheduling mode or the same-carrier scheduling mode is activated is a preset value.

Optionally, the preset value is configured by the network device.

Optionally, the indication information is carried in MAC CE or DCI.

Optionally, in some embodiments, the communication unit may be a communication interface or a transceiver, or an input/output interface of a communication chip or a system on chip. The processing unit may be one or more processors.

It should be understood that the terminal device 1000 according to the embodiment of the present application may correspond to the terminal device in the method embodiment of the present application, and the above and other operations and/or functions of each unit in the terminal device 1000 are respectively for implementing the corresponding processes of the terminal device in the above method embodiment, which will not be repeated here for the sake of brevity.

Fig. 11 shows a schematic block diagram of a network device 1100 according to an embodiment of the present application. As shown in Fig. 11, the network device 1100 includes: a communication unit 1110, configured to send indication information to a terminal device, the indication information being used to indicate whether to activate a cross-carrier scheduling mode or a same-carrier scheduling mode of a first serving cell of the terminal device.

Optionally, the communication unit 1110 is further used to send first configuration information to the terminal device, where the first configuration information includes: configuration information of a cross-carrier scheduling method of a first serving cell of the terminal device.

Optionally, the first configuration information further includes: a first indication. The first indication is used to indicate a same-carrier scheduling mode of the first serving cell supporting the terminal device.

Optionally, the first configuration information further includes: a second indication. The second indication is used to indicate support for dynamic adjustment of carrier scheduling mode.

Optionally, the second indication is at a serving cell level or a terminal device level.

Optionally, the terminal device supports the same-carrier scheduling mode by default.

Optionally, the configuration information of the cross-carrier scheduling mode includes: an identifier of the second serving cell and a CIF in the scheduling information of the first serving cell. The second serving cell is used to schedule the first serving cell.

Optionally, the indication information includes multiple bits, each bit is used to indicate whether a serving cell activates a cross-carrier scheduling mode or a same-carrier scheduling mode of the serving cell.

Optionally, the indication information includes multiple bits, each bit being used to indicate whether a serving cell configured to support a cross-carrier scheduling mode activates the cross-carrier scheduling mode or the same-carrier scheduling mode of the serving cell.

Optionally, the number of bits included in the indication information is ceil(n/8)*8, where n is the number of service cells supporting the cross-carrier scheduling method.

Optionally, the indication information includes multiple bits, each bit being used to indicate whether a service cell configured to support dynamic adjustment of carrier scheduling mode activates the cross-carrier scheduling mode or the same-carrier scheduling mode of the service cell.

Optionally, the number of bits included in the indication information is ceil(n/8)*8, where n is the number of service cells that support dynamic adjustment of carrier scheduling.

Optionally, the time when the terminal device receives the indication information is the same as the time when the cross-carrier scheduling mode or the same-carrier scheduling mode is activated.

Optionally, the time difference between the time when the terminal device receives the indication information and the time when the cross-carrier scheduling mode or the same-carrier scheduling mode is activated is a preset value.

Optionally, the preset value is configured by the network device.

Optionally, the indication information is carried in MAC CE or DCI.

Optionally, in some embodiments, the communication unit may be a communication interface or a transceiver, or an input/output interface of a communication chip or a system on chip. The processing unit may be one or more processors.

It should be understood that the network device 1100 according to the embodiment of the present application may correspond to the network device in the method embodiment of the present application, and the above and other operations and/or functions of each unit in the network device 1100 are respectively for implementing the corresponding processes of the network device in the above method embodiment, which will not be repeated here for the sake of brevity.

Fig. 12 is a schematic structural diagram of a communication device 1200 provided in an embodiment of the present application. The communication device 1200 shown in Fig. 12 includes a processor 1210, and the processor 1210 can call and run a computer program from a memory to implement the method in the embodiment of the present application.

Optionally, as shown in Fig. 12, the communication device 1200 may further include a memory 1220. The processor 1210 may call and run a computer program from the memory 1220 to implement the method in the embodiment of the present application.

The memory 1220 may be a separate device independent of the processor 1210 , or may be integrated into the processor 1210 .

Optionally, as shown in FIG. 12 , the communication device 1200 may further include a transceiver 1230 , and the processor 1210 may control the transceiver 1230 to communicate with other devices, specifically, may send information or data to other devices, or receive information or data sent by other devices.

The transceiver 1230 may include a transmitter and a receiver. The transceiver 1230 may further include an antenna, and the number of the antennas may be one or more.

Optionally, the communication device 1200 may specifically be a network device of an embodiment of the present application, and the communication device 1200 may implement corresponding processes implemented by the network device in each method of the embodiment of the present application, which will not be described in detail here for the sake of brevity.

Optionally, the communication device 1200 may specifically be a terminal device of an embodiment of the present application, and the communication device 1200 may implement the corresponding processes implemented by the terminal device in each method of the embodiment of the present application, which will not be described in detail here for the sake of brevity.

Fig. 13 is a schematic structural diagram of a device according to an embodiment of the present application. The device 1300 shown in Fig. 13 includes a processor 1310, and the processor 1310 can call and run a computer program from a memory to implement the method according to the embodiment of the present application.

Optionally, as shown in FIG13 , the apparatus 1300 may further include a memory 1320. The processor 1310 may call and run a computer program from the memory 1320 to implement the method in the embodiment of the present application.

The memory 1320 may be a separate device independent of the processor 1310 , or may be integrated into the processor 1310 .

Optionally, the apparatus 1300 may further include an input interface 1330. The processor 1310 may control the input interface 1330 to communicate with other devices or chips, and specifically, may obtain information or data sent by other devices or chips.

Optionally, the apparatus 1300 may further include an output interface 1340. The processor 1310 may control the output interface 1340 to communicate with other devices or chips, and specifically, may output information or data to other devices or chips.

Optionally, the device can be applied to the network equipment in the embodiments of the present application, and the device can implement the corresponding processes implemented by the network equipment in the various methods in the embodiments of the present application. For the sake of brevity, they will not be repeated here.

Optionally, the apparatus may be applied to a terminal device in an embodiment of the present application, and the apparatus may implement corresponding processes implemented by the terminal device in each method in an embodiment of the present application, which will not be described in detail here for the sake of brevity.

Optionally, the device mentioned in the embodiments of the present application may also be a chip, for example, a system-on-chip, a system-on-chip, a chip system, or a system-on-chip chip.

FIG14 is a schematic block diagram of a communication system 1400 provided in an embodiment of the present application. As shown in FIG14 , the communication system 1400 includes a terminal device 1410 and a network device 1420 .

Among them, the terminal device 1410 can be used to implement the corresponding functions implemented by the terminal device in the above method, and the network device 1420 can be used to implement the corresponding functions implemented by the network device or base station in the above method. For the sake of brevity, they are not repeated here.

It should be understood that the processor of the embodiment of the present application may be an integrated circuit chip with signal processing capabilities. In the implementation process, each step of the above method embodiment can be completed by the hardware integrated logic circuit or software instructions in the processor. The above processor can be a general processor, a digital signal processor (Digital Signal Processor, DSP), an application specific integrated circuit (Application Specific Integrated Circuit, ASIC), a field programmable gate array (Field Programmable Gate Array, FPGA) or other programmable logic devices, discrete gates or transistor logic devices, discrete hardware components. The methods, steps and logic block diagrams disclosed in the embodiments of the present application can be implemented or executed. The general processor can be a microprocessor or the processor can also be any conventional processor, etc. The steps of the method disclosed in the embodiment of the present application can be directly embodied as a hardware decoding processor to perform, or the hardware and software modules in the decoding processor are combined and performed. The software module can be located in a mature storage medium in the field such as a random access memory, a flash memory, a read-only memory, a programmable read-only memory or an electrically erasable programmable memory, a register, etc. The storage medium is located in a memory, and the processor reads the information in the memory and completes the steps of the above method in combination with its hardware.

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

It should be understood that the above-mentioned memory is exemplary but not restrictive. For example, the memory in the embodiments of the present application may also be static random access memory (static RAM, SRAM), dynamic random access memory (dynamic RAM, DRAM), synchronous dynamic random access memory (synchronous DRAM, SDRAM), double data rate synchronous dynamic random access memory (double data rate SDRAM, DDR SDRAM), enhanced synchronous dynamic random access memory (enhanced SDRAM, ESDRAM), synchronous link dynamic random access memory (synch link DRAM, SLDRAM) and direct memory bus random access memory (Direct Rambus RAM, DR RAM), etc. That is to say, the memory in the embodiments of the present application is intended to include but not limited to these and any other suitable types of memory.

An embodiment of the present application also provides a computer-readable storage medium for storing a computer program.

Optionally, the computer-readable storage medium can be applied to the network device or base station in the embodiments of the present application, and the computer program enables the computer to execute the corresponding processes implemented by the network device or base station in the various methods of the embodiments of the present application. For the sake of brevity, they are not repeated here.

Optionally, the computer-readable storage medium can be applied to the mobile terminal/terminal device in the embodiments of the present application, and the computer program enables the computer to execute the corresponding processes implemented by the mobile terminal/terminal device in the various methods of the embodiments of the present application. For the sake of brevity, they are not repeated here.

An embodiment of the present application also provides a computer program product, including computer program instructions.

Optionally, the computer program product can be applied to the network device or base station in the embodiments of the present application, and the computer program instructions enable the computer to execute the corresponding processes implemented by the network device or base station in the various methods of the embodiments of the present application. For the sake of brevity, they are not repeated here.

Optionally, the computer program product can be applied to the mobile terminal/terminal device in the embodiments of the present application, and the computer program instructions enable the computer to execute the corresponding processes implemented by the mobile terminal/terminal device in the various methods of the embodiments of the present application. For the sake of brevity, they are not repeated here.

The embodiment of the present application also provides a computer program.

Optionally, the computer program can be applied to the network device or base station in the embodiments of the present application. When the computer program runs on a computer, the computer executes the corresponding processes implemented by the network device or base station in the various methods of the embodiments of the present application. For the sake of brevity, they are not described here.

Optionally, the computer program can be applied to the mobile terminal/terminal device in the embodiments of the present application. When the computer program is run on a computer, the computer executes the corresponding processes implemented by the mobile terminal/terminal device in the various methods of the embodiments of the present application. For the sake of brevity, they are not repeated here.

Those of ordinary skill in the art will appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of this application.

Those skilled in the art can 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.

In the several embodiments provided in the present application, it should be understood that the disclosed systems, devices and methods can be implemented in other ways. For example, the device embodiments described above are only schematic. For example, the division of the units is only a logical function division. There may be other division methods in actual implementation, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.

The units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

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

If the functions are implemented in the form of software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. In view of such an understanding, the technical solution of the present application can be embodied in the form of a software product in essence or in other words, the part that contributes to the prior art or the part of the technical solution. The computer software product is stored in a storage medium, including several instructions for enabling a computer device (which can be a personal computer, a server, or a network device, etc.) to perform all or part of the steps of the methods described in each embodiment of the present application. The aforementioned storage medium includes: various media that can store program codes, such as a USB flash drive, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk.

The above is only a specific implementation of the present application, but the protection scope of the present application is not limited thereto. Any technician familiar with the technical field can easily think of changes or substitutions within the technical scope disclosed in the present application, which should be included in the protection scope of the present application. Therefore, the protection scope of the present application should be based on the protection scope of the claims.

Claims (44)

1. A method of wireless communication, comprising:

the terminal equipment receives first configuration information; the first configuration information includes: configuration information of a cross-carrier scheduling mode of a first service cell of the terminal equipment;

Wherein the first configuration information further includes: a first indication; the first indication is used for indicating a same carrier scheduling mode supporting a first service cell of the terminal equipment; or the first configuration information further includes: a second indication; the second instruction is used for indicating supporting a dynamic adjustment carrier scheduling mode; or the terminal equipment defaults to support the same carrier scheduling mode; wherein, the first configuration information is carried in a radio resource control RRC signaling;

The terminal equipment receives indication information, wherein the indication information is used for indicating whether to activate a cross-carrier scheduling mode or a same-carrier scheduling mode of a first service cell of the terminal equipment; the indication information is carried in a media access control-control unit (MAC CE) or Downlink Control Information (DCI);

The terminal equipment determines whether to activate a cross-carrier scheduling mode or a same-carrier scheduling mode of a first service cell of the terminal equipment based on the indication information;

The time for receiving the indication information by the terminal equipment is the same as the time for activating the cross-carrier scheduling mode or the same-carrier scheduling mode; or the time difference between the time when the terminal equipment receives the indication information and the time when the cross-carrier scheduling mode or the same-carrier scheduling mode is activated is a preset value.

2. The method of claim 1, wherein the second indication is at a serving cell level or at a terminal device level.

3. The method according to claim 1 or 2, wherein the configuration information of the cross-carrier scheduling manner includes: the identification of the second service cell and a Carrier Indication Field (CIF) in the scheduling information of the first service cell;

the second serving cell is used for scheduling the first serving cell.

4. The method according to claim 1 or 2, wherein the indication information comprises a plurality of bits, each bit being used to indicate whether a serving cell activates a cross-carrier scheduling mode or a co-carrier scheduling mode of the serving cell.

5. The method according to claim 1 or 2, wherein the indication information comprises a plurality of bits, each bit being used for indicating whether a serving cell configured to support a cross-carrier scheduling mode activates the cross-carrier scheduling mode or the co-carrier scheduling mode of the serving cell.

6. The method of claim 5, wherein the indication information includes a bit number ceil (n/8) x 8, where n is a number of serving cells supporting a cross-carrier scheduling manner.

7. The method according to claim 1 or 2, wherein the indication information comprises a plurality of bits, each bit being used for indicating whether a serving cell configured to support the dynamically adjusted carrier scheduling mode activates the cross-carrier scheduling mode or the co-carrier scheduling mode of the serving cell.

8. The method of claim 7 wherein the indication information includes a bit number ceil (n/8) x 8, where n is a number of serving cells supporting a dynamic adjustment carrier scheduling manner.

9. A method according to claim 1 or 2, wherein the preset value is configured by a network device.

10. A method of wireless communication, comprising:

the network equipment sends first configuration information to the terminal equipment, wherein the first configuration information comprises the following components: configuration information of a cross-carrier scheduling mode of a first service cell of the terminal equipment;

Wherein the first configuration information further includes: a first indication; the first indication is used for indicating a same carrier scheduling mode supporting a first service cell of the terminal equipment; or the first configuration information further includes: a second indication; the second instruction is used for indicating supporting a dynamic adjustment carrier scheduling mode; or the terminal equipment defaults to support the same carrier scheduling mode; the first configuration information is carried in RRC signaling;

the network equipment sends indication information to the terminal equipment, wherein the indication information is used for indicating whether to activate a cross-carrier scheduling mode or a same-carrier scheduling mode of a first service cell of the terminal equipment; the indication information is carried in MAC CE or DCI;

The time for receiving the indication information by the terminal equipment is the same as the time for activating the cross-carrier scheduling mode or the same-carrier scheduling mode; or the time difference between the time when the terminal equipment receives the indication information and the time when the cross-carrier scheduling mode or the same-carrier scheduling mode is activated is a preset value.

11. The method of claim 10, wherein the second indication is at a serving cell level or at a terminal device level.

12. The method according to claim 10 or 11, wherein the configuration information of the cross-carrier scheduling manner includes: the identification of the second service cell and the CIF in the scheduling information of the first service cell;

the second serving cell is used for scheduling the first serving cell.

13. The method according to claim 10 or 11, wherein the indication information comprises a plurality of bits, each bit being used to indicate whether a serving cell activates a cross-carrier scheduling mode or a co-carrier scheduling mode of the serving cell.

14. The method according to claim 10 or 11, wherein the indication information comprises a plurality of bits, each bit being used to indicate whether a serving cell configured to support a cross-carrier scheduling mode activates the cross-carrier scheduling mode or the co-carrier scheduling mode of the serving cell.

15. The method of claim 14 wherein the indication information includes a bit number ceil (n/8) x 8, where n is a number of serving cells supporting a cross-carrier scheduling manner.

16. The method according to claim 10 or 11, wherein the indication information comprises a plurality of bits, each bit being used to indicate whether a serving cell configured to support a dynamically adjusted carrier scheduling mode activates a cross-carrier scheduling mode or a co-carrier scheduling mode of the serving cell.

17. The method of claim 16 wherein the indication information includes a bit number ceil (n/8) x 8, where n is a number of serving cells supporting a dynamically adjusted carrier scheduling scheme.

18. The method according to claim 10 or 11, wherein the preset value is configured by a network device.

19. A terminal device, comprising:

A communication unit configured to:

Receiving first configuration information, the first configuration information comprising: configuration information of a cross-carrier scheduling mode of a first service cell of the terminal equipment;

Wherein the first configuration information further includes: a first indication; the first indication is used for indicating a same carrier scheduling mode supporting a first service cell of the terminal equipment; or the first configuration information further includes: a second indication; the second instruction is used for indicating supporting a dynamic adjustment carrier scheduling mode; or the terminal equipment defaults to support the same carrier scheduling mode; the first configuration information is carried in RRC signaling;

Receiving indication information, wherein the indication information is used for indicating whether to activate a cross-carrier scheduling mode or a same-carrier scheduling mode of a first service cell of the terminal equipment; the indication information is carried in MAC CE or DCI;

the processing module is used for determining whether to activate a cross-carrier scheduling mode or a same-carrier scheduling mode of a first service cell of the terminal equipment based on the indication information;

The time for receiving the indication information by the terminal equipment is the same as the time for activating the cross-carrier scheduling mode or the same-carrier scheduling mode; or the time difference between the time when the terminal equipment receives the indication information and the time when the cross-carrier scheduling mode or the same-carrier scheduling mode is activated is a preset value.

20. The terminal device of claim 19, wherein the second indication is at a serving cell level or at a terminal device level.

21. The terminal device according to claim 19 or 20, wherein the configuration information of the cross-carrier scheduling manner includes: the identification of the second service cell and the CIF in the scheduling information of the first service cell;

the second serving cell is used for scheduling the first serving cell.

22. The terminal device according to claim 19 or 20, wherein the indication information comprises a plurality of bits, each bit being used to indicate whether a serving cell activates a cross-carrier scheduling mode or a co-carrier scheduling mode of the serving cell.

23. The terminal device according to claim 19 or 20, wherein the indication information comprises a plurality of bits, each bit being used for indicating whether a serving cell configured to support a cross-carrier scheduling mode activates the cross-carrier scheduling mode or the co-carrier scheduling mode of the serving cell.

24. The terminal device of claim 23, wherein the indication information includes a bit number of ceil (n/8) ×8, where n is a number of serving cells supporting a cross-carrier scheduling manner.

25. The terminal device according to claim 19 or 20, wherein the indication information comprises a plurality of bits, each bit being used for indicating whether a serving cell configured to support a dynamically adjusted carrier scheduling mode activates a cross-carrier scheduling mode or a co-carrier scheduling mode of the serving cell.

26. The terminal device of claim 25, wherein the indication information includes a bit number ceil (n/8) ×8, where n is a number of serving cells supporting a dynamic adjustment carrier scheduling manner.

27. A terminal device according to claim 19 or 20, wherein the preset value is network device configured.

28. A network device, comprising:

A communication unit configured to:

Transmitting first configuration information to a terminal device, wherein the first configuration information comprises: configuration information of a cross-carrier scheduling mode of a first service cell of the terminal equipment;

Wherein the first configuration information further includes: a first indication; the first indication is used for indicating a same carrier scheduling mode supporting a first service cell of the terminal equipment; or the first configuration information further includes: a second indication; the second instruction is used for indicating supporting a dynamic adjustment carrier scheduling mode; or the terminal equipment defaults to support the same carrier scheduling mode; the first configuration information is carried in RRC signaling;

Transmitting indication information to the terminal equipment, wherein the indication information is used for indicating whether to activate a cross-carrier scheduling mode or a same-carrier scheduling mode of a first service cell of the terminal equipment; the indication information is carried in MAC CE or DCI;

The time for receiving the indication information by the terminal equipment is the same as the time for activating the cross-carrier scheduling mode or the same-carrier scheduling mode; or the time difference between the time when the terminal equipment receives the indication information and the time when the cross-carrier scheduling mode or the same-carrier scheduling mode is activated is a preset value.

29. The network device of claim 28, wherein the second indication is at a serving cell level or a terminal device level.

30. The network device according to claim 28 or 29, wherein the configuration information of the cross-carrier scheduling manner includes: the identification of the second service cell and the CIF in the scheduling information of the first service cell;

the second serving cell is used for scheduling the first serving cell.

31. The network device according to claim 28 or 29, wherein the indication information comprises a plurality of bits, each bit being used to indicate whether a serving cell activates a cross-carrier scheduling mode or a co-carrier scheduling mode of the serving cell.

32. The network device according to claim 28 or 29, wherein the indication information comprises a plurality of bits, each bit being used to indicate whether a serving cell configured to support a cross-carrier scheduling mode activates the cross-carrier scheduling mode or the co-carrier scheduling mode of the serving cell.

33. The network device of claim 32, wherein the indication information includes a bit number of ceil (n/8) ×8, where n is a number of serving cells supporting a cross-carrier scheduling manner.

34. The network device according to claim 28 or 29, wherein the indication information comprises a plurality of bits, each bit being used to indicate whether a serving cell configured to support a dynamically adjusted carrier scheduling mode activates a cross-carrier scheduling mode or a co-carrier scheduling mode of the serving cell.

35. The network device of claim 34, wherein the indication information includes a bit number ceil (n/8) ×8, where n is a number of serving cells supporting a dynamic adjustment carrier scheduling manner.

36. The network device of claim 28 or 29, wherein the preset value is network device configured.

37. A terminal device, comprising: a processor and a memory for storing a computer program, the processor being adapted to invoke and run the computer program stored in the memory for performing the method according to any of claims 1 to 9.

38. A network device, comprising: a processor and a memory for storing a computer program, the processor being for invoking and running the computer program stored in the memory, performing the method of any of claims 10 to 18.

39. A chip, comprising: a processor for calling and running a computer program from a memory, causing a device on which the chip is mounted to perform the method of any one of claims 1 to 9.

40. A chip, comprising: a processor for calling and running a computer program from a memory, causing a device on which the chip is mounted to perform the method of any of claims 10 to 18.

41. A computer readable storage medium storing a computer program for causing a computer to perform the method of any one of claims 1 to 9.

42. A computer readable storage medium storing a computer program for causing a computer to perform the method of any one of claims 10 to 18.

43. A computer program product comprising computer program instructions for causing a computer to perform the method of any one of claims 1 to 9.

44. A computer program product comprising computer program instructions for causing a computer to perform the method of any one of claims 10 to 18.