CN115668838B

CN115668838B - Wireless communication method, terminal device and network device

Info

Publication number: CN115668838B
Application number: CN202080101215.6A
Authority: CN
Inventors: 王淑坤
Original assignee: Guangdong Oppo Mobile Telecommunications Corp Ltd
Current assignee: Guangdong Oppo Mobile Telecommunications Corp Ltd
Priority date: 2020-07-29
Filing date: 2020-07-29
Publication date: 2024-06-25
Anticipated expiration: 2040-07-29
Also published as: CN115668838A; WO2022021136A1

Abstract

The embodiment of the application provides a wireless communication method, terminal equipment and network equipment, wherein the method comprises the following steps: the terminal equipment receives indication information, wherein the indication information is used for indicating whether to activate a cross-carrier scheduling mode or a co-carrier scheduling mode of a first service cell of the terminal equipment. Thereby improving the adaptivity of the carrier scheduling mode.

Description

Wireless communication method, terminal device and network device

Technical Field

The embodiment of the application relates to the field of communication, and more particularly relates to a wireless communication method, terminal equipment and network equipment.

Background

Carrier aggregation (Carrier Aggregation, CA) enables a New Radio (NR) system to support a larger bandwidth by jointly scheduling and using resources on multiple carrier units (Component Carrier, CC), thereby enabling a higher system peak rate. Regarding scheduling of each CC in CA, whether a CC in which a physical downlink control channel (Physical Downlink Control Channel, PDCCH) resource used in scheduling is located and a CC to be scheduled are the same CC is classified into co-carrier scheduling and cross-carrier scheduling.

In the prior art, the scheduling mode of one CC is either a cross-carrier scheduling mode or a co-carrier scheduling mode, and the carrier scheduling mode is semi-static configuration through radio resource control (Radio Resource Control, RRC) signaling. The reason for adopting cross-carrier scheduling is that the PDCCH passing through another cell is used for scheduling because the PDCCH of the current serving cell of the terminal device is interfered. However, since the interference suffered by one cell is not necessarily stable, the above-mentioned carrier scheduling method configured by adopting the RRC signaling semi-static method has a problem of low adaptability.

Disclosure of Invention

The embodiment of the application provides a wireless communication method, terminal equipment and network equipment, thereby improving the self-adaptability of a carrier scheduling mode.

In a first aspect, a wireless communication method is provided, the method comprising: the terminal equipment receives indication information, wherein the indication information is used for indicating whether to activate a cross-carrier scheduling mode or a co-carrier scheduling mode of a first service cell of the terminal equipment.

In a second aspect, there is provided a wireless communication method comprising: the network device sends indication information to the terminal device, 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 device.

In a third aspect, a terminal device is provided for performing the method in the first aspect or each implementation manner thereof.

Specifically, the terminal device comprises functional modules for performing the method of the first aspect or its implementation manner.

In a fourth aspect, a network device is provided for performing the method of the second aspect or implementations thereof.

In particular, the network device comprises functional modules for performing the method of the second aspect or implementations thereof described above.

In a fifth aspect, a terminal device is provided comprising a processor and a memory. The memory is used for storing a computer program, and the processor is used for calling and running the computer program stored in the memory and executing the method in the first aspect or various implementation manners thereof.

In a sixth aspect, a network device is provided that includes a processor and a memory. The memory is for storing a computer program and the processor is for calling and running the computer program stored in the memory for performing the method of the second aspect or implementations thereof described above.

A seventh aspect provides an apparatus for implementing the method of any one of the first to second aspects or each implementation thereof.

Specifically, the device comprises: a processor for calling and running a computer program from a memory, causing a device in which the apparatus is installed to perform the method as in any one of the first to second aspects or implementations thereof described above.

In an eighth aspect, a computer-readable storage medium is provided for storing a computer program that causes a computer to perform the method of any one of the above-described first to second aspects or implementations thereof.

In a ninth aspect, there is provided a computer program product comprising computer program instructions for causing a computer to perform the method of any one of the first to second aspects or implementations thereof.

In a tenth aspect, there is provided a computer program which, when run on a computer, causes the computer to perform the method of any one of the first to second aspects or implementations thereof.

By the technical solution of the first aspect or the second aspect, the terminal device may determine whether to activate a cross-carrier scheduling manner or a co-carrier scheduling manner of the first serving cell of the terminal device according to the indication information, so as to dynamically adjust the carrier scheduling manner, thereby improving the adaptability of the carrier scheduling manner, so as to adapt to a cell environment, such as a change of interference, for example: when the interference of the first serving cell is large, the terminal equipment can activate a cross-carrier scheduling mode to perform data scheduling in other cells. When the interference of the first serving cell is smaller, the terminal device can activate the same carrier scheduling mode to perform data scheduling in the cell.

Drawings

Fig. 1 is a schematic diagram of a communication system architecture according to an embodiment of the present application;

Fig. 2 is a schematic diagram of carrier aggregation according to an embodiment of the present application;

Fig. 3 is a schematic diagram of another carrier aggregation according to an embodiment of the present application;

fig. 4 is a schematic illustration of co-carrier scheduling according to an embodiment of the present application;

fig. 5 is a schematic diagram of cross-carrier scheduling according to an embodiment of the present application;

Fig. 6 is a flowchart illustrating interaction of a wireless communication method according to an embodiment of the present application;

Fig. 7 is a schematic diagram of a MAC CE according to an embodiment of the present application;

FIG. 8 is a schematic diagram of another MAC CE according to an embodiment of the present application;

Fig. 9 is a schematic diagram of yet another MAC CE according to an embodiment of the present application;

fig. 10 shows a schematic block diagram of a terminal device 1000 according to an embodiment of the application;

fig. 11 shows a schematic block diagram of a network device 1100 according to an embodiment of the application;

fig. 12 is a schematic block diagram of a communication device 1200 according to an embodiment of the present application;

FIG. 13 is a schematic block diagram of an apparatus of an embodiment of the present application;

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

Detailed Description

The following description of the technical solutions according to the embodiments of the present application will be given with reference to the accompanying drawings in the embodiments of the present application, and it is apparent that the described embodiments are some embodiments of the present application, but not all embodiments. All other embodiments, which can be made by those skilled in the art to which the application pertains without inventive faculty, are intended to fall within the scope of the application.

The embodiment of the application can be applied to various communication systems, such as: global system for mobile communications (Global System of Mobile communication, GSM), code division multiple access (Code Division Multiple Access, CDMA) system, wideband code division multiple access (Wideband Code Division Multiple Access, WCDMA) system, general Packet Radio Service (GPRS), long term evolution (Long Term Evolution, LTE) system, long term evolution advanced (Advanced long term evolution, LTE-a) system, new Radio, NR, evolution system of NR system, LTE-based access to unlicensed spectrum, LTE-U system on unlicensed spectrum, NR-based access to unlicensed spectrum, NR-U system on unlicensed spectrum, universal mobile communication system (Universal Mobile Telecommunication System, UMTS), wireless local area network (Wireless Local Area Networks, WLAN), wireless fidelity (WIRELESS FIDELITY, WIFI), next generation communication system or other communication system, etc.

Generally, the number of connections supported by the conventional Communication system is limited and easy to implement, however, as the Communication technology advances, the mobile Communication system will support not only conventional Communication but also, for example, device-to-Device (D2D) Communication, machine-to-machine (Machine to Machine, M2M) Communication, machine type Communication (MACHINE TYPE Communication, MTC), inter-vehicle (Vehicle to Vehicle, V2V) Communication, and the like, and 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 may be applied to a CA scenario, and may also be applied to a dual-connection (Dual Connectivity, DC) +ca scenario.

The frequency spectrum of the application of the embodiment of the application is not limited. For example, the embodiment of the application can be applied to licensed spectrum and unlicensed spectrum.

An exemplary communication system 100 to which embodiments of the present application may be applied is shown in fig. 1. The communication system 100 may include a network device 110, and the network device 110 may be a device that communicates with a terminal device 120 (or referred to as a communication terminal, terminal). Network device 110 may provide communication coverage for a particular geographic area and may communicate with terminal devices located within the coverage area.

Fig. 1 illustrates one network device and two terminal devices by way of example, and the communication system 100 may alternatively include multiple network devices and may include other numbers of terminal devices within the coverage area of each network device, as embodiments of the application are not limited in this regard.

Optionally, the communication system 100 may further include a network controller, a mobility management entity, and other network entities, which are not limited by the embodiment of the present application.

It should be understood that a device having a communication function in a network/system according to an embodiment of the present application may be referred to as a communication device. Taking the communication system 100 shown in fig. 1 as an example, the communication device may include a network device 110 and a terminal device 120 with communication functions, where the network device 110 and the terminal device 120 may be specific devices described above, and are not described herein again; the communication device may also include other devices in the communication system 100, such as a network controller, a mobility management entity, and other network entities, which are not limited in this embodiment of the present application.

It should be understood that the terms "system" and "network" are used interchangeably herein. The term "and/or" is herein merely an association relationship describing an associated object, meaning that there may be three relationships, e.g., a and/or B, may represent: a exists alone, A and B exist together, and B exists alone. In addition, the character "/" herein generally indicates that the front and rear associated objects are an "or" relationship.

The embodiments of the present application describe various embodiments in connection with a terminal device and a network device, wherein: a terminal device may also be called a User Equipment (UE), an access terminal, a subscriber unit, a subscriber station, a mobile station, a remote terminal, a mobile device, a User terminal, a wireless communication device, a User agent, a User device, or the like. The terminal device may be a Station (ST) in a WLAN, may be a cellular telephone, a cordless telephone, a session initiation protocol (Session Initiation Protocol, SIP) phone, a wireless local loop (Wireless Local Loop, WLL) station, a Personal digital assistant (Personal DIGITAL ASSISTANT, PDA) device, a handheld device with wireless communication functionality, a computing device or other processing device connected to a wireless modem, an in-vehicle device, a wearable device, and a next generation communication system, e.g. a terminal device in an NR network or a terminal device in a future evolved public land mobile network (Public Land Mobile Network, PLMN) network, etc.

By way of example, and not limitation, in embodiments of the present application, the terminal device may also be a wearable device. The wearable device can also be called as a wearable intelligent device, and is a generic name for intelligently designing daily wear by applying wearable technology and developing wearable devices, such as glasses, gloves, watches, clothes, shoes and the like. The wearable device is a portable device that is worn directly on the body or integrated into the clothing or accessories of the user. The wearable device is not only a hardware device, but also can realize a powerful function through software support, data interaction and cloud interaction. The generalized wearable intelligent device includes full functionality, large size, and may not rely on the smart phone to implement complete or partial functionality, such as: smart watches or smart glasses, etc., and focus on only certain types of application functions, and need to be used in combination with other devices, such as smart phones, for example, various smart bracelets, smart jewelry, etc. for physical sign monitoring.

The network device may be a device for communicating with the mobile device, the network device may 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 an Access Point, or a vehicle device, a wearable device, and a network device in NR network or a base station (gNB) or a network device in future evolved PLMN network, etc.

In the embodiment of the present application, the network device provides services for a cell, and the terminal device communicates with the network device through a transmission resource (for example, a frequency domain resource, or a spectrum resource) used by the cell, where the cell may be a cell corresponding to the network device (for example, a base station), and the cell may belong to a macro base station or a base station corresponding to a small cell (SMALL CELL), and the small cell may include: urban cells (Metro cells), micro cells (Micro cells), pico cells (Pico cells), femto cells (Femto cells) and the like, and the small cells have the characteristics of small coverage area and low transmitting power and are suitable for providing high-rate data transmission services.

Before describing the technical scheme of the application, CA is described below:

In order to provide a higher system peak rate, it is necessary to provide a maximum transmission bandwidth of 100MHz, but CA is proposed due to the scarcity of continuous spectrum of such a large bandwidth, i.e. a larger transmission bandwidth is obtained by a plurality of continuous or discontinuous carrier aggregation, thereby obtaining a higher peak rate and throughput. Wherein, according to whether the aggregated carriers are continuous in frequency spectrum, continuous carrier aggregation and discontinuous carrier aggregation can be classified.

CA is to aggregate 2 or more CCs together to support a larger transmission bandwidth (up to 100 MHz). The standard specifies that CA aggregates a maximum of 5 CCs and that the aggregated CCs belong to the same network device.

The bandwidth of each CC may be 5MHz, 10MHz, 15MHz, and 20MHz, but the maximum bandwidth does not exceed 20MHz. As shown in fig. 2, 2 discontinuous 20MHz CC aggregation may obtain a bandwidth of 40MHz, and as shown in fig. 3, 5 continuous 20MHz CC aggregation may obtain a bandwidth of 100 MHz.

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

(1) CCs of the same or different bandwidths;

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

(3) CCs within different frequency bands;

CA can be classified into Intra-band (Intra-band) carrier aggregation and inter-band (inter-band) carrier aggregation according to whether bands (bands) in which aggregated CCs are located are identical.

Basic concept in CA:

Primary cell (PRIMARY CELL, PCELL): it is a cell in which the terminal device performs initial connection establishment, or a cell in which RRC connection reestablishment is performed, or a primary cell designated in a handover (handover) procedure. The PCell is responsible for RRC communication with the terminal device. The CC corresponding to the PCell is called a primary carrier (Primary Component Carrier, PCC). The physical uplink control channel (Physical Uplink Control Channel, PUCCH) is present on and only on the PCC. Among them, the Downlink carrier of the PCell is called a Downlink (DL) PCC, and the Uplink carrier of the PCell is called an Uplink (UL) PCC.

Secondary cell (SecondaryCell, SCell): it is added at RRC reconfiguration to provide additional radio resources, without any RRC communication between SCell and terminal device. The CC corresponding to the SCell is referred to as a secondary carrier (Secondary Component Carrier, SCC). The downlink carrier of the SCell is referred to as DL SCC, and the uplink carrier of the SCell is referred to as UL SCC.

The PCell is determined at the time of connection establishment (connection establishment). SCell is added/modified/released by RRC connection reconfiguration message (RRC Connection Reconfiguraion) after initial security activation procedure (initial security activation procedure).

Serving cell (SERVING CELL): is a cell that serves (i.e., uplink and downlink transmissions) for a terminal device. If the terminal device is in RRC CONNECTED state (rrc_connected), but CA is not configured, the terminal device has only one serving cell, i.e., 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. I.e. the serving cell may refer to both PCell and SCell. A terminal device configured with CA may be connected with 1 PCell and at most 4 scells. The terminal device configured with CA uses the same Cell-radio network temporary identity (Cell-RadioNetworkTemporaryIdentifier, C-RNTI) in all serving cells to ensure that the C-RNTI does not collide in all serving cells.

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

Since both asymmetric carrier aggregation and symmetric carrier aggregation are supported, there is a certain requirement for downlink carrier aggregation, and there may be no uplink carrier aggregation. Also, for the PCell, there must be PDCCH and PUCCH of the present cell, and only the PCell has PUCCH, and other secondary cells may have PDCCH.

As described above, regarding scheduling of each CC in CA, whether or not a CC in which a PDCCH resource used for scheduling is located and a CC to be scheduled are the same CC is classified into co-carrier scheduling and cross-carrier scheduling.

The co-carrier scheduling refers to that PDCCH scheduling of one serving cell is performed on radio resources on the own cell. I.e. 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 radio resources on another serving cell. I.e. scheduling information is transmitted on one CC and corresponding data is transmitted on another CC. The introduction of cross-carrier scheduling is based on interference avoidance of heterogeneous networks.

Fig. 4 is a schematic illustration of co-carrier scheduling according to an embodiment of the present application, and as shown in fig. 4, scheduling of each physical downlink shared channel (Physical Downlink SHARED CHANNEL, PDSCH) is scheduled by PDCCH on the CC on which it is located. Fig. 5 is a schematic diagram of cross-carrier scheduling according to an embodiment of the present application, where, as shown in fig. 5, scheduling of PDSCH on three CCs is scheduled by PDCCH on one CC.

It should be noted that, in the cross-carrier scheduling, the scheduling information between different CCs is distinguished by a carrier indication field (Carrier Indicator Field, CIF) in downlink control information (Downlink Control Information, DCI), the CIF is used to indicate the number of the CC, fix 3 bits, and take values 0 to 7, where the CIF of the PCC is fixed to 0. There may be multiple CCs on which the PDCCH channel exists, but the PCC must have its own PDCCH channel. The network device may configure a PDCCH channel indicating which CC the current SCC uses for scheduling through higher layer signaling.

As described above, in the prior art, the scheduling manner of one CC is either the cross-carrier scheduling manner or the co-carrier scheduling manner, and the carrier scheduling manner is semi-static configured through RRC signaling. The carrier scheduling mode is configured by adopting the RRC signaling semi-static mode, so that the problem of low adaptability exists.

In order to solve the technical problems, the application enables the terminal equipment to dynamically change or adjust the carrier scheduling mode in a dynamic indication mode.

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

Fig. 6 is a flowchart illustrating an interaction of a wireless communication method according to an embodiment of the present application, where the method includes the following steps:

step S610: the terminal equipment receives indication information, wherein the indication information is used for indicating whether to activate a cross-carrier scheduling mode or a co-carrier scheduling mode of a first service cell of the terminal equipment.

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 a CC corresponding to the cell. For example: the carrier scheduling method of the cell may be referred to as a CC scheduling method.

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

Alternatively, the first dedicated signaling may be RRC signaling, DCI, or a medium access control element (MEDIA ACCESS Control Control Element, MAC CE).

In the present application, after 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 mode of a first service cell of the terminal equipment.

Alternatively, the network device may send the first configuration information through second dedicated signaling.

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

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

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

Optionally, the configuration information of the cross-carrier scheduling manner includes: an Identity (ID) of the second serving cell and a CIF in scheduling information of the first serving cell. The second serving cell is used for scheduling the first serving cell. I.e. the PDCCH on the second serving cell is used for scheduling data of the first serving cell.

Optionally, the data of the first serving cell may be uplink data or downlink data, and when the data of the first serving cell is uplink data, the PDCCH on the second serving cell is used for scheduling the data of the first serving cell, which may also be described as: the PDCCH on the second serving cell is used to schedule a Physical Uplink shared channel (Physical Uplink SHARED CHANNEL, PUSCH) of the first serving cell. When the data of the first serving cell is downlink data, then the PDCCH on the second serving cell is used to schedule the data of the first serving cell, which can also be described as: the PDCCH on the second serving cell is used to schedule the PDSCH of the first serving cell.

Alternatively, the scheduling information of the first serving cell may also be described as scheduling information of 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 co-carrier scheduling mode, since the scheduling information and the CC for data transmission are the same CC, the network device does not need to send configuration information of the co-carrier scheduling mode to the terminal device. However, the terminal device needs to know whether the network device supports the co-carrier scheduling mode or whether the network device supports the dynamically adjusted carrier scheduling mode. The terminal device may learn whether the network device supports the same carrier scheduling manner or whether the network device supports the dynamic adjustment carrier scheduling manner, but is not limited thereto:

(1) The first configuration information further includes: a first indication. The first indication is used for indicating a same carrier scheduling mode supporting a first serving cell of the terminal equipment.

(2) The first configuration information further includes: a second indication. The second indication is used for indicating supporting the dynamic adjustment of the carrier scheduling mode.

(3) The terminal device defaults to support the co-carrier scheduling mode.

Description is made with respect to item (1):

alternatively, the first indication may be set on a preset bit of the second dedicated signaling, and the length may be a preset length.

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

Optionally, the preset length may be 1, and correspondingly, the value of the first indication may be 0 or 1, and when the value of the first indication is 0, the same carrier scheduling manner of the first serving cell supporting the terminal device is indicated. Or when the first indication takes a value of 1, the same carrier scheduling mode of the first service cell supporting the terminal equipment is indicated.

Optionally, when the first configuration information includes the first indication and the configuration information of the cross-carrier scheduling mode of the first serving cell, it means that the terminal device supports the co-carrier scheduling mode and the cross-carrier scheduling mode of the first serving cell, based on which the terminal device can dynamically adjust the carrier scheduling mode according to the indication information.

Description is made for the item (2):

Optionally, the second indication is at the serving cell level or at the terminal device level. I.e. the second indication may indicate that the first serving cell supports dynamically adjusted carrier scheduling. The terminal device may also be instructed to support adjustment of the carrier scheduling manner.

Alternatively, the second indication may be set on a preset bit of the second dedicated signaling, and the length may be a preset length.

Optionally, the preset length may be 1, and correspondingly, the value of the second indication may be 0 or 1, and when the value of the second indication is 0, the support of dynamically adjusting the carrier scheduling mode is indicated. Or when the first indication takes a value of 1, the dynamic adjustment carrier scheduling mode is supported.

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

It should be understood that, when the initial default carrier scheduling mode of the first serving cell is the co-carrier scheduling mode, then activating the co-carrier scheduling mode may be understood as using the co-carrier scheduling mode; when the initial default carrier scheduling mode of the first serving cell is a cross-carrier scheduling mode, then activating the co-carrier scheduling mode may 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 serving cell is a cross-carrier scheduling mode, then activating the co-carrier scheduling mode may be understood as switching the carrier scheduling mode to the co-carrier scheduling mode or using the co-carrier scheduling mode; when the initial default carrier scheduling mode of the first serving cell is the cross-carrier scheduling mode, then activating the cross-carrier scheduling mode may be understood as using the cross-carrier scheduling mode.

Or "active" is relative to "inactive", the initial default carrier scheduling mode may be understood as the carrier scheduling mode in the inactive state.

The time for receiving the indication information by the terminal device is the same as the time for activating the cross-carrier scheduling mode or the same as the time for activating the cross-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. For example: the time for the terminal equipment to receive the indication information is n, the time for activating the cross-carrier scheduling mode or the same-carrier scheduling mode is n+k, and k is a preset value.

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

Alternatively, in the present application, the time unit may be a subframe, a symbol, a slot, or the like, which is not limited in the present application.

In summary, in the present application, the terminal device may determine whether to activate the cross-carrier scheduling mode or the co-carrier scheduling mode of the first serving 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, so as to adapt to the cell environment, such as the change of interference, for example: when the interference of the first serving cell is large, the terminal equipment can activate a cross-carrier scheduling mode to perform data scheduling in other cells. When the interference of the first serving cell is smaller, the terminal device can activate the same carrier scheduling mode to perform data scheduling in the cell.

The following will describe the above indication information in detail, wherein the function of the indication information is as follows, but not limited thereto:

(1) The indication information includes a plurality of bits, and each bit is used for indicating whether a service cell activates a cross-carrier scheduling mode or a co-carrier scheduling mode of the service 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 co-carrier scheduling mode of the serving cell.

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

Alternatively, the indication information may be carried in a MAC CE or DCI. If the indication information is carried in the MAC CEs, each MAC CE defines a Logical channel identification (Logical CHANNEL IDENTITY, LCID) and identifies the MAC CE in a MAC packet data Unit (PACKET DATA Unit, PDU).

When the instruction information is carried in the MAC CE, the following description is made regarding the function of the instruction information described above:

description is made with respect to item (1):

The MAC CE may be 8 bits as shown in fig. 7, or may be 32 bits as shown in fig. 8. Wherein each bit corresponds to a serving cell. Ci corresponds to a serving cell with ID i, and the value of Ci indicates whether the same carrier scheduling mode or the cross carrier scheduling mode of the serving cell is activated. For example, 0 indicates that co-carrier scheduling is activated, and 1 indicates that cross-carrier scheduling is activated. Or 1 indicates that co-carrier scheduling is activated, and 0 indicates that cross-carrier scheduling is activated.

Description is made for the item (2):

The MAC CE may be an integer multiple of 8 bits, as shown in fig. 9, where each bit corresponds to a serving cell configured to support the cross-carrier scheduling manner. And c, configuring a service cell supporting a cross-carrier scheduling mode corresponding to the ID of Ci as i, wherein the value of Ci indicates whether the same-carrier scheduling mode or the cross-carrier scheduling mode of the service cell is activated. For example, 0 indicates that co-carrier scheduling is activated, and 1 indicates that cross-carrier scheduling is activated. Or 1 indicates that co-carrier scheduling is activated, and 0 indicates that cross-carrier scheduling is activated. The indication information or the number of bits included in the MAC CE is ceil (n/8) ×8, where n is the number of serving cells supporting the cross-carrier scheduling manner. ceil () is a round-up function. For example, n=12, and the mac CE includes a bit number of Ceil (12/8) by 8=16.

Description is made for the item (3):

The MAC CE may be an integer multiple of 8 bits, as shown in fig. 9, where each bit corresponds to a serving cell configured to support a dynamic adjustment carrier scheduling manner, ci corresponds to a serving cell configured to support a dynamic adjustment carrier scheduling manner with ID i, and the value of Ci indicates whether the same carrier scheduling manner or the cross carrier scheduling manner of the serving cell is activated. For example, 0 indicates that co-carrier scheduling is activated, and 1 indicates that cross-carrier scheduling is activated. Or 1 indicates that co-carrier scheduling is activated, and 0 indicates that cross-carrier scheduling is activated. The indication information or the number of bits included in the MAC CE is ceil (n/8) ×8, where n is the number of serving cells supporting the dynamic adjustment carrier scheduling method. For example, n=12, and the mac CE includes a bit number of Ceil (12/8) by 8=16.

When the indication information is carried in the DCI, the DCI may carry a bitmap (bitmap) defined according to the number of bits in the MAC CE in the above three cases, where 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, which is not described in detail in the present application.

In summary, in the present application, the indication information includes a plurality of bits, and each bit is used to indicate whether a serving cell activates a cross-carrier scheduling manner or a co-carrier scheduling manner of the serving cell. Or the indication information includes a plurality of bits, and each bit is used for indicating whether a service cell configured with a support of a cross-carrier scheduling mode activates the cross-carrier scheduling mode or the co-carrier scheduling mode of the service cell. Or the indication information comprises a plurality of bits, and each bit is used for indicating whether a service cell configured with the service cell supporting the dynamic adjustment carrier scheduling mode activates the cross-carrier scheduling mode or the same-carrier scheduling mode of the service cell. The terminal equipment can determine whether to activate the cross-carrier scheduling mode or the same-carrier scheduling mode of the first service cell of the terminal equipment according to the indication information so as to dynamically adjust the carrier scheduling mode, thereby improving the adaptability of the carrier scheduling mode.

The method embodiments of the present application are described in detail above with reference to fig. 6 to 9, and the apparatus embodiments of the present application are described in detail below with reference to fig. 10 to 14, it being understood that the apparatus embodiments and the method embodiments correspond to each other, and similar descriptions may refer to the method embodiments.

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

Optionally, the communication unit 1010 is further configured to receive first configuration information, where the first configuration information includes: configuration information of a cross-carrier scheduling mode of a first service cell of the terminal equipment.

Optionally, the first configuration information further includes: a first indication. The first indication is used for indicating a same carrier scheduling mode supporting a first serving cell of the terminal equipment.

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

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

Optionally, the terminal device defaults to support the co-carrier scheduling mode.

Optionally, the configuration information of the cross-carrier scheduling manner includes: the identity of the second serving cell and the CIF in the scheduling information of the first serving cell. The second serving cell is used for scheduling the first serving cell.

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

Optionally, the indication information includes a plurality of bits, and each bit is used for indicating whether a serving cell configured to support the cross-carrier scheduling mode activates the cross-carrier scheduling mode or the co-carrier scheduling mode of the serving cell.

Optionally, the indication information includes a bit number ceil (n/8) x 8, where n is the number of serving cells supporting the cross-carrier scheduling manner.

Optionally, the indication information includes a plurality of bits, and each bit is used for indicating whether a serving cell configured to support the dynamic adjustment carrier scheduling mode activates the cross-carrier scheduling mode or the co-carrier scheduling mode of the serving cell.

Optionally, the indication information includes a bit number ceil (n/8) x 8, where n is the number of serving cells supporting the dynamic adjustment carrier scheduling mode.

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

Optionally, a time difference between a time when the terminal device receives the indication information and a 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 a MAC CE or DCI.

Alternatively, in some embodiments, the communication unit may be a communication interface or transceiver, or an input/output interface of a communication chip or a system on a 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 embodiment of the method of the present application, and the foregoing and other operations and/or functions of each unit in the terminal device 1000 are respectively for implementing the corresponding flow of the terminal device in the embodiment of the method, which is not described herein for brevity.

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

Optionally, the communication unit 1110 is further configured to send first configuration information to the terminal device, where the first configuration information includes: configuration information of a cross-carrier scheduling mode of a first service cell of the terminal equipment.

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

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

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 embodiment of the method of the present application, and the foregoing and other operations and/or functions of each unit in the network device 1100 are respectively for implementing the corresponding flow of the network device in the embodiment of the method, which is not described herein for brevity.

Fig. 12 is a schematic block diagram of a communication device 1200 according to an embodiment of the present application. The communication device 1200 shown in fig. 12 comprises a processor 1210, which processor 1210 may call and run a computer program from memory to implement the method in an embodiment of the application.

Optionally, as shown in fig. 12, the communication device 1200 may also include a memory 1220. Wherein the processor 1210 may call and run computer programs from the memory 1220 to implement the methods of embodiments of the present application.

The memory 1220 may be a separate device from 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, and in particular, may send information or data to other devices, or receive information or data sent by other devices.

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

Optionally, the communication device 1200 may be specifically a network device according to an embodiment of the present application, and the communication device 1200 may implement a corresponding flow implemented by the network device in each method according to an embodiment of the present application, which is not described herein for brevity.

Optionally, the communication device 1200 may be specifically a terminal device in the embodiment of the present application, and the communication device 1200 may implement a corresponding flow implemented by the terminal device in each method in the embodiment of the present application, which is not described herein for brevity.

Fig. 13 is a schematic structural view of an apparatus of an embodiment of the present application. The apparatus 1300 shown in fig. 13 includes a processor 1310, and the processor 1310 may call and execute a computer program from a memory to implement the method in the embodiment of the present application.

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

Wherein the memory 1320 may be a separate device from the processor 1310 or may be integrated into the processor 1310.

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

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

Optionally, the apparatus may be applied to a network device in the embodiment of the present application, and the apparatus may implement a corresponding flow implemented by the network device in each method in the embodiment of the present application, which is not described herein for brevity.

Optionally, the apparatus may be applied to a terminal device in the embodiment of the present application, and the apparatus may implement a corresponding flow implemented by the terminal device in each method in the embodiment of the present application, which is not described herein for brevity.

Alternatively, the device according to the embodiment of the present application may be a chip. For example, a system-on-chip or a system-on-chip, etc.

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

The terminal device 1410 may be used to implement the corresponding functions implemented by the terminal device in the above method, and the network device 1420 may be used to implement the corresponding functions implemented by the network device or the base station in the above method, which are not described herein for brevity.

It should be appreciated that the processor of an embodiment of the present application may be an integrated circuit chip having signal processing capabilities. In implementation, the steps of the above method embodiments may be implemented by integrated logic circuits of hardware in a processor or instructions in software form. The Processor may be a general purpose Processor, a digital signal Processor (DIGITAL SIGNAL Processor, DSP), an Application SPECIFIC INTEGRATED Circuit (ASIC), an off-the-shelf programmable gate array (Field Programmable GATE ARRAY, FPGA) or other programmable logic device, discrete gate or transistor logic device, discrete hardware components. The disclosed methods, steps, and logic blocks in the embodiments of the present application may be implemented or performed. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like. The steps of the method disclosed in connection with the embodiments of the present application may be embodied directly in the execution of a hardware decoding processor, or in the execution of a combination of hardware and software modules in a decoding processor. The software modules may be located in a random access memory, flash memory, read only memory, programmable read only memory, or electrically erasable programmable memory, registers, etc. as well known in the art. The storage medium is located in a memory, and the processor reads the information in the memory and, in combination with its hardware, performs the steps of the above method.

It will be appreciated that the memory in embodiments of the application may be volatile memory or nonvolatile memory, or may include both volatile and nonvolatile memory. The nonvolatile Memory may be a Read-Only Memory (ROM), a Programmable ROM (PROM), an Erasable PROM (EPROM), an Electrically Erasable EPROM (EEPROM), or a flash Memory. The volatile memory may be random access memory (Random Access Memory, RAM) which acts as external cache memory. By way of example, and not limitation, many forms of RAM are available, such as static random access memory (STATIC RAM, SRAM), dynamic random access memory (DYNAMIC RAM, DRAM), synchronous Dynamic Random Access Memory (SDRAM), double data rate Synchronous dynamic random access memory (Double DATA RATE SDRAM, DDR SDRAM), enhanced Synchronous dynamic random access memory (ENHANCED SDRAM, ESDRAM), synchronous link dynamic random access memory (SYNCHLINK DRAM, SLDRAM), and Direct memory bus RAM (DR RAM). It should be noted that the memory of the systems and methods described herein is intended to comprise, without being limited to, these and any other suitable types of memory.

It should be appreciated that the above memory is exemplary but not limiting, and 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 (SDRAM), double data rate synchronous dynamic random access memory (doubledata RATE SDRAM, DDR SDRAM), enhanced synchronous dynamic random access memory (ENHANCED SDRAM, ESDRAM), synchronous link dynamic random access memory (SYNCH LINK DRAM, SLDRAM), direct Rambus RAM (DR RAM), and the like. That is, the memory in embodiments of the present application is intended to comprise, without being limited to, these and any other suitable types of memory.

The embodiment of the application also provides a computer readable storage medium for storing a computer program.

Optionally, the computer readable storage medium may be applied to a network device or a base station in the embodiment of the present application, and the computer program causes a computer to execute a corresponding flow implemented by the network device or the base station in each method of the embodiment of the present application, which is not described herein for brevity.

Optionally, the computer readable storage medium may be applied to a mobile terminal/terminal device in the embodiment of the present application, and the computer program causes a computer to execute a corresponding procedure implemented by the mobile terminal/terminal device in each method of the embodiment of the present application, which is not described herein for brevity.

The embodiment of the application also provides a computer program product comprising computer program instructions.

Optionally, the computer program product may be applied to a network device or a base station in the embodiment of the present application, and the computer program instructions cause a computer to execute corresponding flows implemented by the network device or the base station in the methods in the embodiments of the present application, which are not described herein for brevity.

Optionally, the computer program product may be applied to a mobile terminal/terminal device in the embodiment of the present application, and the computer program instructions cause a computer to execute corresponding processes implemented by the mobile terminal/terminal device in each method of the embodiment of the present application, which are not described herein for brevity.

The embodiment of the application also provides a computer program.

Optionally, the computer program may be applied to a network device or a base station in the embodiment of the present application, and when the computer program runs on a computer, the computer is caused to execute a corresponding flow implemented by the network device or the base station in each method in the embodiment of the present application, which is not described herein for brevity.

Optionally, the computer program may be applied to a mobile terminal/terminal device in the embodiment of the present application, and when the computer program runs on a computer, the computer is caused to execute corresponding processes implemented by the mobile terminal/terminal device in each method in the embodiment of the present application, which is not described herein for brevity.

Those of ordinary skill in the art will appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware, or combinations of computer software and electronic hardware. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the solution. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present application.

It will be clear to those skilled in the art that, for convenience and brevity of description, specific working procedures of the above-described systems, apparatuses and units may refer to corresponding procedures in the foregoing method embodiments, and are not repeated herein.

In the several embodiments provided by the present application, it should be understood that the disclosed systems, devices, and methods may be implemented in other manners. For example, the apparatus embodiments described above are merely illustrative, e.g., the division of the units is merely a logical function division, and there may be additional divisions when actually implemented, e.g., multiple units or components may be combined or integrated into another system, or some features may be omitted or not performed. Alternatively, the coupling or direct coupling or communication connection shown or discussed with each other may be an indirect coupling or communication connection via some interfaces, devices or units, which may be in electrical, mechanical or other form.

The units described as separate units may or may not be physically separate, and units shown as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of 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 the embodiments of the present application may be integrated in one processing unit, or each unit may exist alone physically, or two or more units may be integrated in one unit.

The functions, if implemented in the form of software functional units and sold or used as a stand-alone product, may be stored in a computer-readable storage medium. For such understanding, the technical solution of the present application may be embodied essentially or in a part contributing to the prior art or in a part of the technical solution, in the form of a software product stored in a storage medium, comprising several instructions for causing a computer device (which may be a personal computer, a server, a network device, etc.) to perform all or part of the steps of the method according to the embodiments of the present application. And the aforementioned storage medium includes: a U-disk, a removable hard disk, a Read-Only Memory (ROM), a random access Memory (Random Access Memory, RAM), a magnetic disk, or an optical disk, or other various media capable of storing program codes.

The foregoing is merely illustrative of the present application, and the present application is not limited thereto, and any person skilled in the art will readily recognize that variations or substitutions are within the scope of the present application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.

Claims

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;

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;

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;

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;

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;

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.